天天看點

U-Boot-2011.06的README翻譯

U-Boot-2011.06的README翻譯

翻譯不準确的地方請指正。共同學習,一起進步。

#

# (C) Copyright 2000 - 2011

# Wolfgang Denk, DENX Software Engineering, [email protected].

#

# See file CREDITS for list of people who contributed to this project.

# 可以檢視CREDITS檔案來了解對本項目作出過貢獻的人們

#

# This program is free software; you can redistribute it and/or

# modify it under the terms of the GNU General Public License as

# published by the Free Software Foundation; either version 2 of

# the License, or (at your option) any later version.

# 本程式是自由軟體;你可以在遵守自由軟體基金會釋出的GNU GPL v2及其後

# 版本的條款下釋出或修改它;

#

# This program is distributed in the hope that it will be useful,

# but WITHOUT ANY WARRANTY; without even the implied warranty of

# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

# GNU General Public License for more details.

# 本程式釋出後希望是有用的,但是沒有任何保證,甚至沒有隐含的對适銷性或針

# 對特定用途的适用性的保證。更多詳細資訊參見GNU GPL。

# You should have received a copy of the GNU General Public License

# along with this program; if not, write to the Free Software

# Foundation, Inc., 59 Temple Place, Suite 330, Boston,

# MA 02111-1307 USA

#你應該在本程式中同時收到一份GNU GPL許可證,如果沒有的話,請向自由軟體基金會寫信。

#

Summary:

概述:

========

This directory contains the source code for U-Boot, a boot loader for Embedded boards based on PowerPC, ARM, MIPS and several other processors, which can be installed in a boot ROM and used to initialize and test the hardware or to download and run application code.

 這個目錄包含的是U-Boot的源代碼,U-Boot是一個用于基于PowerPC,ARM,MIPS和一些其他處理器的嵌入式開發闆的bootloader。U-Boot可被安裝到啟動ROM中,用于初始化和測試硬體,或者是下載下傳并運作應用程式代碼。

The development of U-Boot is closely related to Linux: some parts of the source code originate in the Linux source tree, we have some header files in common, and special provision has been made to support booting of Linux images.

U-Boot的發展與linux聯系緊密:源代碼的一些部分源自于linux源碼樹,還有一些頭檔案是和Linux共有的,為支援啟動Linux鏡像,還做了一些特殊的規定。

Some attention has been paid to make this software easily configurable and extendable. For instance, all monitor commands are implemented with the same call interface, so that it's very easy to add new commands. Also, instead of permanently adding rarely used code (for instance hardware test utilities) to the monitor, you can load and run it dynamically.

 為使這個軟體變得更容易配置和擴充,我們已經注意了一些事項。比如,所有的U-Boot指令都以相同的調用接口實作,是以添加新的指令變得非常簡單。此外,對于那些不常用的代碼(例如硬體測試程式),你可以動态地加載和運作,而不是将它們永久地添加到U-Boot中。

Status:

狀态:

=======

In general, all boards for which a configuration option exists in the Makefile have been tested to some extent and can be considered "working". In fact, many of them are used in production systems.

一般來說,所有存在配置選項的開發闆都已經做過一定範圍的測試,并且可以認為是能夠正常工作的,事實上,它們很多都用于實際的産品中。

In case of problems see the CHANGELOG and CREDITS files to find out who contributed the specific port. The MAINTAINERS file lists board maintainers.

如果出現了問題,可以檢視CHANGELOG和CREDITS檔案以找出是誰負責這個移植。MAINTAINERS檔案列出了每個開發闆的維護者。

Where to get help:

從哪裡獲得幫助:

==================

In case you have questions about, problems with or contributions for U-Boot you should send a message to the U-Boot mailing list at <[email protected]>. There is also an archive of previous traffic on the mailing list - please search the archive before asking FAQ's. Please see http://lists.denx.de/pipermail/u-boot and http://dir.gmane.org/gmane.comp.boot-loaders.u-boot

如果你有問題或者是要向U-Boot貢獻代碼,你應該向U-Boot的郵件清單發送一個郵件,郵件清單的位址為<[email protected]>。郵件清單中有一個以前問題的歸檔,在你提問之前應該先搜尋一下這個歸檔。請看http://lists.denx.de/pipermail/u-boot和http://dir.gmane.org/gmane.comp.boot-loaders.u-boot

Where to get source code:

從哪裡獲得源代碼:

=========================

The U-Boot source code is maintained in the git repository at git://www.denx.de/git/u-boot.git ; you can browse it online at http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary

U-Boot的源代碼在git庫中維護,位址在git://www.denx.de/git/u-boot.git,你可以在http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary上線上浏覽源代碼。

The "snapshot" links on this page allow you to download tarballs of any version you might be interested in. Official releases are also available for FTP download from the ftp://ftp.denx.de/pub/u-boot/ directory.

你可以使用該頁上的"snapshot" (快照)連結來下載下傳你感興趣的任何版本的tar包,官方的釋出版本也可通過FTP來下載下傳,位址為ftp://ftp.denx.de/pub/u-boot/ directory。

Pre-built (and tested) images are available from ftp://ftp.denx.de/pub/u-boot/images/

預先編譯和測試好的鏡像ftp://ftp.denx.de/pub/u-boot/images/。

Where we come from:

我們來自哪裡:

===================

- start from 8xxrom sources

