Lines Matching +full:kernel +full:- +full:policy

8 In hotpluggable busses like USB (and Cardbus PCI), end-users plug devices
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
22       be driver-specific actions.
24 This involves a mix of kernel mode and user mode actions.  Making devices
26 administrator to do them:  the kernel must trigger them, either passively
31 such programs are called "policy agents" here.  Typically they involve
38 Kernel Hotplug Helper (``/sbin/hotplug``)
41 There is a kernel parameter: ``/proc/sys/kernel/hotplug``, which normally
43 which the kernel may invoke at various times.
48 some kernel event.  That name is used as the first key for further event
54 	http://linux-hotplug.sourceforge.net
59 USB Policy Agent
63 are added or removed from system.  The invocation is done by the kernel
82 Currently available policy agent implementations can load drivers for
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
92 files can be used by various user mode policy agents to make sure all the
118 	{ } /* end with an all-zeroes entry */