Kconfig 21 KB

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