Lines Matching refs:console

4 	The framebuffer console (fbcon), as its name implies, is a text
5 console running on top of the framebuffer device. It has the functionality of
6 any standard text console driver, such as the VGA console, with the added
9 	 In the x86 architecture, the framebuffer console is optional, and
13 	 What are the features of fbcon?  The framebuffer console supports
20 	The framebuffer console can be enabled by using your favorite kernel
40 framebuffer console.  Depending on the driver, you may get a blanked or
43 will still get a VGA console.
51 	 Usually, fbcon will automatically take over your console. The notable
57 	 Depending on the driver, you either get a standard console, or a
58 	 garbled display, as mentioned above.  To get a framebuffer console,
63 	 You get your standard console.  Once the driver is loaded with
64 	 'modprobe xxxfb', fbcon automatically takes over the console with
70 	 over the console.
74          The framebuffer console has several, largely unknown, boot options
97         which console. The value '0123' is a sequence that gets repeated until
110 	console.
112 	Later on, when you want to map the console the to the framebuffer
120 	console driver.
122 	NOTE: For x86 machines, the standard console is the VGA console which
124 	are controlled by the VGA console will be garbled.
128         This option changes the orientation angle of the console display. The
140 		rotate     - rotate the display of the active console
146 	NOTE: This is purely console rotation.  Any other applications that
148 	Actually, the underlying fb driver is totally ignorant of console
153 Before going on how to attach, detach and unload the framebuffer console, an
156 The console layer, as with most subsystems, needs a driver that interfaces with
157 the hardware. Thus, in a VGA console:
159 console ---> VGA driver ---> hardware.
162 from the console layer before unloading the driver.  The VGA driver cannot be
163 unloaded if it is still bound to the console layer. (See
164 Documentation/console/console.txt for more information).
166 This is more complicated in the case of the framebuffer console (fbcon),
167 because fbcon is an intermediate layer between the console and the drivers:
169 console ---> fbcon ---> fbdev drivers ---> hardware
172 be unloaded if it's bound to the console layer.
174 So to unload the fbdev drivers, one must first unbind fbcon from the console,
176 the console layer will automatically unbind framebuffer drivers from
180 So, how do we unbind fbcon from the console? Part of the answer is in
181 Documentation/console/console.txt. To summarize:
183 Echo a value to the bind file that represents the framebuffer console
186 echo 1 > sys/class/vtconsole/vtcon1/bind - attach framebuffer console to
187                                            console layer
188 echo 0 > sys/class/vtconsole/vtcon1/bind - detach framebuffer console from
189                                            console layer
191 If fbcon is detached from the console layer, your boot console driver (which is
230 automatically bind the console, fbcon and the drivers together. Unloading
232 console to bind fbcon.
239 Instead, vgacon will replace the default boot console with dummycon, and you
261 	echo <ID> > /sys/class/tty/console/bind
279 framebuffer console driver if you are in an X86 box: