Uboot中一些CONFIG_XXX定义说明

1. CONFIG_LCD

    如果定义了，Output会到LCD屏幕上.(通常是白色背景，黑色字)

   还有一些子配置项，是一些成熟厂商的开发板，支持的LCD配置项：

  CONFIG_ATMEL_LCD         :    HITACHI TX09D70VM1CCA, 3.5", 240x320.

  CONFIG_NEC_NL6448AC33:   NEC NL6448AC33-18. Active, color, single scan.

  CONFIG_NEC_NL6448BC20:   NEC NL6448BC20-08. 6.5", 640x480.   Active, color, single scan.

  CONFIG_NEC_NL6448BC33_54 :    NEC NL6448BC33-54. 10.4", 640x480.   Active, color, single scan.

  CONFIG_SHARP_16x9           :   Sharp 320x240. Active, color, single scan.   It isn't 16x9, and I am not sure what it is.

  CONFIG_SHARP_LQ64D341 :    Sharp LQ64D341 display, 640x480.   Active, color, single scan.

  CONFIG_HLD1045                 :    HLD1045 display, 640x480.   Active, color, single scan.

  CONFIG_OPTREX_BW          :    Optrex  CBL50840-2 NF-FW 99 22 M5
                                                      or   Hitachi  LMG6912RPFC-00T
                                                      or   Hitachi  SP14Q002   320x240. Black & white.
2. CONFIG_SPI

    Enables SPI Drivers (支持SPI EEPROM)

3 CONFIG_SKIP_LOWLEVEL_INIT : 用处  

2012-12-26 17:41:28|  分类： UBoot|字号 订阅

- CONFIG_SKIP_LOWLEVEL_INIT
- CONFIG_SKIP_RELOCATE_UBOOT

  [ARM only] If these variables are defined, then
  certain low level initializations (like setting up
  the memory controller) are omitted and/or U-Boot does
  not relocate itself into RAM.
  Normally these variables MUST NOT be defined. The
  only exception is when U-Boot is loaded (to RAM) by
  some other boot loader or by a debugger which
  performs these intializations itself.