- create PPCBoot project (http://sourceforge.net/projects/ppcboot)

- clean up code

- make it easier to add custom boards

- make it possible to add other [PowerPC] CPUs

- extend functions, especially:

  * Provide extended interface to Linux boot loader

  * S-Record download

  * network boot

  * PCMCIA / CompactFlash / ATA disk / SCSI ... boot

- create ARMBoot project (http://sourceforge.net/projects/armboot)

- add other CPU families (starting with ARM)

- create U-Boot project (http://sourceforge.net/projects/u-boot)

- current project page: see http://www.denx.de/wiki/U-Boot

- 起源于8xxrom項目

- 建立了PPCBoot項目(http://sourceforge.net/projects/ppcboot)

- 清理代碼

- 使其更容易添加自定義開發闆

- 使添加其他CPU[PowerPC]成為可能

- 擴充功能,尤其是

  * 為linux boot loader提供了擴充接口

  * S-Record下載下傳

  * 網絡啟動

  * CMCIA / CompactFlash / ATA disk / SCSI ... 啟動

- 建立了ARMBoot項目 (http://sourceforge.net/projects/armboot)

- 添加了其他CPU(從ARM開始)

- 建立了U-Boot項目(http://sourceforge.net/projects/u-boot)

- 目前項目首頁:http://www.denx.de/wiki/U-Boot

Names and Spelling:

命名和拼寫:

===================

The "official" name of this project is "Das U-Boot". The spelling "U-Boot" shall be used in all written text (documentation, comments in source files etc.). Example:

這個項目的官方命名是"Das U-Boot",在所有的文本書寫中應使用"U-Boot"這個拼寫,如:

 This is the README file for the U-Boot project.

 這是U-Boot項目的README檔案

File names etc. shall be based on the string "u-boot". Examples:

檔案名等應該使用字元串"u-boot",比如

 include/asm-ppc/u-boot.h

 #include <asm/u-boot.h>

Variable names, preprocessor constants etc. shall be either based on the string "u_boot" or on "U_BOOT". Example:

變量名、預處理常數等應使用基于"u_boot"或"U_BOOT"的名字,如:

 U_BOOT_VERSION  u_boot_logo

 IH_OS_U_BOOT  u_boot_hush_start

Versioning:

版本:

===========

Starting with the release in October 2008, the names of the releases were changed from numerical release numbers without deeper meaning into a time stamp based numbering. Regular releases are identified by names consisting of the calendar year and month of the release date. Additional fields (if present) indicate release candidates or bug fix releases in "stable" maintenance trees.

從2008年10月開始,發行版名字中的版本号由原來用數值表示改為用時間表示,原來用數值表示的版本号沒有更深程度的含義,用時間表示的版本号由兩部分組成,分别是發行時的年和月。附加的字段(如果出現了的話)訓示備選的發行版或者是在穩定版中修複bug後的發行版。

Examples:

 U-Boot v2009.11     - Release November 2009

 U-Boot v2009.11.1   - Release 1 in version November 2009 stable tree

 U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release

 U-Boot v2009.11     - 2009年11月的發行版

 U-Boot v2009.11.1   - 2009年11月的穩定版基礎上修改後的第一個發行版

 U-Boot v2010.09-rc1 - 2010年9月的候選發行版1

Directory Hierarchy:

目錄層次:

==================== 

/arch   Architecture specific files                                            體系結構專有檔案

    /arm   Files generic to ARM architecture                          ARM體系的檔案

        /cpu  CPU specific files                                                   CPU專有檔案

            /arm720t  Files specific to ARM 720 CPUs             ARM720t專有檔案

            /arm920t  Files specific to ARM 920 CPUs             ARM920t專有檔案

            /s3c24x0 Files specific to Samsung S3C24X0 CPUs     三星S3C24X0 CPU專有檔案

            ……

        /lib  Architecture specific library files                             體系結構專有庫檔案

    /avr32  Files generic to AVR32 architecture

        /cpu  CPU specific files

        /lib  Architecture specific library files

    ……

/api   Machine/arch independent API for external apps      外部程式使用的與體系無關的API

/board   Board dependent files                                               開發闆相關檔案

/common   Misc architecture independent functions          各種體系無關的功能

/disk   Code for disk drive partition handling                        磁盤分區處理的代碼

/doc   Documentation (don't expect too much)                     文檔(不要希望太多)

/drivers  Commonly used device drivers                               常用的裝置驅動

/examples  Example code for standalone applications, etc.   獨立應用的示例代碼

/fs   Filesystem code (cramfs, ext2, jffs2, etc.)                      檔案系統代碼

/include  Header Files                                                               頭檔案

/lib   Files generic to all architectures                                     所有體系共有的檔案

    /libfdt  Library files to support flattened device trees       支援flattened裝置樹的庫

    /lzma   Library files to support LZMA decompression     支援LAMA解壓的庫

    /lzo   Library files to support LZO decompression           支援LZO解壓的庫

/net   Networking code                                                               網絡代碼

/post   Power On Self Test                                                        開機自檢

/rtc   Real Time Clock drivers                                                   實時時鐘驅動

/tools   Tools to build S-Record or U-Boot images, etc.     建立S-Record和U-Boot鏡像的工具

Software Configuration:

軟體配置:

=======================

Configuration is usually done using C preprocessor defines; the rationale behind that is to avoid dead code whenever possible.

配置通常使用C預處理器的宏定義;這樣做的合理性在于可以避免任何可能的死代碼。

There are two classes of configuration variables:

有兩種類型的可配置變量:

* Configuration _OPTIONS_:

  These are selectable by the user and have names beginning with  "CONFIG_".

  這些配置是使用者可選的,以"CONFIG_"開頭命名

* Configuration _SETTINGS_:

  These depend on the hardware etc. and should not be meddled with if you don't know what you're doing; they have names beginning with "CONFIG_SYS_".

  這些配置依賴于硬體等,如果你不知道你在做什麼的話,請不要幹預,這些配置以"CONFIG_SYS_"開頭。

Later we will add a configuration tool - probably similar to or even identical to what's used for the Linux kernel. Right now, we have to do the configuration by hand, which means creating some symbolic links and editing some configuration files. We use the TQM8xxL boards as an example here.

以後我們會添加一個配置工具 - 可能和Linux核心使用的類似甚至完全相同。但是目前我們還必須手工配置,這意味着需要建立一些符号連結并且編寫一些配置檔案。我們這裡使用TQM8xxL開發闆作為示例。

配置太多了,這裡有選擇地忽略了一部分内容。

Selection of Processor Architecture and Board Type:

選擇處理器體系結構和開發闆類型:

---------------------------------------------------

For all supported boards there are ready-to-use default configurations available; just type "make <board_name>_config".

對于支援的所有開發闆,都有一個現成可用的預設配置,僅需要輸入"make <開發闆名字>_config"即可:

Example: For a TQM823L module type:

例如:對于TQM823L:

 cd u-boot

 make TQM823L_config

For the Cogent platform, you need to specify the CPU type as well; e.g. "make cogent_mpc8xx_config". And also configure the cogent directory according to the instructions in cogent/README.

對于Cogent平台,你需要指定CPU類型,例如"make cogent_mpc8xx_config"。此外,還需要按照cogent/README的說明配置cogent目錄。

Configuration Options:

配置選項:

----------------------

Configuration depends on the combination of board and CPU type; all such information is kept in a configuration file "include/configs/<board_name>.h".

配置選項依賴于開發闆和CPU的組合,所有的這些資訊儲存在配置檔案"include/configs/<開發闆名字>.h"中。

Example: For a TQM823L module, all configuration settings are in "include/configs/TQM823L.h".

例如:TQM823L的所有配置的設定在"include/configs/TQM823L.h"中。

Many of the options are named exactly as the corresponding Linux kernel configuration options. The intention is to make it easier to build a config tool - later.

許多選項和對應的Linux核心的配置選擇命名完全相同,目的是在使以後建立配置工具更簡單。

The following options need to be configured:

一下選項需要配置:

- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.

- CPU類型:隻能定義一個,比如CONFIG_MPC85XX.

- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.

- 開發闆類型:隻能定義一個,比如CONFIG_MPC8540ADS.

- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)

 Define exactly one, e.g. CONFIG_ATSTK1002

- CPU子闆類型:(如果定義了ONFIG_ATSTK1000)隻能定義一個,例如CONFIG_ATSTK1002

- CPU Module Type: (if CONFIG_COGENT is defined)

  Define exactly one of

  CONFIG_CMA286_60_OLD

--- FIXME --- not tested yet:

  CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

  CONFIG_CMA287_23, CONFIG_CMA287_50

- CPU元件類型:(如果定義了CONFIG_COGENT)隻能定義以下配置中的一個

  CONFIG_CMA286_60_OLD

--- 需要整理 --- 尚未測試:

  CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

  CONFIG_CMA287_23, CONFIG_CMA287_50

- Motherboard Type: (if CONFIG_COGENT is defined)

  Define exactly one of

  CONFIG_CMA101, CONFIG_CMA102

- 主機闆類型:(如果定義了CONFIG_COGENT)

  隻能定義以下配置之一

  CONFIG_CMA101, CONFIG_CMA102

……

- Linux Kernel Interface:

- Linux核心接口

  CONFIG_CLOCKS_IN_MHZ

  U-Boot stores all clock information in Hz internally. For binary compatibility with older Linux kernels (which expect the clocks passed in the bd_info data to be in MHz) the environment variable "clocks_in_mhz" can be defined so that U-Boot converts clock data to MHZ before passing it to the Linux kernel. When CONFIG_CLOCKS_IN_MHZ is defined, a definition of  "clocks_in_mhz=1" is automatically included in the default environment.

  U-Boot内部使用Hz來存儲所有的時鐘資訊。為了與舊核心(舊核心使用MHZ)的二進制相容,應該定義環境變量"clocks_in_mhz"以使U-Boot在将時鐘資料傳遞給Linux核心核心前将其轉換為MHZ。如果定義了CONFIG_CLOCKS_IN_MHZ,則"clocks_in_mhz=1"的定義會自動包含到預設的環境變量中。

  CONFIG_MEMSIZE_IN_BYTES  [relevant for MIPS only]

  When transferring memsize parameter to linux, some versions expect it to be in bytes, others in MB. Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.

  僅和MIPS相關。當傳遞記憶體大小參數給核心時,一些版本以位元組為機關,另一些以MB為機關。定義CONFIG_MEMSIZE_IN_BYTES将以位元組為機關。

  CONFIG_OF_LIBFDT

  New kernel versions are expecting firmware settings to be passed using flattened device trees (based on open firmware concepts).

  新的核心版本要求用flattened裝置樹傳遞固件設定(基于開放固件思想?)

  CONFIG_OF_LIBFDT

   * New libfdt-based support

   * Adds the "fdt" command

   * The bootm command automatically updates the fdt

  OF_CPU - The proper name of the cpus node (only required for

   MPC512X and MPC5xxx based boards).

  OF_SOC - The proper name of the soc node (only required for

   MPC512X and MPC5xxx based boards).

  OF_TBCLK - The timebase frequency.

  OF_STDOUT_PATH - The path to the console device

  boards with QUICC Engines require OF_QE to set UCC MAC

  addresses

  CONFIG_OF_BOARD_SETUP

  Board code has addition modification that it wants to make to the flat device tree before handing it off to the kernel

  CONFIG_OF_BOOT_CPU

  This define fills in the correct boot CPU in the boot param header, the default value is zero if undefined.

  這個定義在啟動參數頭中填充正确的啟動CPU,如果沒有定義,預設值将是0

  CONFIG_OF_IDE_FIXUP

  U-Boot can detect if an IDE device is present or not. If not, and this new config option is activated, U-Boot removes the ATA node from the DTS before booting Linux, so the Linux IDE driver does not probe the device and crash. This is needed for buggy hardware (uc101) where no pull down resistor is connected to the signal IDE5V_DD7.

  U-Boot會檢測是否存在IDE裝置,如果不存在,并且激活了這個選項,那麼U-Boot将在啟動Linux前從DTS中删除ATA結點,是以,Linux的IDE驅動不會探測IDE裝置并崩潰。這個選項用于那些有bug的硬體(uc101),這些硬體沒有下拉電阻連接配接到IDE5V_DD7。

- vxWorks boot parameters:

- vxWorks啟動參數:

 ……

- Serial Ports:

- 序列槽:

 ……

- Console Interface:

- 控制台接口:

- Console Baudrate:

- 控制台波特率:

  CONFIG_BAUDRATE - in bps                                                     機關bps

  Select one of the baudrates listed in                                            從下面定義的波特率清單中選擇一個

  CONFIG_SYS_BAUDRATE_TABLE, see below.

  CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale

- Console Rx buffer length

- 控制台接收緩沖長度

  僅82xx and 8xx可能使用。

 ……

- Boot Delay: CONFIG_BOOTDELAY - in seconds

  Delay before automatically booting the default image;set to -1 to disable autoboot.

  在自動啟動預設鏡像前的延時,機關是秒,設為-1可禁用自動啟動

  See doc/README.autoboot for these options that work with CONFIG_BOOTDELAY. None are required.

  閱讀doc/README.autoboot可以了解下面這些同CONFIG_BOOTDELAY一起工作的選項。它們都不是必須的。

  CONFIG_BOOT_RETRY_TIME

  CONFIG_BOOT_RETRY_MIN

  CONFIG_AUTOBOOT_KEYED

  CONFIG_AUTOBOOT_PROMPT

  CONFIG_AUTOBOOT_DELAY_STR

  CONFIG_AUTOBOOT_STOP_STR

  CONFIG_AUTOBOOT_DELAY_STR2

  CONFIG_AUTOBOOT_STOP_STR2

  CONFIG_ZERO_BOOTDELAY_CHECK

  CONFIG_RESET_TO_RETRY

- Autoboot Command:

  CONFIG_BOOTCOMMAND

  Only needed when CONFIG_BOOTDELAY is enabled; define a command string that is automatically executed when no character is read on the console interface within "Boot Delay" after reset.

  僅CONFIG_BOOTDELAY使能時需要,定義一個指令字元串,如果複位後在Boot Dealy時間内沒有從控制台讀入任何字元,則自動執行該字元串定義的指令。

  CONFIG_BOOTARGS

  This can be used to pass arguments to the bootm command. The value of CONFIG_BOOTARGS goes into the environment value "bootargs".

  用于向bootm指令傳遞參數。CONFIG_BOOTARGS的值将會加入環境變量"bootargs"中

  CONFIG_RAMBOOT and CONFIG_NFSBOOT

  The value of these goes into the environment as "ramboot" and "nfsboot" respectively, and can be used as a convenience, when switching between booting from RAM and NFS.

  它們的值将分别加入環境變量"ramboot"和"nfsboot"中,可為從RAM或NFS啟動切換提供友善

- Pre-Boot Commands:

- 預啟動指令:

……

- Serial Download Echo Mode:

- 序列槽下載下傳回顯模式:

  CONFIG_LOADS_ECHO

  If defined to 1, all characters received during a serial download (using the "loads" command) are echoed back. This might be needed by some terminal emulations (like "cu"), but may as well just take time on others. This setting #define's the initial value of the "loads_echo" environment variable.

  如果定義為1,所有通過序列槽下載下傳(使用loads指令)接收的字元會回顯。這可能被某些終端模拟器(比如cu)需要。

……

- Monitor Functions:

- U-Boot功能:

  Monitor commands can be included or excluded from the build by using the #include files "config_cmd_all.h" and #undef'ing unwanted commands, or using "config_cmd_default.h"  and augmenting with additional #define's for wanted commands.

  U-Boot指令可以包含或排除在生成中,可以使用#include "config_cmd_all.h"并用#undef排除不需要的指令的方式,也可以使用include "config_cmd_default.h"并用define添加需要指令的方式。

  The default command configuration includes all commands except those marked below with a "*".

  預設指令包含如下除标以*的所有指令。

  CONFIG_CMD_ASKENV * ask for env variable

  CONFIG_CMD_BDI    bdinfo

  CONFIG_CMD_BEDBUG * Include BedBug Debugger

  CONFIG_CMD_BMP  * BMP support

  CONFIG_CMD_BSP  * Board specific commands

  CONFIG_CMD_BOOTD   bootd

  CONFIG_CMD_CACHE * icache, dcache

  CONFIG_CMD_CONSOLE   coninfo

  CONFIG_CMD_CRC32 * crc32

  CONFIG_CMD_DATE  * support for RTC, date/time...

  CONFIG_CMD_DHCP  * DHCP support

  CONFIG_CMD_DIAG  * Diagnostics

  CONFIG_CMD_DS4510 * ds4510 I2C gpio commands

  CONFIG_CMD_DS4510_INFO * ds4510 I2C info command

  CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd

  CONFIG_CMD_DS4510_RST * ds4510 I2C rst command

  CONFIG_CMD_DTT  * Digital Therm and Thermostat

  CONFIG_CMD_ECHO    echo arguments

  CONFIG_CMD_EDITENV   edit env variable

  CONFIG_CMD_EEPROM * EEPROM read/write support

  CONFIG_CMD_ELF  * bootelf, bootvx

  CONFIG_CMD_EXPORTENV * export the environment

  CONFIG_CMD_SAVEENV   saveenv

  CONFIG_CMD_FDC  * Floppy Disk Support

  CONFIG_CMD_FAT  * FAT partition support

  CONFIG_CMD_FDOS  * Dos diskette Support

  CONFIG_CMD_FLASH   flinfo, erase, protect

  CONFIG_CMD_FPGA    FPGA device initialization support

  CONFIG_CMD_GO  * the 'go' command (exec code)

  CONFIG_CMD_GREPENV * search environment

  CONFIG_CMD_HWFLOW * RTS/CTS hw flow control

  CONFIG_CMD_I2C  * I2C serial bus support

  CONFIG_CMD_IDE  * IDE harddisk support

  CONFIG_CMD_IMI    iminfo

  CONFIG_CMD_IMLS    List all found images

  CONFIG_CMD_IMMAP * IMMR dump support

  CONFIG_CMD_IMPORTENV * import an environment

  CONFIG_CMD_IRQ  * irqinfo

  CONFIG_CMD_ITEST   Integer/string test of 2 values

  CONFIG_CMD_JFFS2 * JFFS2 Support

  CONFIG_CMD_KGDB  * kgdb

  CONFIG_CMD_LDRINFO   ldrinfo (display Blackfin loader)

  CONFIG_CMD_LOADB   loadb

  CONFIG_CMD_LOADS   loads

  CONFIG_CMD_MD5SUM   print md5 message digest

       (requires CONFIG_CMD_MEMORY and CONFIG_MD5)

  CONFIG_CMD_MEMORY   md, mm, nm, mw, cp, cmp, crc, base,

       loop, loopw, mtest

  CONFIG_CMD_MISC    Misc functions like sleep etc

  CONFIG_CMD_MMC  * MMC memory mapped support

  CONFIG_CMD_MII  * MII utility commands

  CONFIG_CMD_MTDPARTS * MTD partition support

  CONFIG_CMD_NAND  * NAND support

  CONFIG_CMD_NET    bootp, tftpboot, rarpboot

  CONFIG_CMD_PCA953X * PCA953x I2C gpio commands

  CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command

  CONFIG_CMD_PCI  * pciinfo

  CONFIG_CMD_PCMCIA  * PCMCIA support

  CONFIG_CMD_PING  * send ICMP ECHO_REQUEST to network

       host

  CONFIG_CMD_PORTIO * Port I/O

  CONFIG_CMD_REGINFO * Register dump

  CONFIG_CMD_RUN    run command in env variable

  CONFIG_CMD_SAVES * save S record dump

  CONFIG_CMD_SCSI  * SCSI Support

  CONFIG_CMD_SDRAM * print SDRAM configuration information

       (requires CONFIG_CMD_I2C)

  CONFIG_CMD_SETGETDCR   Support for DCR Register access

       (4xx only)

  CONFIG_CMD_SHA1SUM   print sha1 memory digest

       (requires CONFIG_CMD_MEMORY)

  CONFIG_CMD_SOURCE   "source" command Support

  CONFIG_CMD_SPI  * SPI serial bus support

  CONFIG_CMD_TFTPSRV * TFTP transfer in server mode

  CONFIG_CMD_USB  * USB support

  CONFIG_CMD_CDP  * Cisco Discover Protocol support

  CONFIG_CMD_FSL  * Microblaze FSL support

  EXAMPLE: If you want all functions except of network support you can write:

  例如:如果你需要除網絡外的所有功能,你可以這樣寫:

  #include "config_cmd_all.h"

  #undef CONFIG_CMD_NET

 Other Commands:

  fdt (flattened device tree) command: CONFIG_OF_LIBFDT

 Note: Don't enable the "icache" and "dcache" commands (configuration option CONFIG_CMD_CACHE) unless you know what you (and your U-Boot users) are doing. Data cache cannot be enabled on systems like the 8xx or 8260 (where accesses to the IMMR region must be uncached), and it cannot be disabled on all other systems where we (mis-) use the data cache to hold an initial stack and some data.

 注意:不要使能指令cache和資料cache指令(配置CONFIG_CMD_CACHE選項),除非你知道你(和你的U-Boot使用者)知道你在做什麼。資料cache不能在像8xx或8260(這裡通路IMMR區域必須不能被緩存)這樣的系統中啟用,但是在其他一些系統中(mis-)資料cache不能被禁用,因為在這些地方我們要使用資料cache保持初始化堆棧和一些資料。

  XXX - this list needs to get updated!

  XXX - 這個清單需要更新

本篇文章來源于 Linux公社網站(www.linuxidc.com)  原文連結:http://www.linuxidc.com/Linux/2011-08/40559p2.htm

繼續閱讀