Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

drvctl(8) [netbsd man page]

DRVCTL(8)						    BSD 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 [-nt] -l [device] drvctl [-n] -p device [property ...] 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 information). This will only be needed in rare cases where the bus has multiple attributes. If there are multiple attributes, and one is not spec- ified, drvctl will return an Invalid argument. In such cases, the -p option can be used to determine the available interface 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 column is the child. -n Suppress first column in -l output. Suppress non-XML headers in -p output. -p Get properties for the device specified by the device argument. If property is specified, the value of that property is printed, otherwise 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. -t Print a tree of devices in -l output. 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 than it could be. BSD
January 16, 2012 BSD

Check Out this Related Man Page

DEVICE(9)						   BSD Kernel Developer's Manual						 DEVICE(9)

NAME
device -- an abstract representation of a device SYNOPSIS
typedef struct device *device_t; DESCRIPTION
The device object represents a piece of hardware attached to the system such as an expansion card, the bus which that card is plugged into, disk drives attached to the expansion card etc. The system defines one device, root_bus and all other devices are created dynamically during autoconfiguration. Normally devices representing top-level busses in the system (ISA, PCI etc.) will be attached directly to root_bus and other devices will be added as children of their relevant bus. The devices in a system form a tree. All devices except root_bus have a parent (see device_get_parent(9)). In addition, any device can have children attached to it (see device_add_child(9), device_add_child_ordered(9), device_find_child(9), device_get_children(9), and device_delete_child(9)). A device which has been successfully probed and attached to the system will also have a driver (see device_get_driver(9) and driver(9)) and a devclass (see device_get_devclass(9) and devclass(9)). Various other attributes of the device include a unit number (see device_get_unit(9)), verbose description (normally supplied by the driver, see device_set_desc(9) and device_get_desc(9)), a set of bus-spe- cific variables (see device_get_ivars(9)) and a set of driver-specific variables (see device_get_softc(9)). Devices can be in one of several states: DS_NOTPRESENT the device has not been probed for existence or the probe failed DS_ALIVE the device probe succeeded but not yet attached DS_ATTACHED the device has been successfully attached DS_BUSY the device is currently open The current state of the device can be determined by calling device_get_state(9). SEE ALSO
devclass(9), driver(9) AUTHORS
This manual page was written by Doug Rabson. BSD
June 16, 1998 BSD
Man Page