Lines Matching refs:console
5 The framebuffer console (fbcon), as its name implies, is a text
6 console running on top of the framebuffer device. It has the functionality of
7 any standard text console driver, such as the VGA console, with the added
10 In the x86 architecture, the framebuffer console is optional, and
14 What are the features of fbcon? The framebuffer console supports
22 The framebuffer console can be enabled by using your favorite kernel
43 framebuffer console. Depending on the driver, you may get a blanked or
46 will still get a VGA console.
55 Usually, fbcon will automatically take over your console. The notable
61 Depending on the driver, you either get a standard console, or a
62 garbled display, as mentioned above. To get a framebuffer console,
67 You get your standard console. Once the driver is loaded with
68 'modprobe xxxfb', fbcon automatically takes over the console with
74 over the console.
78 The framebuffer console has several, largely unknown, boot options
94 which console. The value '0123' is a sequence that gets repeated until
107 console.
109 Later on, when you want to map the console the to the framebuffer
117 console driver.
119 NOTE: For x86 machines, the standard console is the VGA console which
121 are controlled by the VGA console will be garbled.
125 This option changes the orientation angle of the console display. The
137 - rotate - rotate the display of the active console
143 NOTE: This is purely console rotation. Any other applications that
145 Actually, the underlying fb driver is totally ignorant of console
159 be preserved until there actually is some text is output to the console.
177 Before going on to how to attach, detach and unload the framebuffer console, an
180 The console layer, as with most subsystems, needs a driver that interfaces with
181 the hardware. Thus, in a VGA console::
183 console ---> VGA driver ---> hardware.
186 from the console layer before unloading the driver. The VGA driver cannot be
187 unloaded if it is still bound to the console layer. (See
188 Documentation/driver-api/console.rst for more information).
190 This is more complicated in the case of the framebuffer console (fbcon),
191 because fbcon is an intermediate layer between the console and the drivers::
193 console ---> fbcon ---> fbdev drivers ---> hardware
196 be unloaded if it's bound to the console layer.
198 So to unload the fbdev drivers, one must first unbind fbcon from the console,
200 the console layer will automatically unbind framebuffer drivers from
204 So, how do we unbind fbcon from the console? Part of the answer is in
205 Documentation/driver-api/console.rst. To summarize:
207 Echo a value to the bind file that represents the framebuffer console
210 echo 1 > /sys/class/vtconsole/vtcon1/bind - attach framebuffer console to
211 console layer
212 echo 0 > /sys/class/vtconsole/vtcon1/bind - detach framebuffer console from
213 console layer
215 If fbcon is detached from the console layer, your boot console driver (which is
254 automatically bind the console, fbcon and the drivers together. Unloading
256 console to bind fbcon.
263 Instead, vgacon will replace the default boot console with dummycon, and you
286 echo <ID> > /sys/class/tty/console/bind
303 framebuffer console driver if you are on an X86 box::