ddi-forceattach(9P) Kernel Properties for Drivers ddi-forceattach(9P)NAME
ddi-forceattach, ddi-no-autodetach - properties controlling driver attach/detach behavior
DESCRIPTION
Solaris device drivers are attached by devfsadm(1M) and by the kernel in response to open(2) requests from applications. Drivers not cur-
rently in use can be detached when the system experiences memory pressure. The ddi-forceattach and ddi-no-autodetach properties can be used
to customize driver attach/detach behavior.
The ddi-forceattach is an integer property, to be set globally by means of the driver.conf(4) file. Drivers with this property set to 1 are
loaded and attached to all possible instances during system startup. The driver will not be auto-detached due to system memory pressure.
The ddi-no-autodetach is an integer property to be set globally by means of the driver.conf(4) file or created dynamically by the driver on
a per-instance basis with ddi_prop_update_int(9F). When this property is set to 1, the kernel will not auto-detach driver due to system
memory pressure.
Note that ddi-forceattach implies ddi-no-autodetach. Setting either property to a non-integer value or an integer value not equal to 1 pro-
duces undefined results. These properties do not prevent driver detaching in response to reconfiguration requests, such as executing com-
mands cfgadm(1M), modunload(1M), rem_drv(1M), and update_drv(1M).
SEE ALSO driver.conf(4)
Writing Device Drivers
SunOS 5.10 18 May 2001 ddi-forceattach(9P)
Check Out this Related Man Page
ddi_binding_name(9F) Kernel Functions for Drivers ddi_binding_name(9F)NAME
ddi_binding_name, ddi_get_name - return driver binding name
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
char *ddi_binding_name(dev_info_t *dip);
char *ddi_get_name(dev_info_t *dip);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI).
PARAMETERS
dip A pointer to the device's dev_info structure.
DESCRIPTION
ddi_binding_name() and ddi_get_name() return the driver binding name. This is the name used to select a driver for the device. This name is
typically derived from the device name property or the device compatible property. The name returned may be a driver alias or the driver
name.
RETURN VALUES
ddi_binding_name() and ddi_get_name() return the name used to bind a driver to a device.
CONTEXT
ddi_binding_name() and ddi_get_name() can be called from user, kernel, or interrupt context.
SEE ALSO ddi_node_name(9F)
Writing Device Drivers
WARNINGS
The name returned by ddi_binding_name() and ddi_get_name() is read-only.
SunOS 5.11 3 May 1996 ddi_binding_name(9F)
Hello there,
Here is how it goes - I have written a small test driver as an exercise to "Linux Device Drivers" and as a preparation for writing a real, functional driver.
For the sake of seeing how far I got it working (I already implemented the open(0, read(), write() and ioctl() calls) I... (4 Replies)
Hi,
I'm trying to update the last two characters coming in a string globally in a file.
Here is the sample data:
file1
In file1, I want to have all instances replace where _o is appearing in the end of a word with _g. If _o is appearing in the middle or any other position except the... (2 Replies)
My NIC driver, which is writed by myself, didn't pass high pressure test!
I writed a shell script in which the key commands are "scp" to test the driver under high pressure. The shell script loop 3000 times and in each loop, the scp command transmits 1GB data.
When the test fail, it... (2 Replies)