1 # 2 # Video configuration 3 # 4 5 menu "Graphics support" 6 7 config 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 17 config BACKLIGHT_PWM 18 bool "Generic PWM based Backlight Driver" 19 depends on DM_VIDEO && DM_PWM 20 default y 21 help 22 If you have a LCD backlight adjustable by PWM, say Y to enable 23 this driver. 24 This driver can be use with "simple-panel" and 25 it understands the standard device tree 26 (leds/backlight/pwm-backlight.txt) 27 28 config BACKLIGHT_GPIO 29 bool "Generic GPIO based Backlight Driver" 30 depends on DM_VIDEO 31 help 32 If you have a LCD backlight adjustable by GPIO, say Y to enable 33 this driver. 34 This driver can be used with "simple-panel" and 35 it understands the standard device tree 36 (leds/backlight/gpio-backlight.txt) 37 38 config VIDEO_BPP8 39 bool "Support 8-bit-per-pixel displays" 40 depends on DM_VIDEO 41 default y if DM_VIDEO 42 help 43 Support drawing text and bitmaps onto a 8-bit-per-pixel display. 44 Enabling this will include code to support this display. Without 45 this option, such displays will not be supported and console output 46 will be empty. 47 48 config VIDEO_BPP16 49 bool "Support 16-bit-per-pixel displays" 50 depends on DM_VIDEO 51 default y if DM_VIDEO 52 help 53 Support drawing text and bitmaps onto a 16-bit-per-pixel display. 54 Enabling this will include code to support this display. Without 55 this option, such displays will not be supported and console output 56 will be empty. 57 58 config VIDEO_BPP32 59 bool "Support 32-bit-per-pixel displays" 60 depends on DM_VIDEO 61 default y if DM_VIDEO 62 help 63 Support drawing text and bitmaps onto a 32-bit-per-pixel display. 64 Enabling this will include code to support this display. Without 65 this option, such displays will not be supported and console output 66 will be empty. 67 68 config VIDEO_ANSI 69 bool "Support ANSI escape sequences in video console" 70 depends on DM_VIDEO 71 default y if DM_VIDEO 72 help 73 Enable ANSI escape sequence decoding for a more fully functional 74 console. 75 76 config CONSOLE_NORMAL 77 bool "Support a simple text console" 78 depends on DM_VIDEO 79 default y if DM_VIDEO 80 help 81 Support drawing text on the frame buffer console so that it can be 82 used as a console. Rotation is not supported by this driver (see 83 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used 84 for the display. 85 86 config CONSOLE_ROTATION 87 bool "Support rotated displays" 88 depends on DM_VIDEO 89 help 90 Sometimes, for example if the display is mounted in portrait 91 mode or even if it's mounted landscape but rotated by 180degree, 92 we need to rotate our content of the display relative to the 93 framebuffer, so that user can read the messages which are 94 printed out. Enable this option to include a text driver which can 95 support this. The rotation is set by the 'rot' parameter in 96 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180 97 degrees, 3=270 degrees. 98 99 config CONSOLE_TRUETYPE 100 bool "Support a console that uses TrueType fonts" 101 depends on DM_VIDEO 102 help 103 TrueTrype fonts can provide outline-drawing capability rather than 104 needing to provide a bitmap for each font and size that is needed. 105 With this option you can adjust the text size and use a variety of 106 fonts. Note that this is noticeably slower than with normal console. 107 108 config CONSOLE_TRUETYPE_SIZE 109 int "TrueType font size" 110 depends on CONSOLE_TRUETYPE 111 default 18 112 help 113 This sets the font size for the console. The size is measured in 114 pixels and is the nominal height of a character. Note that fonts 115 are commonly measured in 'points', being 1/72 inch (about 3.52mm). 116 However that measurement depends on the size of your display and 117 there is no standard display density. At present there is not a 118 method to select the display's physical size, which would allow 119 U-Boot to calculate the correct font size. 120 121 config SYS_WHITE_ON_BLACK 122 bool "Display console as white on a black background" 123 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || TEGRA || X86 124 help 125 Normally the display is black on a white background, Enable this 126 option to invert this, i.e. white on a black background. This can be 127 better in low-light situations or to reduce eye strain in some 128 cases. 129 130 config NO_FB_CLEAR 131 bool "Skip framebuffer clear" 132 help 133 If firmware (whatever loads u-boot) has already put a splash image 134 on screen, you might want to preserve it until whatever u-boot 135 loads takes over the screen. This, for example, can be used to 136 keep splash image on screen until grub graphical boot menu starts. 137 138 source "drivers/video/fonts/Kconfig" 139 140 config VIDCONSOLE_AS_LCD 141 bool "Use 'vidconsole' when 'lcd' is seen in stdout" 142 depends on DM_VIDEO 143 help 144 This is a work-around for boards which have 'lcd' in their stdout 145 environment variable, but have moved to use driver model for video. 146 In this case the console will no-longer work. While it is possible 147 to update the environment, the breakage may be confusing for users. 148 This option will be removed around the end of 2016. 149 150 config VIDEO_COREBOOT 151 bool "Enable coreboot framebuffer driver support" 152 depends on X86 && SYS_COREBOOT 153 help 154 Turn on this option to enable a framebuffer driver when U-Boot is 155 loaded by coreboot where the graphics device is configured by 156 coreboot already. This can in principle be used with any platform 157 that coreboot supports. 158 159 config VIDEO_EFI 160 bool "Enable EFI framebuffer driver support" 161 depends on EFI_STUB 162 help 163 Turn on this option to enable a framebuffeer driver when U-Boot is 164 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where 165 the graphics device is configured by the EFI BIOS already. This can 166 in principle be used with any platform that has an EFI BIOS. 167 168 config VIDEO_VESA 169 bool "Enable VESA video driver support" 170 default n 171 help 172 Turn on this option to enable a very simple driver which uses vesa 173 to discover the video mode and then provides a frame buffer for use 174 by U-Boot. This can in principle be used with any platform that 175 supports PCI and video cards that support VESA BIOS Extension (VBE). 176 177 config FRAMEBUFFER_SET_VESA_MODE 178 bool "Set framebuffer graphics resolution" 179 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD 180 help 181 Set VESA/native framebuffer mode (needed for bootsplash and graphical 182 framebuffer console) 183 184 choice 185 prompt "framebuffer graphics resolution" 186 default FRAMEBUFFER_VESA_MODE_118 187 depends on FRAMEBUFFER_SET_VESA_MODE 188 help 189 This option sets the resolution used for the U-Boot framebuffer (and 190 bootsplash screen). 191 192 config FRAMEBUFFER_VESA_MODE_100 193 bool "640x400 256-color" 194 195 config FRAMEBUFFER_VESA_MODE_101 196 bool "640x480 256-color" 197 198 config FRAMEBUFFER_VESA_MODE_102 199 bool "800x600 16-color" 200 201 config FRAMEBUFFER_VESA_MODE_103 202 bool "800x600 256-color" 203 204 config FRAMEBUFFER_VESA_MODE_104 205 bool "1024x768 16-color" 206 207 config FRAMEBUFFER_VESA_MODE_105 208 bool "1024x768 256-color" 209 210 config FRAMEBUFFER_VESA_MODE_106 211 bool "1280x1024 16-color" 212 213 config FRAMEBUFFER_VESA_MODE_107 214 bool "1280x1024 256-color" 215 216 config FRAMEBUFFER_VESA_MODE_108 217 bool "80x60 text" 218 219 config FRAMEBUFFER_VESA_MODE_109 220 bool "132x25 text" 221 222 config FRAMEBUFFER_VESA_MODE_10A 223 bool "132x43 text" 224 225 config FRAMEBUFFER_VESA_MODE_10B 226 bool "132x50 text" 227 228 config FRAMEBUFFER_VESA_MODE_10C 229 bool "132x60 text" 230 231 config FRAMEBUFFER_VESA_MODE_10D 232 bool "320x200 32k-color (1:5:5:5)" 233 234 config FRAMEBUFFER_VESA_MODE_10E 235 bool "320x200 64k-color (5:6:5)" 236 237 config FRAMEBUFFER_VESA_MODE_10F 238 bool "320x200 16.8M-color (8:8:8)" 239 240 config FRAMEBUFFER_VESA_MODE_110 241 bool "640x480 32k-color (1:5:5:5)" 242 243 config FRAMEBUFFER_VESA_MODE_111 244 bool "640x480 64k-color (5:6:5)" 245 246 config FRAMEBUFFER_VESA_MODE_112 247 bool "640x480 16.8M-color (8:8:8)" 248 249 config FRAMEBUFFER_VESA_MODE_113 250 bool "800x600 32k-color (1:5:5:5)" 251 252 config FRAMEBUFFER_VESA_MODE_114 253 bool "800x600 64k-color (5:6:5)" 254 255 config FRAMEBUFFER_VESA_MODE_115 256 bool "800x600 16.8M-color (8:8:8)" 257 258 config FRAMEBUFFER_VESA_MODE_116 259 bool "1024x768 32k-color (1:5:5:5)" 260 261 config FRAMEBUFFER_VESA_MODE_117 262 bool "1024x768 64k-color (5:6:5)" 263 264 config FRAMEBUFFER_VESA_MODE_118 265 bool "1024x768 16.8M-color (8:8:8)" 266 267 config FRAMEBUFFER_VESA_MODE_119 268 bool "1280x1024 32k-color (1:5:5:5)" 269 270 config FRAMEBUFFER_VESA_MODE_11A 271 bool "1280x1024 64k-color (5:6:5)" 272 273 config FRAMEBUFFER_VESA_MODE_11B 274 bool "1280x1024 16.8M-color (8:8:8)" 275 276 config FRAMEBUFFER_VESA_MODE_USER 277 bool "Manually select VESA mode" 278 279 endchoice 280 281 # Map the config names to an integer (KB). 282 config FRAMEBUFFER_VESA_MODE 283 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER 284 hex 285 default 0x100 if FRAMEBUFFER_VESA_MODE_100 286 default 0x101 if FRAMEBUFFER_VESA_MODE_101 287 default 0x102 if FRAMEBUFFER_VESA_MODE_102 288 default 0x103 if FRAMEBUFFER_VESA_MODE_103 289 default 0x104 if FRAMEBUFFER_VESA_MODE_104 290 default 0x105 if FRAMEBUFFER_VESA_MODE_105 291 default 0x106 if FRAMEBUFFER_VESA_MODE_106 292 default 0x107 if FRAMEBUFFER_VESA_MODE_107 293 default 0x108 if FRAMEBUFFER_VESA_MODE_108 294 default 0x109 if FRAMEBUFFER_VESA_MODE_109 295 default 0x10A if FRAMEBUFFER_VESA_MODE_10A 296 default 0x10B if FRAMEBUFFER_VESA_MODE_10B 297 default 0x10C if FRAMEBUFFER_VESA_MODE_10C 298 default 0x10D if FRAMEBUFFER_VESA_MODE_10D 299 default 0x10E if FRAMEBUFFER_VESA_MODE_10E 300 default 0x10F if FRAMEBUFFER_VESA_MODE_10F 301 default 0x110 if FRAMEBUFFER_VESA_MODE_110 302 default 0x111 if FRAMEBUFFER_VESA_MODE_111 303 default 0x112 if FRAMEBUFFER_VESA_MODE_112 304 default 0x113 if FRAMEBUFFER_VESA_MODE_113 305 default 0x114 if FRAMEBUFFER_VESA_MODE_114 306 default 0x115 if FRAMEBUFFER_VESA_MODE_115 307 default 0x116 if FRAMEBUFFER_VESA_MODE_116 308 default 0x117 if FRAMEBUFFER_VESA_MODE_117 309 default 0x118 if FRAMEBUFFER_VESA_MODE_118 310 default 0x119 if FRAMEBUFFER_VESA_MODE_119 311 default 0x11A if FRAMEBUFFER_VESA_MODE_11A 312 default 0x11B if FRAMEBUFFER_VESA_MODE_11B 313 default 0x117 if FRAMEBUFFER_VESA_MODE_USER 314 315 config VIDEO_LCD_ANX9804 316 bool "ANX9804 bridge chip" 317 default n 318 ---help--- 319 Support for the ANX9804 bridge chip, which can take pixel data coming 320 from a parallel LCD interface and translate it on the fy into a DP 321 interface for driving eDP TFT displays. It uses I2C for configuration. 322 323 config VIDEO_LCD_SSD2828 324 bool "SSD2828 bridge chip" 325 default n 326 ---help--- 327 Support for the SSD2828 bridge chip, which can take pixel data coming 328 from a parallel LCD interface and translate it on the fly into MIPI DSI 329 interface for driving a MIPI compatible LCD panel. It uses SPI for 330 configuration. 331 332 config VIDEO_LCD_SSD2828_TX_CLK 333 int "SSD2828 TX_CLK frequency (in MHz)" 334 depends on VIDEO_LCD_SSD2828 335 default 0 336 ---help--- 337 The frequency of the crystal, which is clocking SSD2828. It may be 338 anything in the 8MHz-30MHz range and the exact value should be 339 retrieved from the board schematics. Or in the case of Allwinner 340 hardware, it can be usually found as 'lcd_xtal_freq' variable in 341 FEX files. It can be also set to 0 for selecting PCLK from the 342 parallel LCD interface instead of TX_CLK as the PLL clock source. 343 344 config VIDEO_LCD_SSD2828_RESET 345 string "RESET pin of SSD2828" 346 depends on VIDEO_LCD_SSD2828 347 default "" 348 ---help--- 349 The reset pin of SSD2828 chip. This takes a string in the format 350 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 351 352 config VIDEO_LCD_HITACHI_TX18D42VM 353 bool "Hitachi tx18d42vm LVDS LCD panel support" 354 depends on VIDEO 355 default n 356 ---help--- 357 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a 358 lcd controller which needs to be initialized over SPI, once that is 359 done they work like a regular LVDS panel. 360 361 config VIDEO_LCD_SPI_CS 362 string "SPI CS pin for LCD related config job" 363 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM 364 default "" 365 ---help--- 366 This is one of the SPI communication pins, involved in setting up a 367 working LCD configuration. The exact role of SPI may differ for 368 different hardware setups. The option takes a string in the format 369 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 370 371 config VIDEO_LCD_SPI_SCLK 372 string "SPI SCLK pin for LCD related config job" 373 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM 374 default "" 375 ---help--- 376 This is one of the SPI communication pins, involved in setting up a 377 working LCD configuration. The exact role of SPI may differ for 378 different hardware setups. The option takes a string in the format 379 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 380 381 config VIDEO_LCD_SPI_MOSI 382 string "SPI MOSI pin for LCD related config job" 383 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM 384 default "" 385 ---help--- 386 This is one of the SPI communication pins, involved in setting up a 387 working LCD configuration. The exact role of SPI may differ for 388 different hardware setups. The option takes a string in the format 389 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 390 391 config VIDEO_LCD_SPI_MISO 392 string "SPI MISO pin for LCD related config job (optional)" 393 depends on VIDEO_LCD_SSD2828 394 default "" 395 ---help--- 396 This is one of the SPI communication pins, involved in setting up a 397 working LCD configuration. The exact role of SPI may differ for 398 different hardware setups. If wired up, this pin may provide additional 399 useful functionality. Such as bi-directional communication with the 400 hardware and LCD panel id retrieval (if the panel can report it). The 401 option takes a string in the format understood by 'name_to_gpio' 402 function, e.g. PH1 for pin 1 of port H. 403 404 config VIDEO_MVEBU 405 bool "Armada XP LCD controller" 406 default n 407 ---help--- 408 Support for the LCD controller integrated in the Marvell 409 Armada XP SoC. 410 411 config I2C_EDID 412 bool "Enable EDID library" 413 depends on DM_I2C 414 default n 415 help 416 This enables library for accessing EDID data from an LCD panel. 417 418 config DISPLAY 419 bool "Enable Display support" 420 depends on DM 421 default n 422 select I2C_EDID 423 help 424 This supports drivers that provide a display, such as eDP (Embedded 425 DisplayPort) and HDMI (High Definition Multimedia Interface). 426 The devices provide a simple interface to start up the display, 427 read display information and enable it. 428 429 config ATMEL_HLCD 430 bool "Enable ATMEL video support using HLCDC" 431 depends on DM_VIDEO 432 help 433 HLCDC supports video output to an attached LCD panel. 434 435 config VIDEO_BROADWELL_IGD 436 bool "Enable Intel Broadwell integrated graphics device" 437 depends on X86 438 help 439 This enables support for integrated graphics on Intel broadwell 440 devices. Initialisation is mostly performed by a VGA boot ROM, with 441 some setup handled by U-Boot itself. The graphics adaptor works as 442 a VESA device and supports LCD panels, eDP and LVDS outputs. 443 Configuration of most aspects of device operation is performed using 444 a special tool which configures the VGA ROM, but the graphics 445 resolution can be selected in U-Boot. 446 447 config VIDEO_IVYBRIDGE_IGD 448 bool "Enable Intel Ivybridge integration graphics support" 449 depends on X86 450 help 451 This enables support for integrated graphics on Intel ivybridge 452 devices. Initialisation is mostly performed by a VGA boot ROM, with 453 some setup handled by U-Boot itself. The graphics adaptor works as 454 a VESA device and supports LCD panels, eDP and LVDS outputs. 455 Configuration of most aspects of device operation is performed using 456 a special tool which configures the VGA ROM, but the graphics 457 resolution can be selected in U-Boot. 458 459 config VIDEO_FSL_DCU_FB 460 bool "Enable Freescale Display Control Unit" 461 depends on VIDEO 462 help 463 This enables support for Freescale Display Control Unit (DCU4) 464 module found on Freescale Vybrid and QorIQ family of SoCs. 465 466 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB 467 int "Freescale DCU framebuffer size" 468 depends on VIDEO_FSL_DCU_FB 469 default 4194304 470 help 471 Set maximum framebuffer size to be used for Freescale Display 472 Controller Unit (DCU4). 473 474 source "drivers/video/rockchip/Kconfig" 475 476 config VIDEO_SANDBOX_SDL 477 bool "Enable sandbox video console using SDL" 478 depends on SANDBOX 479 help 480 When using sandbox you can enable an emulated LCD display which 481 appears as an SDL (Simple DirectMedia Layer) window. This is a 482 console device and can display stdout output. Within U-Boot is is 483 a normal bitmap display and can display images as well as text. 484 485 source "drivers/video/stm32/Kconfig" 486 487 config VIDEO_TEGRA20 488 bool "Enable LCD support on Tegra20" 489 depends on OF_CONTROL 490 help 491 Tegra20 supports video output to an attached LCD panel as well as 492 other options such as HDMI. Only the LCD is supported in U-Boot. 493 This option enables this support which can be used on devices which 494 have an LCD display connected. 495 496 config VIDEO_TEGRA124 497 bool "Enable video support on Tegra124" 498 depends on DM_VIDEO 499 help 500 Tegra124 supports many video output options including eDP and 501 HDMI. At present only eDP is supported by U-Boot. This option 502 enables this support which can be used on devices which 503 have an eDP display connected. 504 505 source "drivers/video/bridge/Kconfig" 506 507 config VIDEO 508 bool "Enable legacy video support" 509 depends on !DM_VIDEO 510 help 511 Define this for video support, without using driver model. Some 512 drivers use this because they are not yet converted to driver 513 model. Video drivers typically provide a colour text console and 514 cursor. 515 516 config VIDEO_IPUV3 517 bool "i.MX IPUv3 Core video support" 518 depends on VIDEO && MX6 519 help 520 This enables framebuffer driver for i.MX processors working 521 on the IPUv3(Image Processing Unit) internal graphic processor. 522 523 config CFB_CONSOLE 524 bool "Enable colour frame buffer console" 525 depends on VIDEO 526 default y if VIDEO 527 help 528 Enables the colour frame buffer driver. This supports colour 529 output on a bitmap display from an in-memory frame buffer. 530 Several colour devices are supported along with various options to 531 adjust the supported features. The driver is implemented in 532 cfb_console.c 533 534 The following defines are needed (cf. smiLynxEM, i8042) 535 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation 536 (default big endian) 537 VIDEO_HW_RECTFILL graphic chip supports 538 rectangle fill (cf. smiLynxEM) 539 VIDEO_HW_BITBLT graphic chip supports 540 bit-blit (cf. smiLynxEM) 541 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch) 542 VIDEO_VISIBLE_ROWS visible pixel rows 543 VIDEO_PIXEL_SIZE bytes per pixel 544 VIDEO_DATA_FORMAT graphic data format 545 (0-5, cf. cfb_console.c) 546 VIDEO_FB_ADRS framebuffer address 547 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init()) 548 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc) 549 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc) 550 CONFIG_VIDEO_LOGO display Linux logo in upper left corner 551 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h 552 for logo. Requires CONFIG_VIDEO_LOGO 553 CONFIG_CONSOLE_EXTRA_INFO 554 additional board info beside 555 the logo 556 CONFIG_HIDE_LOGO_VERSION 557 do not display bootloader 558 version string 559 560 When CONFIG_CFB_CONSOLE is defined, the video console is the 561 default console. The serial console can be forced by setting the 562 environment 'console=serial'. 563 564 config CFB_CONSOLE_ANSI 565 bool "Support ANSI escape sequences" 566 depends on CFB_CONSOLE 567 help 568 This allows the colour buffer frame buffer driver to support 569 a limited number of ANSI escape sequences (cursor control, 570 erase functions and limited graphics rendition control). Normal 571 output from U-Boot will pass through this filter. 572 573 config VGA_AS_SINGLE_DEVICE 574 bool "Set the video as an output-only device" 575 depends on CFB_CONSOLE 576 default y 577 help 578 If enable the framebuffer device will be initialized as an 579 output-only device. The Keyboard driver will not be set up. This 580 may be used if you have no keyboard device, or more than one 581 (USB Keyboard, AT Keyboard). 582 583 config VIDEO_SW_CURSOR 584 bool "Enable a software cursor" 585 depends on CFB_CONSOLE 586 default y if CFB_CONSOLE 587 help 588 This draws a cursor after the last character. No blinking is 589 provided. This makes it possible to see the current cursor 590 position when entering text on the console. It is recommended to 591 enable this. 592 593 config CONSOLE_EXTRA_INFO 594 bool "Display additional board information" 595 depends on CFB_CONSOLE 596 help 597 Display additional board information strings that normally go to 598 the serial port. When this option is enabled, a board-specific 599 function video_get_info_str() is called to get the string for 600 each line of the display. The function should return the string, 601 which can be empty if there is nothing to display for that line. 602 603 config CONSOLE_SCROLL_LINES 604 int "Number of lines to scroll the console by" 605 depends on CFB_CONSOLE || DM_VIDEO || LCD 606 default 1 607 help 608 When the console need to be scrolled, this is the number of 609 lines to scroll by. It defaults to 1. Increasing this makes the 610 console jump but can help speed up operation when scrolling 611 is slow. 612 613 config SYS_CONSOLE_BG_COL 614 hex "Background colour" 615 depends on CFB_CONSOLE 616 default 0x00 617 help 618 Defines the background colour for the console. The value is from 619 0x00 to 0xff and the meaning depends on the graphics card. 620 Typically, 0x00 means black and 0xff means white. Do not set 621 the background and foreground to the same colour or you will see 622 nothing. 623 624 config SYS_CONSOLE_FG_COL 625 hex "Foreground colour" 626 depends on CFB_CONSOLE 627 default 0xa0 628 help 629 Defines the foreground colour for the console. The value is from 630 0x00 to 0xff and the meaning depends on the graphics card. 631 Typically, 0x00 means black and 0xff means white. Do not set 632 the background and foreground to the same colour or you will see 633 nothing. 634 635 config LCD 636 bool "Enable legacy LCD support" 637 help 638 Define this to enable LCD support (for output to LCD display). 639 You will also need to select an LCD driver using an additional 640 CONFIG option. See the README for details. Drives which have been 641 converted to driver model will instead used CONFIG_DM_VIDEO. 642 643 config VIDEO_DW_HDMI 644 bool 645 help 646 Enables the common driver code for the Designware HDMI TX 647 block found in SoCs from various vendors. 648 As this does not provide any functionality by itself (but 649 rather requires a SoC-specific glue driver to call it), it 650 can not be enabled from the configuration menu. 651 652 config VIDEO_SIMPLE 653 bool "Simple display driver for preconfigured display" 654 help 655 Enables a simple generic display driver which utilizes the 656 simple-framebuffer devicetree bindings. 657 658 This driver assumes that the display hardware has been initialized 659 before u-boot starts, and u-boot will simply render to the pre- 660 allocated frame buffer surface. 661 662 config VIDEO_DT_SIMPLEFB 663 bool "Enable SimpleFB support for passing framebuffer to OS" 664 help 665 Enables the code to pass the framebuffer to the kernel as a 666 simple framebuffer in the device tree. 667 The video output is initialized by U-Boot, and kept by the 668 kernel. 669 670 endmenu 671
