drvctl(8) - NetBSD Manual Pages

DRVCTL(8)               NetBSD System Manager's Manual               DRVCTL(8)


NAME

     drvctl -- tool to rescan busses and detach devices on user request


SYNOPSIS

     drvctl -r [-a attribute] busdevice [locator ...]
     drvctl -d device
     drvctl [-n] -l [device]
     drvctl -p device
     drvctl -Q device
     drvctl -R device
     drvctl -S device


DESCRIPTION

     The drvctl program works with the drvctl(4) pseudo-driver, and allows to
     rescan busses and to detach drivers from devices.

     The following options are available:

     -a      Give the interface attribute where children are to be attached to
             (and which defines the interpretation of the locator informa-
             tion).  This will only be needed in rare cases where the bus has
             multiple attributes.

     -d      Detach the device driver from the device given by the device
             argument.

     -l      List the children of the device specified by the device argument.
             If device is not specified, list roots of the device tree
             instead.  Output comes in two columns.  The first column is
             device, or ``root'' if device is not specified.  The second col-
             umn is the child.

     -n      Suppress first column in -l output.

     -p      Get the properties for the device specified by the device argu-
             ment.  The properties are displayed as an XML property list.

     -Q      Resume the ancestors of device, device itself, and all of its
             descendants.

     -R      Resume both the ancestors of device and device itself.

     -r      Rescan the bus given by the busdevice argument.  The scan range
             can be restricted by an optional locator list.

     -S      Suspend both the descendants of device and device itself.


FILES

     /dev/drvctl


SEE ALSO

     proplib(3), autoconf(9)


BUGS

     Currently, there is no good way to get information about locator lengths
     and default values (which is present at kernel configuration time) out of
     a running kernel.  Thus the locator handling is less intelligent as it
     could be.

NetBSD 5.1                      April 20, 2009                      NetBSD 5.1