Lines Matching +full:system +full:- +full:on +full:- +full:module

8 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
9 into the bus with power on.  In most cases, users expect the devices to become
10 immediately usable.  That means the system must do many things, including:
12     - Find a driver that can handle the device.  That may involve
13       loading a kernel module; newer drivers can use module-init-tools
16     - Bind a driver to that device.  Bus frameworks do that using a
19     - Tell other subsystems to configure the new device.  Print
21       partitions mounted, and so on.  In some cases these will
22       be driver-specific actions.
30 Those triggered actions must support a system's administrative policies;
34 Because some of those actions rely on information about drivers (metadata)
36 you get the best hotplugging when you configure a highly modular system.
54 	http://linux-hotplug.sourceforge.net
63 are added or removed from system.  The invocation is done by the kernel
80 user mode daemon to detect changes in system configuration.
83 modules, and can invoke driver-specific setup scripts.  The newest ones
84 leverage USB module-init-tools support.  Later agents might unload drivers.
90 Current versions of module-init-tools will create a ``modules.usbmap`` file
118 	{ } /* end with an all-zeroes entry */
123 well as to the module management subsystem.  Not all, though: some driver