Lines Matching refs:to

5 assigned by the kernel to all the virtual consoles during the boot process.
7 to exist. The system driver is persistent and it can never be unloaded, though
10 The second type has to be explicitly loaded and unloaded. This will be called
20 Modular drivers, from the programmer's point of view, has to call:
22 	 do_take_over_console() - load and bind driver to console layer
32 system which are named vtcon<n> where <n> is an integer from 0 to 15. Thus:
45         read, or acts to bind or unbind the driver to the virtual consoles
46         when written to. The possible values are:
49 	    to unbind
51         1 - means the driver is bound and if echo'ed, commands the driver to
60 	    commanded to bind or unbind
68 	    directly commanded to bind or unbind.
74 hand, will bind the driver to the consoles that are currently occupied by a
84 to KD_GRAPHICS is X.
89 for rebooting the kernel. For regular users who may want to switch from
90 framebuffer console to VGA console and vice versa, this feature also makes
102 give_up_console() is a wrapper to do_unregister_con_driver(), and a driver must
103 be fully unbound for this call to succeed. con_is_bound() will check if the
109 In order for binding to and unbinding from the console to properly work,
113    or do_take_over_console(). do_register_con_driver() will just add the driver to
116    bind to) the console.
123    does not have a complementary call to con->con_startup() so it's up to the
124    driver to check when it's legal to release these resources. Calling
126    false(), then it's safe to release the resources.  This balance has to be
127    ensured because con->con_startup() can be called again when a request to
128    rebind the driver to the console arrives.
135    impossible for the driver to service console requests.  This can happen
140 be made to work correctly.