Lines Matching refs:driver

6 This type will be called 'system driver', and only one system driver is allowed
7 to exist. The system driver is persistent and it can never be unloaded, though
11 'modular driver' by this document. Multiple modular drivers can coexist at
12 any time with each driver sharing the console with other drivers including
13 the system driver. However, modular drivers cannot take over the console
14 that is currently occupied by another modular driver. (Exception: Drivers that
16 of driver occupying the consoles.) They can only take over the console that is
17 occupied by the system driver. In the same token, if the modular driver is
18 released by the console, the system driver will take over.
22 	 do_take_over_console() - load and bind driver to console layer
23 	 give_up_console() - unload driver; it will only work if driver
45      1. bind - this is a read/write file. It shows the status of the driver if
46         read, or acts to bind or unbind the driver to the virtual consoles
49 	0 - means the driver is not bound and if echo'ed, commands the driver
52         1 - means the driver is bound and if echo'ed, commands the driver to
55      2. name - read-only file. Shows the name of the driver in this format:
60 	    '(S)' stands for a (S)ystem driver, i.e., it cannot be directly
63 	    'VGA+' is the name of the driver
68 	    In this case, '(M)' stands for a (M)odular driver, one that can be
73 When unbinding, the modular driver is detached first, and then the system
74 driver takes over the consoles vacated by the driver. Binding, on the other
75 hand, will bind the driver to the consoles that are currently occupied by a
76 system driver.
87 How useful is this feature? This is very useful for console driver
88 developers. By unbinding the driver from the console layer, one can unload the
89 driver, make changes, recompile, reload and rebind the driver without any need
103 give_up_console() is a wrapper to do_unregister_con_driver(), and a driver must
105 driver is bound or not.
107 Guidelines for console driver writers:
114    or do_take_over_console(). do_register_con_driver() will just add the driver
123    driver, which was previously bound, becomes unbound.  The console layer
125    driver to check when it's legal to release these resources. Calling
129    rebind the driver to the console arrives.
131 4. Upon exit of the driver, ensure that the driver is totally unbound. If the
132    condition is satisfied, then the driver must call do_unregister_con_driver()
136    impossible for the driver to service console requests.  This can happen