Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

attach(9E)

probe(9E)

ddi_peek(9F)

ddi_poke(9F)

NAME

ddi_poke, ddi_pokec, ddi_pokes, ddi_pokel, ddi_poked − write a value to a location

SYNOPSIS

#include <sys/ddi.h>
#include <sys/sunddi.h>
int ddi_pokec(dev_info_t ∗dip, char ∗addr, char value
);
int ddi_pokes(dev_info_t ∗dip, short ∗addr, short value
);
int ddi_pokel(dev_info_t ∗dip, long ∗addr, long value
);
int ddi_poked(dev_info_t ∗dip, longlong_t ∗addr
, longlong_t value);

ARGUMENTS

dip A pointer to the device’s dev_info structure. 

addr Virtual address of the location to be written to. 

value Value to be written to the location. 

INTERFACE LEVEL

Solaris DDI specific (Solaris DDI). 

DESCRIPTION

These routines cautiously attempt to write a value to a specified virtual address, using the parent nexus driver to assist in the process where necessary. 

If the address is not valid, or the value cannot be written without an error occurring, an error code is returned. 

These routines are most useful when first trying to establish the presence of a given device on the system in a driver’s probe(9E) or attach(9E) routines. 

On multiprocessing machines these routines can be extremely heavy-weight, so use the ddi_peek(9F) routines instead if possible. 

RETURN VALUES

DDI_SUCCESS
The value was successfully written to the given virtual address.

DDI_FAILURE
An error occurred while trying to write to the location.

CONTEXT

These functions can be called from user or interrupt context. 

SEE ALSO

attach(9E), probe(9E), ddi_peek(9F)

Writing Device Drivers

SunOS 5.4  —  Last change: 26 Jul 1993

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026