Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

devctl(8) [freebsd man page]

DEVCTL(8)						    BSD System Manager's Manual 						 DEVCTL(8)

NAME

     devctl -- device control utility

SYNOPSIS

     devctl attach device
     devctl detach [-f] device
     devctl disable [-f] device
     devctl enable device
     devctl suspend device
     devctl resume device
     devctl set driver [-f] device driver

DESCRIPTION

     The devctl utility adjusts the state of individual devices in the kernel's internal device hierarchy.  Each invocation of devctl consists of
     a single command followed by command-specific arguments.  Each command operates on a single device specified via the device argument.  The
     device may be specified either as the name of an existing device or as a bus-specific address.  More details on supported address formats can
     be found in devctl(3).

     The following commands are supported:

     attach device
	     Force the kernel to re-probe the device.  If a suitable driver is found, it is attached to the device.

     detach [-f] device
	     Detach the device from its current device driver.	If the -f flag is specified, the device driver will be detached even if the device
	     is busy.

     disable [-f] device
	     Disable a device.	If the device is currently attached to a device driver, the device driver will be detached from the device, but
	     the device will retain its current name.  If the -f flag is specified, the device driver will be detached even if the device is busy.

     enable device
	     Enable a device.  The device will probe and attach if a suitable device driver is found.  Note that this can re-enable a device dis-
	     abled at boot time via a loader tunable.

     suspend device
	     Suspend a device.	This may include placing the device in a reduced power state.

     resume device
	     Resume a suspended device to a fully working state.

     set driver [-f] device driver
	     Force the device to use a device driver named driver.  If the device is already attached to a device driver and the -f flag is speci-
	     fied, the device will be detached from its current device driver before it is attached to the new device driver.  If the device is
	     already attached to a device driver and the -f flag is not specified, the device will not be changed.

SEE ALSO

     devctl(3), devinfo(8)

HISTORY

     The devctl utility first appeared in FreeBSD 11.0.

BSD
								 February 5, 2015							       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