Lines Matching +full:a +full:- +full:display
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
22 If you have a LCD backlight adjustable by PWM, say Y to enable
24 This driver can be use with "simple-panel" and
26 (leds/backlight/pwm-backlight.txt)
32 If you have a LCD backlight adjustable by GPIO, say Y to enable
34 This driver can be used with "simple-panel" and
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
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
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
73 Enable ANSI escape sequence decoding for a more fully functional
77 bool "Support a simple text console"
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.
90 Sometimes, for example if the display is mounted in portrait
92 we need to rotate our content of the display relative to the
94 printed out. Enable this option to include a text driver which can
100 bool "Support a console that uses TrueType fonts"
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
114 pixels and is the nominal height of a character. Note that fonts
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.
122 bool "Display console as white on a black background"
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
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
144 This is a work-around for boards which have 'lcd' in their stdout
146 In this case the console will no-longer work. While it is possible
154 Turn on this option to enable a framebuffer driver when U-Boot is
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
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
189 This option sets the resolution used for the U-Boot framebuffer (and
193 bool "640x400 256-color"
196 bool "640x480 256-color"
199 bool "800x600 16-color"
202 bool "800x600 256-color"
205 bool "1024x768 16-color"
208 bool "1024x768 256-color"
211 bool "1280x1024 16-color"
214 bool "1280x1024 256-color"
232 bool "320x200 32k-color (1:5:5:5)"
235 bool "320x200 64k-color (5:6:5)"
238 bool "320x200 16.8M-color (8:8:8)"
241 bool "640x480 32k-color (1:5:5:5)"
244 bool "640x480 64k-color (5:6:5)"
247 bool "640x480 16.8M-color (8:8:8)"
250 bool "800x600 32k-color (1:5:5:5)"
253 bool "800x600 64k-color (5:6:5)"
256 bool "800x600 16.8M-color (8:8:8)"
259 bool "1024x768 32k-color (1:5:5:5)"
262 bool "1024x768 64k-color (5:6:5)"
265 bool "1024x768 16.8M-color (8:8:8)"
268 bool "1280x1024 32k-color (1:5:5:5)"
271 bool "1280x1024 64k-color (5:6:5)"
274 bool "1280x1024 16.8M-color (8:8:8)"
318 ---help---
320 from a parallel LCD interface and translate it on the fy into a DP
326 ---help---
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
336 ---help---
338 anything in the 8MHz-30MHz range and the exact value should be
348 ---help---
349 The reset pin of SSD2828 chip. This takes a string in the format
356 ---help---
357 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
359 done they work like a regular LVDS panel.
365 ---help---
366 This is one of the SPI communication pins, involved in setting up a
368 different hardware setups. The option takes a string in the format
375 ---help---
376 This is one of the SPI communication pins, involved in setting up a
378 different hardware setups. The option takes a string in the format
385 ---help---
386 This is one of the SPI communication pins, involved in setting up a
388 different hardware setups. The option takes a string in the format
395 ---help---
396 This is one of the SPI communication pins, involved in setting up a
399 useful functionality. Such as bi-directional communication with the
401 option takes a string in the format understood by 'name_to_gpio'
409 ---help---
417 This enables the Display subsystem (DSS) on OMAP3+ boards.
425 config DISPLAY config
426 bool "Enable Display support"
431 This supports drivers that provide a display, such as eDP (Embedded
433 The devices provide a simple interface to start up the display,
434 read display information and enable it.
438 depends on DISPLAY
442 will convert RGB data streams into HDMI-encoded signals.
452 depends on DISPLAY
455 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
458 Note that this is a pure transmitter device, and has no display
466 devices. Initialisation is mostly performed by a VGA boot ROM, with
467 some setup handled by U-Boot itself. The graphics adaptor works as
468 a VESA device and supports LCD panels, eDP and LVDS outputs.
470 a special tool which configures the VGA ROM, but the graphics
471 resolution can be selected in U-Boot.
478 devices. Initialisation is mostly performed by a VGA boot ROM, with
479 some setup handled by U-Boot itself. The graphics adaptor works as
480 a VESA device and supports LCD panels, eDP and LVDS outputs.
482 a special tool which configures the VGA ROM, but the graphics
483 resolution can be selected in U-Boot.
486 bool "Enable Freescale Display Control Unit"
489 This enables support for Freescale Display Control Unit (DCU4)
497 Set maximum framebuffer size to be used for Freescale Display
503 bool "Enable Arm Mali Display Processor support"
507 This enables support for Arm Ltd Mali Display Processors from
514 When using sandbox you can enable an emulated LCD display which
515 appears as an SDL (Simple DirectMedia Layer) window. This is a
516 console device and can display stdout output. Within U-Boot is is
517 a normal bitmap display and can display images as well as text.
526 other options such as HDMI. Only the LCD is supported in U-Boot.
528 have an LCD display connected.
535 HDMI. At present only eDP is supported by U-Boot. This option
537 have an eDP display connected.
547 model. Video drivers typically provide a colour text console and
563 output on a bitmap display from an in-memory frame buffer.
574 bit-blit (cf. smiLynxEM)
579 (0-5, cf. cfb_console.c)
584 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
591 do not display bootloader
603 a limited number of ANSI escape sequences (cursor control,
605 output from U-Boot will pass through this filter.
608 bool "Set the video as an output-only device"
613 output-only device. The Keyboard driver will not be set up. This
618 bool "Enable a software cursor"
622 This draws a cursor after the last character. No blinking is
628 bool "Display additional board information"
631 Display additional board information strings that normally go to
632 the serial port. When this option is enabled, a board-specific
634 each line of the display. The function should return the string,
635 which can be empty if there is nothing to display for that line.
672 Define this to enable LCD support (for output to LCD display).
683 rather requires a SoC-specific glue driver to call it), it
687 bool "Simple display driver for preconfigured display"
689 Enables a simple generic display driver which utilizes the
690 simple-framebuffer devicetree bindings.
692 This driver assumes that the display hardware has been initialized
693 before u-boot starts, and u-boot will simply render to the pre-
699 Enables the code to pass the framebuffer to the kernel as a
701 The video output is initialized by U-Boot, and kept by the
709 This supports drivers that provide a OSD (on-screen display), which
710 is a (usually text-oriented) graphics buffer to show information on
711 a display.
724 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
725 textual overlays of the display outputs.