blob: 19e97452bda4f025266e77fb9c6526362a0e956a [file] [log] [blame]
Masahiro Yamadacc85b7b2015-07-26 02:46:26 +09001#
2# Video configuration
3#
4
5menu "Graphics support"
6
Simon Glass623d28f2016-01-18 19:52:15 -07007config DM_VIDEO
8 bool "Enable driver model support for LCD/video"
9 depends on DM
10 help
11 This enables driver model for LCD and video devices. These support
12 a bitmap display of various sizes and depths which can be drawn on
13 to display a command-line console or splash screen. Enabling this
14 option compiles in the video uclass and routes all LCD/video access
15 through this.
16
17config VIDEO_BPP8
18 bool "Support 8-bit-per-pixel displays"
19 depends on DM_VIDEO
20 default y if DM_VIDEO
21 help
22 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
23 Enabling this will include code to support this display. Without
24 this option, such displays will not be supported and console output
25 will be empty.
26
27config VIDEO_BPP16
28 bool "Support 16-bit-per-pixel displays"
29 depends on DM_VIDEO
30 default y if DM_VIDEO
31 help
32 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
33 Enabling this will include code to support this display. Without
34 this option, such displays will not be supported and console output
35 will be empty.
36
37config VIDEO_BPP32
38 bool "Support 32-bit-per-pixel displays"
39 depends on DM_VIDEO
40 default y if DM_VIDEO
41 help
42 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
43 Enabling this will include code to support this display. Without
44 this option, such displays will not be supported and console output
45 will be empty.
46
Simon Glass6e0721d2016-01-22 21:53:37 +010047config CONSOLE_NORMAL
48 bool "Support a simple text console"
49 depends on DM_VIDEO
50 default y if DM_VIDEO
51 help
52 Support drawing text on the frame buffer console so that it can be
53 used as a console. Rotation is not supported by this driver (see
54 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
55 for the display.
56
57config CONSOLE_ROTATION
Simon Glass87aae882016-01-18 19:52:19 -070058 bool "Support rotated displays"
59 depends on DM_VIDEO
60 help
61 Sometimes, for example if the display is mounted in portrait
62 mode or even if it's mounted landscape but rotated by 180degree,
63 we need to rotate our content of the display relative to the
64 framebuffer, so that user can read the messages which are
65 printed out. Enable this option to include a text driver which can
66 support this. The rotation is set by the 'rot' parameter in
67 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
68 degrees, 3=270 degrees.
69
Simon Glass2ef353e2016-01-14 18:10:42 -070070config CONSOLE_TRUETYPE
71 bool "Support a console that uses TrueType fonts"
72 depends on DM_VIDEO
73 help
74 TrueTrype fonts can provide outline-drawing capability rather than
75 needing to provide a bitmap for each font and size that is needed.
76 With this option you can adjust the text size and use a variety of
77 fonts. Note that this is noticeably slower than with normal console.
78
79config CONSOLE_TRUETYPE_SIZE
80 int "TrueType font size"
81 depends on CONSOLE_TRUETYPE
82 default 18
83 help
84 This sets the font size for the console. The size is measured in
85 pixels and is the nominal height of a character. Note that fonts
86 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
87 However that measurement depends on the size of your display and
88 there is no standard display density. At present there is not a
89 method to select the display's physical size, which would allow
90 U-Boot to calculate the correct font size.
91
92source "drivers/video/fonts/Kconfig"
93
Simon Glass86f07462016-02-06 14:31:37 -070094config VIDCONSOLE_AS_LCD
95 bool "Use 'vidconsole' when 'lcd' is seen in stdout"
96 depends on DM_VIDEO
97 help
98 This is a work-around for boards which have 'lcd' in their stdout
99 environment variable, but have moved to use driver model for video.
100 In this case the console will no-longer work. While it is possible
101 to update the environment, the breakage may be confusing for users.
102 This option will be removed around the end of 2016.
103
Bin Menga0676be2016-10-09 04:14:16 -0700104config VIDEO_COREBOOT
105 bool "Enable coreboot framebuffer driver support"
106 depends on X86 && SYS_COREBOOT
107 help
108 Turn on this option to enable a framebuffer driver when U-Boot is
109 loaded by coreboot where the graphics device is configured by
110 coreboot already. This can in principle be used with any platform
111 that coreboot supports.
112
Simon Glass42bf3ee2014-12-29 19:32:28 -0700113config VIDEO_VESA
114 bool "Enable VESA video driver support"
Simon Glass42bf3ee2014-12-29 19:32:28 -0700115 default n
116 help
117 Turn on this option to enable a very simple driver which uses vesa
118 to discover the video mode and then provides a frame buffer for use
119 by U-Boot. This can in principle be used with any platform that
120 supports PCI and video cards that support VESA BIOS Extension (VBE).
121
Bin Meng072b79d2015-05-11 07:36:29 +0800122config FRAMEBUFFER_SET_VESA_MODE
123 bool "Set framebuffer graphics resolution"
Simon Glassdec49b72016-03-11 22:07:30 -0700124 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
Bin Meng072b79d2015-05-11 07:36:29 +0800125 help
126 Set VESA/native framebuffer mode (needed for bootsplash and graphical
127 framebuffer console)
128
129choice
130 prompt "framebuffer graphics resolution"
131 default FRAMEBUFFER_VESA_MODE_117
132 depends on FRAMEBUFFER_SET_VESA_MODE
133 help
134 This option sets the resolution used for the U-Boot framebuffer (and
135 bootsplash screen).
136
137config FRAMEBUFFER_VESA_MODE_100
138 bool "640x400 256-color"
139
140config FRAMEBUFFER_VESA_MODE_101
141 bool "640x480 256-color"
142
143config FRAMEBUFFER_VESA_MODE_102
144 bool "800x600 16-color"
145
146config FRAMEBUFFER_VESA_MODE_103
147 bool "800x600 256-color"
148
149config FRAMEBUFFER_VESA_MODE_104
150 bool "1024x768 16-color"
151
152config FRAMEBUFFER_VESA_MODE_105
Bin Meng932adc62015-08-09 23:26:59 -0700153 bool "1024x768 256-color"
Bin Meng072b79d2015-05-11 07:36:29 +0800154
155config FRAMEBUFFER_VESA_MODE_106
156 bool "1280x1024 16-color"
157
158config FRAMEBUFFER_VESA_MODE_107
159 bool "1280x1024 256-color"
160
161config FRAMEBUFFER_VESA_MODE_108
162 bool "80x60 text"
163
164config FRAMEBUFFER_VESA_MODE_109
165 bool "132x25 text"
166
167config FRAMEBUFFER_VESA_MODE_10A
168 bool "132x43 text"
169
170config FRAMEBUFFER_VESA_MODE_10B
171 bool "132x50 text"
172
173config FRAMEBUFFER_VESA_MODE_10C
174 bool "132x60 text"
175
176config FRAMEBUFFER_VESA_MODE_10D
177 bool "320x200 32k-color (1:5:5:5)"
178
179config FRAMEBUFFER_VESA_MODE_10E
180 bool "320x200 64k-color (5:6:5)"
181
182config FRAMEBUFFER_VESA_MODE_10F
183 bool "320x200 16.8M-color (8:8:8)"
184
185config FRAMEBUFFER_VESA_MODE_110
186 bool "640x480 32k-color (1:5:5:5)"
187
188config FRAMEBUFFER_VESA_MODE_111
189 bool "640x480 64k-color (5:6:5)"
190
191config FRAMEBUFFER_VESA_MODE_112
192 bool "640x480 16.8M-color (8:8:8)"
193
194config FRAMEBUFFER_VESA_MODE_113
195 bool "800x600 32k-color (1:5:5:5)"
196
197config FRAMEBUFFER_VESA_MODE_114
198 bool "800x600 64k-color (5:6:5)"
199
200config FRAMEBUFFER_VESA_MODE_115
201 bool "800x600 16.8M-color (8:8:8)"
202
203config FRAMEBUFFER_VESA_MODE_116
204 bool "1024x768 32k-color (1:5:5:5)"
205
206config FRAMEBUFFER_VESA_MODE_117
207 bool "1024x768 64k-color (5:6:5)"
208
209config FRAMEBUFFER_VESA_MODE_118
210 bool "1024x768 16.8M-color (8:8:8)"
211
212config FRAMEBUFFER_VESA_MODE_119
213 bool "1280x1024 32k-color (1:5:5:5)"
214
215config FRAMEBUFFER_VESA_MODE_11A
216 bool "1280x1024 64k-color (5:6:5)"
217
218config FRAMEBUFFER_VESA_MODE_11B
219 bool "1280x1024 16.8M-color (8:8:8)"
220
221config FRAMEBUFFER_VESA_MODE_USER
222 bool "Manually select VESA mode"
223
224endchoice
225
226# Map the config names to an integer (KB).
227config FRAMEBUFFER_VESA_MODE
228 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
229 hex
230 default 0x100 if FRAMEBUFFER_VESA_MODE_100
231 default 0x101 if FRAMEBUFFER_VESA_MODE_101
232 default 0x102 if FRAMEBUFFER_VESA_MODE_102
233 default 0x103 if FRAMEBUFFER_VESA_MODE_103
234 default 0x104 if FRAMEBUFFER_VESA_MODE_104
235 default 0x105 if FRAMEBUFFER_VESA_MODE_105
236 default 0x106 if FRAMEBUFFER_VESA_MODE_106
237 default 0x107 if FRAMEBUFFER_VESA_MODE_107
238 default 0x108 if FRAMEBUFFER_VESA_MODE_108
239 default 0x109 if FRAMEBUFFER_VESA_MODE_109
240 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
241 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
242 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
243 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
244 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
245 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
246 default 0x110 if FRAMEBUFFER_VESA_MODE_110
247 default 0x111 if FRAMEBUFFER_VESA_MODE_111
248 default 0x112 if FRAMEBUFFER_VESA_MODE_112
249 default 0x113 if FRAMEBUFFER_VESA_MODE_113
250 default 0x114 if FRAMEBUFFER_VESA_MODE_114
251 default 0x115 if FRAMEBUFFER_VESA_MODE_115
252 default 0x116 if FRAMEBUFFER_VESA_MODE_116
253 default 0x117 if FRAMEBUFFER_VESA_MODE_117
254 default 0x118 if FRAMEBUFFER_VESA_MODE_118
255 default 0x119 if FRAMEBUFFER_VESA_MODE_119
256 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
257 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
258 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
259
Hans de Goededfc1efe2015-08-08 16:03:29 +0200260config VIDEO_LCD_ANX9804
261 bool "ANX9804 bridge chip"
262 default n
263 ---help---
264 Support for the ANX9804 bridge chip, which can take pixel data coming
265 from a parallel LCD interface and translate it on the fy into a DP
266 interface for driving eDP TFT displays. It uses I2C for configuration.
267
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200268config VIDEO_LCD_SSD2828
269 bool "SSD2828 bridge chip"
270 default n
271 ---help---
272 Support for the SSD2828 bridge chip, which can take pixel data coming
273 from a parallel LCD interface and translate it on the fly into MIPI DSI
274 interface for driving a MIPI compatible LCD panel. It uses SPI for
275 configuration.
276
277config VIDEO_LCD_SSD2828_TX_CLK
278 int "SSD2828 TX_CLK frequency (in MHz)"
279 depends on VIDEO_LCD_SSD2828
Siarhei Siamashka61fb91f2015-01-19 05:23:35 +0200280 default 0
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200281 ---help---
282 The frequency of the crystal, which is clocking SSD2828. It may be
283 anything in the 8MHz-30MHz range and the exact value should be
284 retrieved from the board schematics. Or in the case of Allwinner
285 hardware, it can be usually found as 'lcd_xtal_freq' variable in
Siarhei Siamashka61fb91f2015-01-19 05:23:35 +0200286 FEX files. It can be also set to 0 for selecting PCLK from the
287 parallel LCD interface instead of TX_CLK as the PLL clock source.
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200288
289config VIDEO_LCD_SSD2828_RESET
290 string "RESET pin of SSD2828"
291 depends on VIDEO_LCD_SSD2828
292 default ""
293 ---help---
294 The reset pin of SSD2828 chip. This takes a string in the format
295 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
296
Hans de Goedec0482032015-01-20 09:22:26 +0100297config VIDEO_LCD_HITACHI_TX18D42VM
298 bool "Hitachi tx18d42vm LVDS LCD panel support"
299 depends on VIDEO
300 default n
301 ---help---
302 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
303 lcd controller which needs to be initialized over SPI, once that is
304 done they work like a regular LVDS panel.
305
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200306config VIDEO_LCD_SPI_CS
307 string "SPI CS pin for LCD related config job"
Hans de Goedec0482032015-01-20 09:22:26 +0100308 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200309 default ""
310 ---help---
311 This is one of the SPI communication pins, involved in setting up a
312 working LCD configuration. The exact role of SPI may differ for
313 different hardware setups. The option takes a string in the format
314 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
315
316config VIDEO_LCD_SPI_SCLK
317 string "SPI SCLK pin for LCD related config job"
Hans de Goedec0482032015-01-20 09:22:26 +0100318 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200319 default ""
320 ---help---
321 This is one of the SPI communication pins, involved in setting up a
322 working LCD configuration. The exact role of SPI may differ for
323 different hardware setups. The option takes a string in the format
324 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
325
326config VIDEO_LCD_SPI_MOSI
327 string "SPI MOSI pin for LCD related config job"
Hans de Goedec0482032015-01-20 09:22:26 +0100328 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
Siarhei Siamashka4c19cf22015-01-19 05:23:32 +0200329 default ""
330 ---help---
331 This is one of the SPI communication pins, involved in setting up a
332 working LCD configuration. The exact role of SPI may differ for
333 different hardware setups. The option takes a string in the format
334 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
335
336config VIDEO_LCD_SPI_MISO
337 string "SPI MISO pin for LCD related config job (optional)"
338 depends on VIDEO_LCD_SSD2828
339 default ""
340 ---help---
341 This is one of the SPI communication pins, involved in setting up a
342 working LCD configuration. The exact role of SPI may differ for
343 different hardware setups. If wired up, this pin may provide additional
344 useful functionality. Such as bi-directional communication with the
345 hardware and LCD panel id retrieval (if the panel can report it). The
346 option takes a string in the format understood by 'name_to_gpio'
347 function, e.g. PH1 for pin 1 of port H.
Simon Glass06679ad2015-04-14 21:03:38 -0600348
Stefan Roeseab91fd52016-01-20 08:13:28 +0100349config VIDEO_MVEBU
350 bool "Armada XP LCD controller"
351 default n
352 ---help---
353 Support for the LCD controller integrated in the Marvell
354 Armada XP SoC.
355
Anatolij Gustschin4601eb42016-01-25 17:17:22 +0100356config I2C_EDID
357 bool "Enable EDID library"
358 depends on DM_I2C
359 default n
360 help
361 This enables library for accessing EDID data from an LCD panel.
362
Simon Glass7d3d7762016-01-21 19:45:00 -0700363config DISPLAY
364 bool "Enable Display support"
365 depends on DM
Anatolij Gustschin4601eb42016-01-25 17:17:22 +0100366 default n
367 select I2C_EDID
Simon Glass06679ad2015-04-14 21:03:38 -0600368 help
Simon Glass7d3d7762016-01-21 19:45:00 -0700369 This supports drivers that provide a display, such as eDP (Embedded
370 DisplayPort) and HDMI (High Definition Multimedia Interface).
371 The devices provide a simple interface to start up the display,
372 read display information and enable it.
Simon Glass3ef2a722015-04-14 21:03:42 -0600373
Songjun Wu72ac56a2017-04-11 16:33:30 +0800374config ATMEL_HLCD
375 bool "Enable ATMEL video support using HLCDC"
376 depends on DM_VIDEO
377 help
378 HLCDC supports video output to an attached LCD panel.
379
Simon Glassdec49b72016-03-11 22:07:30 -0700380config VIDEO_BROADWELL_IGD
381 bool "Enable Intel Broadwell integrated graphics device"
382 depends on X86
383 help
Simon Glassa3fdd002016-10-05 20:42:14 -0600384 This enables support for integrated graphics on Intel broadwell
Simon Glassdec49b72016-03-11 22:07:30 -0700385 devices. Initialisation is mostly performed by a VGA boot ROM, with
386 some setup handled by U-Boot itself. The graphics adaptor works as
387 a VESA device and supports LCD panels, eDP and LVDS outputs.
388 Configuration of most aspects of device operation is performed using
389 a special tool which configures the VGA ROM, but the graphics
390 resolution can be selected in U-Boot.
391
Simon Glass03f2a512016-10-05 20:42:15 -0600392config VIDEO_IVYBRIDGE_IGD
393 bool "Enable Intel Ivybridge integration graphics support"
394 depends on X86
395 help
396 This enables support for integrated graphics on Intel ivybridge
397 devices. Initialisation is mostly performed by a VGA boot ROM, with
398 some setup handled by U-Boot itself. The graphics adaptor works as
399 a VESA device and supports LCD panels, eDP and LVDS outputs.
400 Configuration of most aspects of device operation is performed using
401 a special tool which configures the VGA ROM, but the graphics
402 resolution can be selected in U-Boot.
403
Sanchayan Maitye15479b2017-04-11 11:12:09 +0530404config VIDEO_FSL_DCU_FB
405 bool "Enable Freescale Display Control Unit"
406 depends on VIDEO
407 help
408 This enables support for Freescale Display Control Unit (DCU4)
409 module found on Freescale Vybrid and QorIQ family of SoCs.
410
Stefan Agnerec954232017-04-11 11:12:10 +0530411config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
412 int "Freescale DCU framebuffer size"
413 depends on VIDEO_FSL_DCU_FB
414 default 4194304
415 help
416 Set maximum framebuffer size to be used for Freescale Display
417 Controller Unit (DCU4).
418
Simon Glass0139ae62016-01-21 19:45:03 -0700419config VIDEO_ROCKCHIP
420 bool "Enable Rockchip video support"
421 depends on DM_VIDEO
422 help
423 Rockchip SoCs provide video output capabilities for High-Definition
424 Multimedia Interface (HDMI), Low-voltage Differential Signalling
425 (LVDS), embedded DisplayPort (eDP) and Display Serial Interface
426 (DSI). This driver supports the on-chip video output device, and
427 targets the Rockchip RK3288.
428
Simon Glass161eea72016-01-18 19:52:24 -0700429config VIDEO_SANDBOX_SDL
430 bool "Enable sandbox video console using SDL"
431 depends on SANDBOX
432 help
433 When using sandbox you can enable an emulated LCD display which
434 appears as an SDL (Simple DirectMedia Layer) window. This is a
435 console device and can display stdout output. Within U-Boot is is
436 a normal bitmap display and can display images as well as text.
437
Simon Glass89c03462016-01-30 16:37:51 -0700438config VIDEO_TEGRA20
439 bool "Enable LCD support on Tegra20"
Simon Glass54832f22016-01-30 16:37:54 -0700440 depends on OF_CONTROL
Simon Glass89c03462016-01-30 16:37:51 -0700441 help
442 Tegra20 supports video output to an attached LCD panel as well as
443 other options such as HDMI. Only the LCD is supported in U-Boot.
444 This option enables this support which can be used on devices which
445 have an LCD display connected.
446
Simon Glass3ef2a722015-04-14 21:03:42 -0600447config VIDEO_TEGRA124
448 bool "Enable video support on Tegra124"
Simon Glassfad72182016-01-30 16:37:50 -0700449 depends on DM_VIDEO
Simon Glass3ef2a722015-04-14 21:03:42 -0600450 help
451 Tegra124 supports many video output options including eDP and
452 HDMI. At present only eDP is supported by U-Boot. This option
453 enables this support which can be used on devices which
454 have an eDP display connected.
Simon Glass7cf17572015-07-02 18:16:08 -0600455
456source "drivers/video/bridge/Kconfig"
Masahiro Yamadacc85b7b2015-07-26 02:46:26 +0900457
Simon Glasse9d797a2016-10-17 20:12:40 -0600458config VIDEO
459 bool "Enable legacy video support"
460 depends on !DM_VIDEO
461 help
462 Define this for video support, without using driver model. Some
463 drivers use this because they are not yet converted to driver
464 model. Video drivers typically provide a colour text console and
465 cursor.
466
Jagan Tekif36b5942016-12-06 00:00:54 +0100467config VIDEO_IPUV3
468 bool "i.MX IPUv3 Core video support"
469 depends on VIDEO && MX6
470 help
471 This enables framebuffer driver for i.MX processors working
472 on the IPUv3(Image Processing Unit) internal graphic processor.
473
Simon Glasse64c7242016-10-17 20:12:41 -0600474config CFB_CONSOLE
475 bool "Enable colour frame buffer console"
476 depends on VIDEO
477 default y if VIDEO
478 help
479 Enables the colour frame buffer driver. This supports colour
480 output on a bitmap display from an in-memory frame buffer.
481 Several colour devices are supported along with various options to
482 adjust the supported features. The driver is implemented in
483 cfb_console.c
484
485 The following defines are needed (cf. smiLynxEM, i8042)
486 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
487 (default big endian)
488 VIDEO_HW_RECTFILL graphic chip supports
489 rectangle fill (cf. smiLynxEM)
490 VIDEO_HW_BITBLT graphic chip supports
491 bit-blit (cf. smiLynxEM)
492 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
493 VIDEO_VISIBLE_ROWS visible pixel rows
494 VIDEO_PIXEL_SIZE bytes per pixel
495 VIDEO_DATA_FORMAT graphic data format
496 (0-5, cf. cfb_console.c)
497 VIDEO_FB_ADRS framebuffer address
498 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
499 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
500 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
501 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
502 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
503 for logo. Requires CONFIG_VIDEO_LOGO
504 CONFIG_CONSOLE_EXTRA_INFO
505 additional board info beside
506 the logo
507 CONFIG_HIDE_LOGO_VERSION
508 do not display bootloader
509 version string
510
511 When CONFIG_CFB_CONSOLE is defined, the video console is the
512 default console. The serial console can be forced by setting the
513 environment 'console=serial'.
514
Simon Glass8d0efc12016-10-17 20:12:42 -0600515config CFB_CONSOLE_ANSI
516 bool "Support ANSI escape sequences"
517 depends on CFB_CONSOLE
518 help
519 This allows the colour buffer frame buffer driver to support
520 a limited number of ANSI escape sequences (cursor control,
521 erase functions and limited graphics rendition control). Normal
522 output from U-Boot will pass through this filter.
523
Simon Glassdcff6922016-10-17 20:12:49 -0600524config VGA_AS_SINGLE_DEVICE
525 bool "Set the video as an output-only device"
526 depends on CFB_CONSOLE
527 default y
528 help
529 If enable the framebuffer device will be initialized as an
530 output-only device. The Keyboard driver will not be set up. This
531 may be used if you have no keyboard device, or more than one
532 (USB Keyboard, AT Keyboard).
533
Simon Glass706605f2016-10-17 20:12:51 -0600534config VIDEO_SW_CURSOR
535 bool "Enable a software cursor"
536 depends on CFB_CONSOLE
537 default y if CFB_CONSOLE
538 help
539 This draws a cursor after the last character. No blinking is
540 provided. This makes it possible to see the current cursor
541 position when entering text on the console. It is recommended to
542 enable this.
543
Simon Glass5a772352016-10-17 20:12:53 -0600544config CONSOLE_EXTRA_INFO
545 bool "Display additional board information"
546 depends on CFB_CONSOLE
547 help
548 Display additional board information strings that normally go to
549 the serial port. When this option is enabled, a board-specific
550 function video_get_info_str() is called to get the string for
551 each line of the display. The function should return the string,
552 which can be empty if there is nothing to display for that line.
553
Simon Glassd76f29a2016-10-17 20:12:57 -0600554config CONSOLE_SCROLL_LINES
555 int "Number of lines to scroll the console by"
556 depends on CFB_CONSOLE || DM_VIDEO || LCD
557 default 1
558 help
559 When the console need to be scrolled, this is the number of
560 lines to scroll by. It defaults to 1. Increasing this makes the
561 console jump but can help speed up operation when scrolling
562 is slow.
563
Simon Glass1ad7b452016-10-17 20:12:43 -0600564config VIDEO_CT69000
565 bool "Enable Chips & Technologies 69000 video driver"
566 depends on VIDEO
567 help
568 This enables a frame buffer driver for the Chips & Technologies
569 ct69000, a fairly old graphics device (circa 2000) which is used
570 on some hardware. It operates over the ISA bus, and supports
571 some acceleration features.
572
573 For the CT69000 and SMI_LYNXEM drivers, videomode is
574 selected via environment 'videomode'. Two different ways
575 are possible:
576 - "videomode=num" 'num' is a standard LiLo mode numbers.
577 Following standard modes are supported (* is default):
578
579 Colors 640x480 800x600 1024x768 1152x864 1280x1024
580 -------------+---------------------------------------------
581 8 bits | 0x301* 0x303 0x305 0x161 0x307
582 15 bits | 0x310 0x313 0x316 0x162 0x319
583 16 bits | 0x311 0x314 0x317 0x163 0x31A
584 24 bits | 0x312 0x315 0x318 ? 0x31B
585 -------------+---------------------------------------------
586 (i.e. setenv videomode 317; saveenv; reset;)
587
588 - "videomode=bootargs" all the video parameters are parsed
589 from the bootargs. (See drivers/video/videomodes.c)
590
Simon Glass884889d2016-10-17 20:12:44 -0600591config SYS_CONSOLE_BG_COL
592 hex "Background colour"
593 depends on CFB_CONSOLE || VIDEO_CT69000
594 default 0x00
595 help
596 Defines the background colour for the console. The value is from
597 0x00 to 0xff and the meaning depends on the graphics card.
598 Typically, 0x00 means black and 0xff means white. Do not set
599 the background and foreground to the same colour or you will see
600 nothing.
601
602config SYS_CONSOLE_FG_COL
603 hex "Foreground colour"
604 depends on CFB_CONSOLE || VIDEO_CT69000
605 default 0xa0
606 help
607 Defines the foreground colour for the console. The value is from
608 0x00 to 0xff and the meaning depends on the graphics card.
609 Typically, 0x00 means black and 0xff means white. Do not set
610 the background and foreground to the same colour or you will see
611 nothing.
612
Simon Glass169bb3b2016-10-17 20:12:56 -0600613config LCD
614 bool "Enable legacy LCD support"
615 help
616 Define this to enable LCD support (for output to LCD display).
617 You will also need to select an LCD driver using an additional
618 CONFIG option. See the README for details. Drives which have been
619 converted to driver model will instead used CONFIG_DM_VIDEO.
620
Masahiro Yamadacc85b7b2015-07-26 02:46:26 +0900621endmenu