NAME | SYNOPSIS | DESCRIPTION | SEE ALSO
dr
drmach
The dr driver provides a pseudo-driver interface to sequencing dynamic attach and detach of Sun Enterprise 10000 system boards. This interface is provided using file system entry points referred to as attachment points. An attachment point exists for each possible system board slot in the Sun Enterprise 10000 server and takes the form of:
/devices/pseudo/dr@0:slotX
where X represents the physical slot number (0 to 15) for a particular system board.
The dr driver is designed as a general module for sequencing dr operations for different platforms. The dr driver works in conjunction with the drmach(7) miscellaneous module, which provides platform-specific (Sun Enterprise 10000 server) dr sequencing and attributes.
Execution of dr operations on the Sun Enterprise 10000 server is performed by the dr_daemon(1M) . When performing either a dr attach or dr detach operation, dr_daemon(1M) makes the appropriate ioctl(2) system calls into the respective attachment point for that particular board. The general sequence of the ioctl(2) calls are:
For dr attach:
OBP probes for the devices on the incoming board.
Convert the device nodes into CF2 and make the respective resources available to the OS.
For dr detach:
Release usage of certain devices on the respective board.
Remove respective devices from the operating system resource pool.
Remove devices from the (OBP) device tree.
In the Solaris 8 operating environment, unsafe drivers are registered
by using the dr.conf
property unsupported-io-drivers
, as in the following example.
unsupported-io-drivers="device_name1", "device_name2", ...; |
The syntax of the property follows the Form #3 described in driver.conf(4)
add_drv(1M) , drvconfig(1M) , devlinks(1M) , disks(1M) , ports(1M) , dr_daemon(1M) , tapes(1M)
Sun Enterprise 10000 Dynamic Reconfiguration User Guide
Sun Enterprise 10000 SSP 3.2 User Guide
NAME | SYNOPSIS | DESCRIPTION | SEE ALSO