5 menu "Graphics support"
8 bool "Enable driver model support for LCD/video"
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
18 bool "Generic PWM based Backlight Driver"
19 depends on DM_VIDEO && DM_PWM
22 If you have a LCD backlight adjustable by PWM, say Y to enable
24 This driver can be use with "simple-panel" and
25 it understands the standard device tree
26 (leds/backlight/pwm-backlight.txt)
29 bool "Generic GPIO based Backlight Driver"
32 If you have a LCD backlight adjustable by GPIO, say Y to enable
34 This driver can be used with "simple-panel" and
35 it understands the standard device tree
36 (leds/backlight/gpio-backlight.txt)
39 bool "Support 8-bit-per-pixel displays"
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
49 bool "Support 16-bit-per-pixel displays"
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
59 bool "Support 32-bit-per-pixel displays"
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
69 bool "Support ANSI escape sequences in video console"
73 Enable ANSI escape sequence decoding for a more fully functional
77 bool "Support MIPI DSI interface"
80 Support MIPI DSI interface for driving a MIPI compatible device.
81 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
82 serial interface between a host processor and a display module.
85 bool "Support a simple text console"
89 Support drawing text on the frame buffer console so that it can be
90 used as a console. Rotation is not supported by this driver (see
91 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
94 config CONSOLE_ROTATION
95 bool "Support rotated displays"
98 Sometimes, for example if the display is mounted in portrait
99 mode or even if it's mounted landscape but rotated by 180degree,
100 we need to rotate our content of the display relative to the
101 framebuffer, so that user can read the messages which are
102 printed out. Enable this option to include a text driver which can
103 support this. The rotation is set by the 'rot' parameter in
104 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
105 degrees, 3=270 degrees.
107 config CONSOLE_TRUETYPE
108 bool "Support a console that uses TrueType fonts"
111 TrueTrype fonts can provide outline-drawing capability rather than
112 needing to provide a bitmap for each font and size that is needed.
113 With this option you can adjust the text size and use a variety of
114 fonts. Note that this is noticeably slower than with normal console.
116 config CONSOLE_TRUETYPE_SIZE
117 int "TrueType font size"
118 depends on CONSOLE_TRUETYPE
121 This sets the font size for the console. The size is measured in
122 pixels and is the nominal height of a character. Note that fonts
123 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
124 However that measurement depends on the size of your display and
125 there is no standard display density. At present there is not a
126 method to select the display's physical size, which would allow
127 U-Boot to calculate the correct font size.
129 config SYS_WHITE_ON_BLACK
130 bool "Display console as white on a black background"
131 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || TEGRA || X86 || ARCH_SUNXI
133 Normally the display is black on a white background, Enable this
134 option to invert this, i.e. white on a black background. This can be
135 better in low-light situations or to reduce eye strain in some
139 bool "Skip framebuffer clear"
141 If firmware (whatever loads u-boot) has already put a splash image
142 on screen, you might want to preserve it until whatever u-boot
143 loads takes over the screen. This, for example, can be used to
144 keep splash image on screen until grub graphical boot menu starts.
146 source "drivers/video/fonts/Kconfig"
148 config VIDCONSOLE_AS_LCD
149 bool "Use 'vidconsole' when 'lcd' is seen in stdout"
152 This is a work-around for boards which have 'lcd' in their stdout
153 environment variable, but have moved to use driver model for video.
154 In this case the console will no-longer work. While it is possible
155 to update the environment, the breakage may be confusing for users.
156 This option will be removed around the end of 2016.
158 config VIDEO_COREBOOT
159 bool "Enable coreboot framebuffer driver support"
160 depends on X86 && SYS_COREBOOT
162 Turn on this option to enable a framebuffer driver when U-Boot is
163 loaded by coreboot where the graphics device is configured by
164 coreboot already. This can in principle be used with any platform
165 that coreboot supports.
168 bool "Enable EFI framebuffer driver support"
171 Turn on this option to enable a framebuffeer driver when U-Boot is
172 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
173 the graphics device is configured by the EFI BIOS already. This can
174 in principle be used with any platform that has an EFI BIOS.
177 bool "Enable VESA video driver support"
180 Turn on this option to enable a very simple driver which uses vesa
181 to discover the video mode and then provides a frame buffer for use
182 by U-Boot. This can in principle be used with any platform that
183 supports PCI and video cards that support VESA BIOS Extension (VBE).
185 config FRAMEBUFFER_SET_VESA_MODE
186 bool "Set framebuffer graphics resolution"
187 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
189 Set VESA/native framebuffer mode (needed for bootsplash and graphical
193 prompt "framebuffer graphics resolution"
194 default FRAMEBUFFER_VESA_MODE_118
195 depends on FRAMEBUFFER_SET_VESA_MODE
197 This option sets the resolution used for the U-Boot framebuffer (and
200 config FRAMEBUFFER_VESA_MODE_100
201 bool "640x400 256-color"
203 config FRAMEBUFFER_VESA_MODE_101
204 bool "640x480 256-color"
206 config FRAMEBUFFER_VESA_MODE_102
207 bool "800x600 16-color"
209 config FRAMEBUFFER_VESA_MODE_103
210 bool "800x600 256-color"
212 config FRAMEBUFFER_VESA_MODE_104
213 bool "1024x768 16-color"
215 config FRAMEBUFFER_VESA_MODE_105
216 bool "1024x768 256-color"
218 config FRAMEBUFFER_VESA_MODE_106
219 bool "1280x1024 16-color"
221 config FRAMEBUFFER_VESA_MODE_107
222 bool "1280x1024 256-color"
224 config FRAMEBUFFER_VESA_MODE_108
227 config FRAMEBUFFER_VESA_MODE_109
230 config FRAMEBUFFER_VESA_MODE_10A
233 config FRAMEBUFFER_VESA_MODE_10B
236 config FRAMEBUFFER_VESA_MODE_10C
239 config FRAMEBUFFER_VESA_MODE_10D
240 bool "320x200 32k-color (1:5:5:5)"
242 config FRAMEBUFFER_VESA_MODE_10E
243 bool "320x200 64k-color (5:6:5)"
245 config FRAMEBUFFER_VESA_MODE_10F
246 bool "320x200 16.8M-color (8:8:8)"
248 config FRAMEBUFFER_VESA_MODE_110
249 bool "640x480 32k-color (1:5:5:5)"
251 config FRAMEBUFFER_VESA_MODE_111
252 bool "640x480 64k-color (5:6:5)"
254 config FRAMEBUFFER_VESA_MODE_112
255 bool "640x480 16.8M-color (8:8:8)"
257 config FRAMEBUFFER_VESA_MODE_113
258 bool "800x600 32k-color (1:5:5:5)"
260 config FRAMEBUFFER_VESA_MODE_114
261 bool "800x600 64k-color (5:6:5)"
263 config FRAMEBUFFER_VESA_MODE_115
264 bool "800x600 16.8M-color (8:8:8)"
266 config FRAMEBUFFER_VESA_MODE_116
267 bool "1024x768 32k-color (1:5:5:5)"
269 config FRAMEBUFFER_VESA_MODE_117
270 bool "1024x768 64k-color (5:6:5)"
272 config FRAMEBUFFER_VESA_MODE_118
273 bool "1024x768 16.8M-color (8:8:8)"
275 config FRAMEBUFFER_VESA_MODE_119
276 bool "1280x1024 32k-color (1:5:5:5)"
278 config FRAMEBUFFER_VESA_MODE_11A
279 bool "1280x1024 64k-color (5:6:5)"
281 config FRAMEBUFFER_VESA_MODE_11B
282 bool "1280x1024 16.8M-color (8:8:8)"
284 config FRAMEBUFFER_VESA_MODE_USER
285 bool "Manually select VESA mode"
289 # Map the config names to an integer (KB).
290 config FRAMEBUFFER_VESA_MODE
291 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
293 default 0x100 if FRAMEBUFFER_VESA_MODE_100
294 default 0x101 if FRAMEBUFFER_VESA_MODE_101
295 default 0x102 if FRAMEBUFFER_VESA_MODE_102
296 default 0x103 if FRAMEBUFFER_VESA_MODE_103
297 default 0x104 if FRAMEBUFFER_VESA_MODE_104
298 default 0x105 if FRAMEBUFFER_VESA_MODE_105
299 default 0x106 if FRAMEBUFFER_VESA_MODE_106
300 default 0x107 if FRAMEBUFFER_VESA_MODE_107
301 default 0x108 if FRAMEBUFFER_VESA_MODE_108
302 default 0x109 if FRAMEBUFFER_VESA_MODE_109
303 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
304 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
305 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
306 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
307 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
308 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
309 default 0x110 if FRAMEBUFFER_VESA_MODE_110
310 default 0x111 if FRAMEBUFFER_VESA_MODE_111
311 default 0x112 if FRAMEBUFFER_VESA_MODE_112
312 default 0x113 if FRAMEBUFFER_VESA_MODE_113
313 default 0x114 if FRAMEBUFFER_VESA_MODE_114
314 default 0x115 if FRAMEBUFFER_VESA_MODE_115
315 default 0x116 if FRAMEBUFFER_VESA_MODE_116
316 default 0x117 if FRAMEBUFFER_VESA_MODE_117
317 default 0x118 if FRAMEBUFFER_VESA_MODE_118
318 default 0x119 if FRAMEBUFFER_VESA_MODE_119
319 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
320 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
321 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
323 config VIDEO_LCD_ANX9804
324 bool "ANX9804 bridge chip"
327 Support for the ANX9804 bridge chip, which can take pixel data coming
328 from a parallel LCD interface and translate it on the fy into a DP
329 interface for driving eDP TFT displays. It uses I2C for configuration.
331 config VIDEO_LCD_ORISETECH_OTM8009A
332 bool "OTM8009A DSI LCD panel support"
334 select VIDEO_MIPI_DSI
337 Say Y here if you want to enable support for Orise Technology
338 otm8009a 480x800 dsi 2dl panel.
340 config VIDEO_LCD_RAYDIUM_RM68200
341 bool "RM68200 DSI LCD panel support"
343 select VIDEO_MIPI_DSI
346 Say Y here if you want to enable support for Raydium RM68200
347 720x1280 DSI video mode panel.
349 config VIDEO_LCD_SSD2828
350 bool "SSD2828 bridge chip"
353 Support for the SSD2828 bridge chip, which can take pixel data coming
354 from a parallel LCD interface and translate it on the fly into MIPI DSI
355 interface for driving a MIPI compatible LCD panel. It uses SPI for
358 config VIDEO_LCD_SSD2828_TX_CLK
359 int "SSD2828 TX_CLK frequency (in MHz)"
360 depends on VIDEO_LCD_SSD2828
363 The frequency of the crystal, which is clocking SSD2828. It may be
364 anything in the 8MHz-30MHz range and the exact value should be
365 retrieved from the board schematics. Or in the case of Allwinner
366 hardware, it can be usually found as 'lcd_xtal_freq' variable in
367 FEX files. It can be also set to 0 for selecting PCLK from the
368 parallel LCD interface instead of TX_CLK as the PLL clock source.
370 config VIDEO_LCD_SSD2828_RESET
371 string "RESET pin of SSD2828"
372 depends on VIDEO_LCD_SSD2828
375 The reset pin of SSD2828 chip. This takes a string in the format
376 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
378 config VIDEO_LCD_HITACHI_TX18D42VM
379 bool "Hitachi tx18d42vm LVDS LCD panel support"
383 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
384 lcd controller which needs to be initialized over SPI, once that is
385 done they work like a regular LVDS panel.
387 config VIDEO_LCD_SPI_CS
388 string "SPI CS pin for LCD related config job"
389 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
392 This is one of the SPI communication pins, involved in setting up a
393 working LCD configuration. The exact role of SPI may differ for
394 different hardware setups. The option takes a string in the format
395 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
397 config VIDEO_LCD_SPI_SCLK
398 string "SPI SCLK pin for LCD related config job"
399 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
402 This is one of the SPI communication pins, involved in setting up a
403 working LCD configuration. The exact role of SPI may differ for
404 different hardware setups. The option takes a string in the format
405 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
407 config VIDEO_LCD_SPI_MOSI
408 string "SPI MOSI pin for LCD related config job"
409 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
412 This is one of the SPI communication pins, involved in setting up a
413 working LCD configuration. The exact role of SPI may differ for
414 different hardware setups. The option takes a string in the format
415 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
417 config VIDEO_LCD_SPI_MISO
418 string "SPI MISO pin for LCD related config job (optional)"
419 depends on VIDEO_LCD_SSD2828
422 This is one of the SPI communication pins, involved in setting up a
423 working LCD configuration. The exact role of SPI may differ for
424 different hardware setups. If wired up, this pin may provide additional
425 useful functionality. Such as bi-directional communication with the
426 hardware and LCD panel id retrieval (if the panel can report it). The
427 option takes a string in the format understood by 'name_to_gpio'
428 function, e.g. PH1 for pin 1 of port H.
430 source "drivers/video/meson/Kconfig"
433 bool "Armada XP LCD controller"
436 Support for the LCD controller integrated in the Marvell
440 bool "Enable OMAP3+ DSS Support"
441 depends on ARCH_OMAP2PLUS
443 This enables the Display subsystem (DSS) on OMAP3+ boards.
446 bool "Enable EDID library"
449 This enables library for accessing EDID data from an LCD panel.
452 bool "Enable Display support"
457 This supports drivers that provide a display, such as eDP (Embedded
458 DisplayPort) and HDMI (High Definition Multimedia Interface).
459 The devices provide a simple interface to start up the display,
460 read display information and enable it.
463 bool "Enable NXP TDA19988 support"
467 This enables support for the NXP TDA19988 HDMI encoder. This encoder
468 will convert RGB data streams into HDMI-encoded signals.
471 bool "Enable ATMEL video support using HLCDC"
474 HLCDC supports video output to an attached LCD panel.
476 config LOGICORE_DP_TX
477 bool "Enable Logicore DP TX driver"
480 Enable the driver for the transmitter part of the Xilinx LogiCORE
481 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
482 video interface as defined by VESA DisplayPort v1.2.
484 Note that this is a pure transmitter device, and has no display
485 capabilities by itself.
487 config VIDEO_BROADWELL_IGD
488 bool "Enable Intel Broadwell integrated graphics device"
491 This enables support for integrated graphics on Intel broadwell
492 devices. Initialisation is mostly performed by a VGA boot ROM, with
493 some setup handled by U-Boot itself. The graphics adaptor works as
494 a VESA device and supports LCD panels, eDP and LVDS outputs.
495 Configuration of most aspects of device operation is performed using
496 a special tool which configures the VGA ROM, but the graphics
497 resolution can be selected in U-Boot.
499 config VIDEO_IVYBRIDGE_IGD
500 bool "Enable Intel Ivybridge integration graphics support"
503 This enables support for integrated graphics on Intel ivybridge
504 devices. Initialisation is mostly performed by a VGA boot ROM, with
505 some setup handled by U-Boot itself. The graphics adaptor works as
506 a VESA device and supports LCD panels, eDP and LVDS outputs.
507 Configuration of most aspects of device operation is performed using
508 a special tool which configures the VGA ROM, but the graphics
509 resolution can be selected in U-Boot.
511 config VIDEO_FSL_DCU_FB
512 bool "Enable Freescale Display Control Unit"
513 depends on VIDEO || DM_VIDEO
515 This enables support for Freescale Display Control Unit (DCU4)
516 module found on Freescale Vybrid and QorIQ family of SoCs.
518 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
519 int "Freescale DCU framebuffer size"
520 depends on VIDEO_FSL_DCU_FB
523 Set maximum framebuffer size to be used for Freescale Display
524 Controller Unit (DCU4).
526 source "drivers/video/rockchip/Kconfig"
528 config VIDEO_ARM_MALIDP
529 bool "Enable Arm Mali Display Processor support"
530 depends on DM_VIDEO && OF_CONTROL
533 This enables support for Arm Ltd Mali Display Processors from
534 the DP500, DP550 and DP650 family.
536 config VIDEO_SANDBOX_SDL
537 bool "Enable sandbox video console using SDL"
540 When using sandbox you can enable an emulated LCD display which
541 appears as an SDL (Simple DirectMedia Layer) window. This is a
542 console device and can display stdout output. Within U-Boot is is
543 a normal bitmap display and can display images as well as text.
545 source "drivers/video/stm32/Kconfig"
548 bool "Enable LCD support on Tegra20"
549 depends on OF_CONTROL
551 Tegra20 supports video output to an attached LCD panel as well as
552 other options such as HDMI. Only the LCD is supported in U-Boot.
553 This option enables this support which can be used on devices which
554 have an LCD display connected.
556 config VIDEO_TEGRA124
557 bool "Enable video support on Tegra124"
560 Tegra124 supports many video output options including eDP and
561 HDMI. At present only eDP is supported by U-Boot. This option
562 enables this support which can be used on devices which
563 have an eDP display connected.
565 source "drivers/video/bridge/Kconfig"
567 source "drivers/video/imx/Kconfig"
570 bool "Enable legacy video support"
573 Define this for video support, without using driver model. Some
574 drivers use this because they are not yet converted to driver
575 model. Video drivers typically provide a colour text console and
579 bool "Enable colour frame buffer console"
583 Enables the colour frame buffer driver. This supports colour
584 output on a bitmap display from an in-memory frame buffer.
585 Several colour devices are supported along with various options to
586 adjust the supported features. The driver is implemented in
589 The following defines are needed (cf. smiLynxEM, i8042)
590 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
592 VIDEO_HW_RECTFILL graphic chip supports
593 rectangle fill (cf. smiLynxEM)
594 VIDEO_HW_BITBLT graphic chip supports
595 bit-blit (cf. smiLynxEM)
596 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
597 VIDEO_VISIBLE_ROWS visible pixel rows
598 VIDEO_PIXEL_SIZE bytes per pixel
599 VIDEO_DATA_FORMAT graphic data format
600 (0-5, cf. cfb_console.c)
601 VIDEO_FB_ADRS framebuffer address
602 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
603 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
604 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
605 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
606 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
607 for logo. Requires CONFIG_VIDEO_LOGO
608 CONFIG_CONSOLE_EXTRA_INFO
609 additional board info beside
611 CONFIG_HIDE_LOGO_VERSION
612 do not display bootloader
615 When CONFIG_CFB_CONSOLE is defined, the video console is the
616 default console. The serial console can be forced by setting the
617 environment 'console=serial'.
619 config CFB_CONSOLE_ANSI
620 bool "Support ANSI escape sequences"
621 depends on CFB_CONSOLE
623 This allows the colour buffer frame buffer driver to support
624 a limited number of ANSI escape sequences (cursor control,
625 erase functions and limited graphics rendition control). Normal
626 output from U-Boot will pass through this filter.
628 config VGA_AS_SINGLE_DEVICE
629 bool "Set the video as an output-only device"
630 depends on CFB_CONSOLE
633 If enable the framebuffer device will be initialized as an
634 output-only device. The Keyboard driver will not be set up. This
635 may be used if you have no keyboard device, or more than one
636 (USB Keyboard, AT Keyboard).
638 config VIDEO_SW_CURSOR
639 bool "Enable a software cursor"
640 depends on CFB_CONSOLE
641 default y if CFB_CONSOLE
643 This draws a cursor after the last character. No blinking is
644 provided. This makes it possible to see the current cursor
645 position when entering text on the console. It is recommended to
648 config CONSOLE_EXTRA_INFO
649 bool "Display additional board information"
650 depends on CFB_CONSOLE
652 Display additional board information strings that normally go to
653 the serial port. When this option is enabled, a board-specific
654 function video_get_info_str() is called to get the string for
655 each line of the display. The function should return the string,
656 which can be empty if there is nothing to display for that line.
658 config CONSOLE_SCROLL_LINES
659 int "Number of lines to scroll the console by"
660 depends on CFB_CONSOLE || DM_VIDEO || LCD
663 When the console need to be scrolled, this is the number of
664 lines to scroll by. It defaults to 1. Increasing this makes the
665 console jump but can help speed up operation when scrolling
668 config SYS_CONSOLE_BG_COL
669 hex "Background colour"
670 depends on CFB_CONSOLE
673 Defines the background colour for the console. The value is from
674 0x00 to 0xff and the meaning depends on the graphics card.
675 Typically, 0x00 means black and 0xff means white. Do not set
676 the background and foreground to the same colour or you will see
679 config SYS_CONSOLE_FG_COL
680 hex "Foreground colour"
681 depends on CFB_CONSOLE
684 Defines the foreground colour for the console. The value is from
685 0x00 to 0xff and the meaning depends on the graphics card.
686 Typically, 0x00 means black and 0xff means white. Do not set
687 the background and foreground to the same colour or you will see
691 bool "Enable legacy LCD support"
693 Define this to enable LCD support (for output to LCD display).
694 You will also need to select an LCD driver using an additional
695 CONFIG option. See the README for details. Drives which have been
696 converted to driver model will instead used CONFIG_DM_VIDEO.
701 Enables the common driver code for the Designware HDMI TX
702 block found in SoCs from various vendors.
703 As this does not provide any functionality by itself (but
704 rather requires a SoC-specific glue driver to call it), it
705 can not be enabled from the configuration menu.
707 config VIDEO_DSI_HOST_SANDBOX
708 bool "Enable sandbox for dsi host"
710 select VIDEO_MIPI_DSI
712 Enable support for sandbox dsi host device used for testing
714 Display Serial Interface (DSI) defines a serial bus and
715 a communication protocol between the host and the device
718 config VIDEO_DW_MIPI_DSI
720 select VIDEO_MIPI_DSI
722 Enables the common driver code for the Synopsis Designware
723 MIPI DSI block found in SoCs from various vendors.
724 As this does not provide any functionality by itself (but
725 rather requires a SoC-specific glue driver to call it), it
726 can not be enabled from the configuration menu.
729 bool "Simple display driver for preconfigured display"
731 Enables a simple generic display driver which utilizes the
732 simple-framebuffer devicetree bindings.
734 This driver assumes that the display hardware has been initialized
735 before u-boot starts, and u-boot will simply render to the pre-
736 allocated frame buffer surface.
738 config VIDEO_DT_SIMPLEFB
739 bool "Enable SimpleFB support for passing framebuffer to OS"
741 Enables the code to pass the framebuffer to the kernel as a
742 simple framebuffer in the device tree.
743 The video output is initialized by U-Boot, and kept by the
747 bool "Enable OSD support"
751 This supports drivers that provide a OSD (on-screen display), which
752 is a (usually text-oriented) graphics buffer to show information on
756 bool "Enable sandbox OSD"
759 Enable support for sandbox OSD device used for testing purposes.
762 bool "Enable IHS video out driver"
765 Enable support for the gdsys Integrated Hardware Systems (IHS) video
766 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
767 textual overlays of the display outputs.