Lines Matching refs:the

5 assigned by the kernel to all the virtual consoles during the boot process.
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
15 call do_take_over_console() will succeed in the takeover regardless of the type
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.
20 Modular drivers, from the programmer's point of view, has to call:
25 In newer kernels, the following are also available:
30 If sysfs is enabled, the contents of /sys/class/vtconsole can be
31 examined. This shows the console backends currently registered by the
44      1. bind - this is a read/write file. It shows the status of the driver if
45         read, or acts to bind or unbind the driver to the virtual consoles
48 	0 - means the driver is not bound and if echo'ed, commands the driver
51         1 - means the driver is bound and if echo'ed, commands the driver to
54      2. name - read-only file. Shows the name of the driver in this format:
62 	    'VGA+' is the name of the driver
72 When unbinding, the modular driver is detached first, and then the system
73 driver takes over the consoles vacated by the driver. Binding, on the other
74 hand, will bind the driver to the consoles that are currently occupied by a
82 NOTE2: If any of the virtual consoles are in KD_GRAPHICS mode, then binding or
83 unbinding will not succeed. An example of an application that sets the console
87 developers. By unbinding the driver from the console layer, one can unload the
88 driver, make changes, recompile, reload and rebind the driver without any need
89 for rebooting the kernel. For regular users who may want to switch from
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
114    the console's internal list. It won't take over the
116    bind to) the console.
121 3. All resources allocated in con->con_startup() must be released when the
123    does not have a complementary call to con->con_startup() so it's up to the
125    con_is_bound() in con->con_deinit() will help.  If the call returned
126    false(), then it's safe to release the resources.  This balance has to be
128    rebind the driver to the console arrives.
130 4. Upon exit of the driver, ensure that the driver is totally unbound. If the
131    condition is satisfied, then the driver must call do_unregister_con_driver()
135    impossible for the driver to service console requests.  This can happen
136    with the framebuffer console that suddenly lost all of its drivers.