{"id":20161555,"url":"https://github.com/openipc/u-boot-t20","last_synced_at":"2025-09-01T14:35:06.848Z","repository":{"id":82260894,"uuid":"511627507","full_name":"OpenIPC/u-boot-t20","owner":"OpenIPC","description":"U-Boot for t20 group SoC's","archived":false,"fork":false,"pushed_at":"2022-11-14T16:44:19.000Z","size":16935,"stargazers_count":4,"open_issues_count":0,"forks_count":0,"subscribers_count":3,"default_branch":"master","last_synced_at":"2025-08-10T15:41:05.950Z","etag":null,"topics":["ingenic","openipc","t10","t20","u-boot","u-boot-openipc"],"latest_commit_sha":null,"homepage":"https://openipc.org","language":"C","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/OpenIPC.png","metadata":{"files":{"readme":"README","changelog":null,"contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2022-07-07T18:02:22.000Z","updated_at":"2025-03-28T04:13:27.000Z","dependencies_parsed_at":null,"dependency_job_id":"63960d30-022c-42b2-9b84-75d0afde5dd2","html_url":"https://github.com/OpenIPC/u-boot-t20","commit_stats":{"total_commits":8,"total_committers":3,"mean_commits":"2.6666666666666665","dds":0.25,"last_synced_commit":"91a90f127a9e6d51eb1b5995f9b2c4098f699ec8"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/OpenIPC/u-boot-t20","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenIPC%2Fu-boot-t20","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenIPC%2Fu-boot-t20/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenIPC%2Fu-boot-t20/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenIPC%2Fu-boot-t20/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/OpenIPC","download_url":"https://codeload.github.com/OpenIPC/u-boot-t20/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenIPC%2Fu-boot-t20/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":273140336,"owners_count":25052596,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-09-01T02:00:09.058Z","response_time":120,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ingenic","openipc","t10","t20","u-boot","u-boot-openipc"],"created_at":"2024-11-14T00:19:31.187Z","updated_at":"2025-09-01T14:35:06.783Z","avatar_url":"https://github.com/OpenIPC.png","language":"C","readme":"#\n# (C) Copyright 2000 - 2012\n# Wolfgang Denk, DENX Software Engineering, wd@denx.de.\n#\n# See file CREDITS for list of people who contributed to this\n# project.\n#\n# This program is free software; you can redistribute it and/or\n# modify it under the terms of the GNU General Public License as\n# published by the Free Software Foundation; either version 2 of\n# the License, or (at your option) any later version.\n#\n# This program is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.\tSee the\n# GNU General Public License for more details.\n#\n# You should have received a copy of the GNU General Public License\n# along with this program; if not, write to the Free Software\n# Foundation, Inc., 59 Temple Place, Suite 330, Boston,\n# MA 02111-1307 USA\n#\n\nSummary:\n========\n\nThis directory contains the source code for U-Boot, a boot loader for\nEmbedded boards based on PowerPC, ARM, MIPS and several other\nprocessors, which can be installed in a boot ROM and used to\ninitialize and test the hardware or to download and run application\ncode.\n\nThe development of U-Boot is closely related to Linux: some parts of\nthe source code originate in the Linux source tree, we have some\nheader files in common, and special provision has been made to\nsupport booting of Linux images.\n\nSome attention has been paid to make this software easily\nconfigurable and extendable. For instance, all monitor commands are\nimplemented with the same call interface, so that it's very easy to\nadd new commands. Also, instead of permanently adding rarely used\ncode (for instance hardware test utilities) to the monitor, you can\nload and run it dynamically.\n\n\nStatus:\n=======\n\nIn general, all boards for which a configuration option exists in the\nMakefile have been tested to some extent and can be considered\n\"working\". In fact, many of them are used in production systems.\n\nIn case of problems see the CHANGELOG and CREDITS files to find out\nwho contributed the specific port. The MAINTAINERS file lists board\nmaintainers.\n\nNote: There is no CHANGELOG file in the actual U-Boot source tree;\nit can be created dynamically from the Git log using:\n\n\tmake CHANGELOG\n\n\nWhere to get help:\n==================\n\nIn case you have questions about, problems with or contributions for\nU-Boot you should send a message to the U-Boot mailing list at\n\u003cu-boot@lists.denx.de\u003e. There is also an archive of previous traffic\non the mailing list - please search the archive before asking FAQ's.\nPlease see http://lists.denx.de/pipermail/u-boot and\nhttp://dir.gmane.org/gmane.comp.boot-loaders.u-boot\n\n\nWhere to get source code:\n=========================\n\nThe U-Boot source code is maintained in the git repository at\ngit://www.denx.de/git/u-boot.git ; you can browse it online at\nhttp://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary\n\nThe \"snapshot\" links on this page allow you to download tarballs of\nany version you might be interested in. Official releases are also\navailable for FTP download from the ftp://ftp.denx.de/pub/u-boot/\ndirectory.\n\nPre-built (and tested) images are available from\nftp://ftp.denx.de/pub/u-boot/images/\n\n\nWhere we come from:\n===================\n\n- start from 8xxrom sources\n- create PPCBoot project (http://sourceforge.net/projects/ppcboot)\n- clean up code\n- make it easier to add custom boards\n- make it possible to add other [PowerPC] CPUs\n- extend functions, especially:\n  * Provide extended interface to Linux boot loader\n  * S-Record download\n  * network boot\n  * PCMCIA / CompactFlash / ATA disk / SCSI ... boot\n- create ARMBoot project (http://sourceforge.net/projects/armboot)\n- add other CPU families (starting with ARM)\n- create U-Boot project (http://sourceforge.net/projects/u-boot)\n- current project page: see http://www.denx.de/wiki/U-Boot\n\n\nNames and Spelling:\n===================\n\nThe \"official\" name of this project is \"Das U-Boot\". The spelling\n\"U-Boot\" shall be used in all written text (documentation, comments\nin source files etc.). Example:\n\n\tThis is the README file for the U-Boot project.\n\nFile names etc. shall be based on the string \"u-boot\". Examples:\n\n\tinclude/asm-ppc/u-boot.h\n\n\t#include \u003casm/u-boot.h\u003e\n\nVariable names, preprocessor constants etc. shall be either based on\nthe string \"u_boot\" or on \"U_BOOT\". Example:\n\n\tU_BOOT_VERSION\t\tu_boot_logo\n\tIH_OS_U_BOOT\t\tu_boot_hush_start\n\n\nVersioning:\n===========\n\nStarting with the release in October 2008, the names of the releases\nwere changed from numerical release numbers without deeper meaning\ninto a time stamp based numbering. Regular releases are identified by\nnames consisting of the calendar year and month of the release date.\nAdditional fields (if present) indicate release candidates or bug fix\nreleases in \"stable\" maintenance trees.\n\nExamples:\n\tU-Boot v2009.11\t    - Release November 2009\n\tU-Boot v2009.11.1   - Release 1 in version November 2009 stable tree\n\tU-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release\n\n\nDirectory Hierarchy:\n====================\n\n/arch\t\t\tArchitecture specific files\n  /arm\t\t\tFiles generic to ARM architecture\n    /cpu\t\tCPU specific files\n      /arm720t\t\tFiles specific to ARM 720 CPUs\n      /arm920t\t\tFiles specific to ARM 920 CPUs\n\t/at91\t\tFiles specific to Atmel AT91RM9200 CPU\n\t/imx\t\tFiles specific to Freescale MC9328 i.MX CPUs\n\t/s3c24x0\tFiles specific to Samsung S3C24X0 CPUs\n      /arm925t\t\tFiles specific to ARM 925 CPUs\n      /arm926ejs\tFiles specific to ARM 926 CPUs\n      /arm1136\t\tFiles specific to ARM 1136 CPUs\n      /ixp\t\tFiles specific to Intel XScale IXP CPUs\n      /pxa\t\tFiles specific to Intel XScale PXA CPUs\n      /s3c44b0\t\tFiles specific to Samsung S3C44B0 CPUs\n      /sa1100\t\tFiles specific to Intel StrongARM SA1100 CPUs\n    /lib\t\tArchitecture specific library files\n  /avr32\t\tFiles generic to AVR32 architecture\n    /cpu\t\tCPU specific files\n    /lib\t\tArchitecture specific library files\n  /blackfin\t\tFiles generic to Analog Devices Blackfin architecture\n    /cpu\t\tCPU specific files\n    /lib\t\tArchitecture specific library files\n  /x86\t\t\tFiles generic to x86 architecture\n    /cpu\t\tCPU specific files\n    /lib\t\tArchitecture specific library files\n  /m68k\t\t\tFiles generic to m68k architecture\n    /cpu\t\tCPU specific files\n      /mcf52x2\t\tFiles specific to Freescale ColdFire MCF52x2 CPUs\n      /mcf5227x\t\tFiles specific to Freescale ColdFire MCF5227x CPUs\n      /mcf532x\t\tFiles specific to Freescale ColdFire MCF5329 CPUs\n      /mcf5445x\t\tFiles specific to Freescale ColdFire MCF5445x CPUs\n      /mcf547x_8x\tFiles specific to Freescale ColdFire MCF547x_8x CPUs\n    /lib\t\tArchitecture specific library files\n  /microblaze\t\tFiles generic to microblaze architecture\n    /cpu\t\tCPU specific files\n    /lib\t\tArchitecture specific library files\n  /mips\t\t\tFiles generic to MIPS architecture\n    /cpu\t\tCPU specific files\n      /mips32\t\tFiles specific to MIPS32 CPUs\n      /xburst\t\tFiles specific to Ingenic XBurst CPUs\n    /lib\t\tArchitecture specific library files\n  /nds32\t\tFiles generic to NDS32 architecture\n    /cpu\t\tCPU specific files\n      /n1213\t\tFiles specific to Andes Technology N1213 CPUs\n    /lib\t\tArchitecture specific library files\n  /nios2\t\tFiles generic to Altera NIOS2 architecture\n    /cpu\t\tCPU specific files\n    /lib\t\tArchitecture specific library files\n  /powerpc\t\tFiles generic to PowerPC architecture\n    /cpu\t\tCPU specific files\n      /74xx_7xx\t\tFiles specific to Freescale MPC74xx and 7xx CPUs\n      /mpc5xx\t\tFiles specific to Freescale MPC5xx CPUs\n      /mpc5xxx\t\tFiles specific to Freescale MPC5xxx CPUs\n      /mpc8xx\t\tFiles specific to Freescale MPC8xx CPUs\n      /mpc824x\t\tFiles specific to Freescale MPC824x CPUs\n      /mpc8260\t\tFiles specific to Freescale MPC8260 CPUs\n      /mpc85xx\t\tFiles specific to Freescale MPC85xx CPUs\n      /ppc4xx\t\tFiles specific to AMCC PowerPC 4xx CPUs\n    /lib\t\tArchitecture specific library files\n  /sh\t\t\tFiles generic to SH architecture\n    /cpu\t\tCPU specific files\n      /sh2\t\tFiles specific to sh2 CPUs\n      /sh3\t\tFiles specific to sh3 CPUs\n      /sh4\t\tFiles specific to sh4 CPUs\n    /lib\t\tArchitecture specific library files\n  /sparc\t\tFiles generic to SPARC architecture\n    /cpu\t\tCPU specific files\n      /leon2\t\tFiles specific to Gaisler LEON2 SPARC CPU\n      /leon3\t\tFiles specific to Gaisler LEON3 SPARC CPU\n    /lib\t\tArchitecture specific library files\n/api\t\t\tMachine/arch independent API for external apps\n/board\t\t\tBoard dependent files\n/common\t\t\tMisc architecture independent functions\n/disk\t\t\tCode for disk drive partition handling\n/doc\t\t\tDocumentation (don't expect too much)\n/drivers\t\tCommonly used device drivers\n/examples\t\tExample code for standalone applications, etc.\n/fs\t\t\tFilesystem code (cramfs, ext2, jffs2, etc.)\n/include\t\tHeader Files\n/lib\t\t\tFiles generic to all architectures\n  /libfdt\t\tLibrary files to support flattened device trees\n  /lzma\t\t\tLibrary files to support LZMA decompression\n  /lzo\t\t\tLibrary files to support LZO decompression\n/net\t\t\tNetworking code\n/post\t\t\tPower On Self Test\n/rtc\t\t\tReal Time Clock drivers\n/tools\t\t\tTools to build S-Record or U-Boot images, etc.\n\nSoftware Configuration:\n=======================\n\nConfiguration is usually done using C preprocessor defines; the\nrationale behind that is to avoid dead code whenever possible.\n\nThere are two classes of configuration variables:\n\n* Configuration _OPTIONS_:\n  These are selectable by the user and have names beginning with\n  \"CONFIG_\".\n\n* Configuration _SETTINGS_:\n  These depend on the hardware etc. and should not be meddled with if\n  you don't know what you're doing; they have names beginning with\n  \"CONFIG_SYS_\".\n\nLater we will add a configuration tool - probably similar to or even\nidentical to what's used for the Linux kernel. Right now, we have to\ndo the configuration by hand, which means creating some symbolic\nlinks and editing some configuration files. We use the TQM8xxL boards\nas an example here.\n\n\nSelection of Processor Architecture and Board Type:\n---------------------------------------------------\n\nFor all supported boards there are ready-to-use default\nconfigurations available; just type \"make \u003cboard_name\u003e_config\".\n\nExample: For a TQM823L module type:\n\n\tcd u-boot\n\tmake TQM823L_config\n\nFor the Cogent platform, you need to specify the CPU type as well;\ne.g. \"make cogent_mpc8xx_config\". And also configure the cogent\ndirectory according to the instructions in cogent/README.\n\n\nConfiguration Options:\n----------------------\n\nConfiguration depends on the combination of board and CPU type; all\nsuch information is kept in a configuration file\n\"include/configs/\u003cboard_name\u003e.h\".\n\nExample: For a TQM823L module, all configuration settings are in\n\"include/configs/TQM823L.h\".\n\n\nMany of the options are named exactly as the corresponding Linux\nkernel configuration options. The intention is to make it easier to\nbuild a config tool - later.\n\n\nThe following options need to be configured:\n\n- CPU Type:\tDefine exactly one, e.g. CONFIG_MPC85XX.\n\n- Board Type:\tDefine exactly one, e.g. CONFIG_MPC8540ADS.\n\n- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)\n\t\tDefine exactly one, e.g. CONFIG_ATSTK1002\n\n- CPU Module Type: (if CONFIG_COGENT is defined)\n\t\tDefine exactly one of\n\t\tCONFIG_CMA286_60_OLD\n--- FIXME --- not tested yet:\n\t\tCONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,\n\t\tCONFIG_CMA287_23, CONFIG_CMA287_50\n\n- Motherboard Type: (if CONFIG_COGENT is defined)\n\t\tDefine exactly one of\n\t\tCONFIG_CMA101, CONFIG_CMA102\n\n- Motherboard I/O Modules: (if CONFIG_COGENT is defined)\n\t\tDefine one or more of\n\t\tCONFIG_CMA302\n\n- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)\n\t\tDefine one or more of\n\t\tCONFIG_LCD_HEARTBEAT\t- update a character position on\n\t\t\t\t\t  the LCD display every second with\n\t\t\t\t\t  a \"rotator\" |\\-/|\\-/\n\n- Board flavour: (if CONFIG_MPC8260ADS is defined)\n\t\tCONFIG_ADSTYPE\n\t\tPossible values are:\n\t\t\tCONFIG_SYS_8260ADS\t- original MPC8260ADS\n\t\t\tCONFIG_SYS_8266ADS\t- MPC8266ADS\n\t\t\tCONFIG_SYS_PQ2FADS\t- PQ2FADS-ZU or PQ2FADS-VR\n\t\t\tCONFIG_SYS_8272ADS\t- MPC8272ADS\n\n- Marvell Family Member\n\t\tCONFIG_SYS_MVFS\t\t- define it if you want to enable\n\t\t\t\t\t  multiple fs option at one time\n\t\t\t\t\t  for marvell soc family\n\n- MPC824X Family Member (if CONFIG_MPC824X is defined)\n\t\tDefine exactly one of\n\t\tCONFIG_MPC8240, CONFIG_MPC8245\n\n- 8xx CPU Options: (if using an MPC8xx CPU)\n\t\tCONFIG_8xx_GCLK_FREQ\t- deprecated: CPU clock if\n\t\t\t\t\t  get_gclk_freq() cannot work\n\t\t\t\t\t  e.g. if there is no 32KHz\n\t\t\t\t\t  reference PIT/RTC clock\n\t\tCONFIG_8xx_OSCLK\t- PLL input clock (either EXTCLK\n\t\t\t\t\t  or XTAL/EXTAL)\n\n- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):\n\t\tCONFIG_SYS_8xx_CPUCLK_MIN\n\t\tCONFIG_SYS_8xx_CPUCLK_MAX\n\t\tCONFIG_8xx_CPUCLK_DEFAULT\n\t\t\tSee doc/README.MPC866\n\n\t\tCONFIG_SYS_MEASURE_CPUCLK\n\n\t\tDefine this to measure the actual CPU clock instead\n\t\tof relying on the correctness of the configured\n\t\tvalues. Mostly useful for board bringup to make sure\n\t\tthe PLL is locked at the intended frequency. Note\n\t\tthat this requires a (stable) reference clock (32 kHz\n\t\tRTC clock or CONFIG_SYS_8XX_XIN)\n\n\t\tCONFIG_SYS_DELAYED_ICACHE\n\n\t\tDefine this option if you want to enable the\n\t\tICache only when Code runs from RAM.\n\n- 85xx CPU Options:\n\t\tCONFIG_SYS_PPC64\n\n\t\tSpecifies that the core is a 64-bit PowerPC implementation (implements\n\t\tthe \"64\" category of the Power ISA). This is necessary for ePAPR\n\t\tcompliance, among other possible reasons.\n\n\t\tCONFIG_SYS_FSL_TBCLK_DIV\n\n\t\tDefines the core time base clock divider ratio compared to the\n\t\tsystem clock.  On most PQ3 devices this is 8, on newer QorIQ\n\t\tdevices it can be 16 or 32.  The ratio varies from SoC to Soc.\n\n\t\tCONFIG_SYS_FSL_PCIE_COMPAT\n\n\t\tDefines the string to utilize when trying to match PCIe device\n\t\ttree nodes for the given platform.\n\n\t\tCONFIG_SYS_PPC_E500_DEBUG_TLB\n\n\t\tEnables a temporary TLB entry to be used during boot to work\n\t\taround limitations in e500v1 and e500v2 external debugger\n\t\tsupport. This reduces the portions of the boot code where\n\t\tbreakpoints and single stepping do not work.  The value of this\n\t\tsymbol should be set to the TLB1 entry to be used for this\n\t\tpurpose.\n\n\t\tCONFIG_SYS_FSL_ERRATUM_A004510\n\n\t\tEnables a workaround for erratum A004510.  If set,\n\t\tthen CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and\n\t\tCONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set.\n\n\t\tCONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV\n\t\tCONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional)\n\n\t\tDefines one or two SoC revisions (low 8 bits of SVR)\n\t\tfor which the A004510 workaround should be applied.\n\n\t\tThe rest of SVR is either not relevant to the decision\n\t\tof whether the erratum is present (e.g. p2040 versus\n\t\tp2041) or is implied by the build target, which controls\n\t\twhether CONFIG_SYS_FSL_ERRATUM_A004510 is set.\n\n\t\tSee Freescale App Note 4493 for more information about\n\t\tthis erratum.\n\n\t\tCONFIG_A003399_NOR_WORKAROUND\n\t\tEnables a workaround for IFC erratum A003399. It is only\n\t\trequred during NOR boot.\n\n\t\tCONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY\n\n\t\tThis is the value to write into CCSR offset 0x18600\n\t\taccording to the A004510 workaround.\n\n\t\tCONFIG_SYS_FSL_DSP_M2_RAM_ADDR\n\t\tThis value denotes start offset of M2 memory\n\t\twhich is directly connected to the DSP core.\n\n\t\tCONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT\n\t\tThis value denotes start offset of DSP CCSR space.\n\n- Generic CPU options:\n\t\tCONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN\n\n\t\tDefines the endianess of the CPU. Implementation of those\n\t\tvalues is arch specific.\n\n- Intel Monahans options:\n\t\tCONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO\n\n\t\tDefines the Monahans run mode to oscillator\n\t\tratio. Valid values are 8, 16, 24, 31. The core\n\t\tfrequency is this value multiplied by 13 MHz.\n\n\t\tCONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO\n\n\t\tDefines the Monahans turbo mode to oscillator\n\t\tratio. Valid values are 1 (default if undefined) and\n\t\t2. The core frequency as calculated above is multiplied\n\t\tby this value.\n\n- MIPS CPU options:\n\t\tCONFIG_SYS_INIT_SP_OFFSET\n\n\t\tOffset relative to CONFIG_SYS_SDRAM_BASE for initial stack\n\t\tpointer. This is needed for the temporary stack before\n\t\trelocation.\n\n\t\tCONFIG_SYS_MIPS_CACHE_MODE\n\n\t\tCache operation mode for the MIPS CPU.\n\t\tSee also arch/mips/include/asm/mipsregs.h.\n\t\tPossible values are:\n\t\t\tCONF_CM_CACHABLE_NO_WA\n\t\t\tCONF_CM_CACHABLE_WA\n\t\t\tCONF_CM_UNCACHED\n\t\t\tCONF_CM_CACHABLE_NONCOHERENT\n\t\t\tCONF_CM_CACHABLE_CE\n\t\t\tCONF_CM_CACHABLE_COW\n\t\t\tCONF_CM_CACHABLE_CUW\n\t\t\tCONF_CM_CACHABLE_ACCELERATED\n\n\t\tCONFIG_SYS_XWAY_EBU_BOOTCFG\n\n\t\tSpecial option for Lantiq XWAY SoCs for booting from NOR flash.\n\t\tSee also arch/mips/cpu/mips32/start.S.\n\n\t\tCONFIG_XWAY_SWAP_BYTES\n\n\t\tEnable compilation of tools/xway-swap-bytes needed for Lantiq\n\t\tXWAY SoCs for booting from NOR flash. The U-Boot image needs to\n\t\tbe swapped if a flash programmer is used.\n\n- ARM options:\n\t\tCONFIG_SYS_EXCEPTION_VECTORS_HIGH\n\n\t\tSelect high exception vectors of the ARM core, e.g., do not\n\t\tclear the V bit of the c1 register of CP15.\n\n\t\tCONFIG_SYS_THUMB_BUILD\n\n\t\tUse this flag to build U-Boot using the Thumb instruction\n\t\tset for ARM architectures. Thumb instruction set provides\n\t\tbetter code density. For ARM architectures that support\n\t\tThumb2 this flag will result in Thumb2 code generated by\n\t\tGCC.\n\n\t\tCONFIG_ARM_ERRATA_716044\n\t\tCONFIG_ARM_ERRATA_742230\n\t\tCONFIG_ARM_ERRATA_743622\n\t\tCONFIG_ARM_ERRATA_751472\n\n\t\tIf set, the workarounds for these ARM errata are applied early\n\t\tduring U-Boot startup. Note that these options force the\n\t\tworkarounds to be applied; no CPU-type/version detection\n\t\texists, unlike the similar options in the Linux kernel. Do not\n\t\tset these options unless they apply!\n\n- CPU timer options:\n\t\tCONFIG_SYS_HZ\n\n\t\tThe frequency of the timer returned by get_timer().\n\t\tget_timer() must operate in milliseconds and this CONFIG\n\t\toption must be set to 1000.\n\n- Linux Kernel Interface:\n\t\tCONFIG_CLOCKS_IN_MHZ\n\n\t\tU-Boot stores all clock information in Hz\n\t\tinternally. For binary compatibility with older Linux\n\t\tkernels (which expect the clocks passed in the\n\t\tbd_info data to be in MHz) the environment variable\n\t\t\"clocks_in_mhz\" can be defined so that U-Boot\n\t\tconverts clock data to MHZ before passing it to the\n\t\tLinux kernel.\n\t\tWhen CONFIG_CLOCKS_IN_MHZ is defined, a definition of\n\t\t\"clocks_in_mhz=1\" is automatically included in the\n\t\tdefault environment.\n\n\t\tCONFIG_MEMSIZE_IN_BYTES\t\t[relevant for MIPS only]\n\n\t\tWhen transferring memsize parameter to linux, some versions\n\t\texpect it to be in bytes, others in MB.\n\t\tDefine CONFIG_MEMSIZE_IN_BYTES to make it in bytes.\n\n\t\tCONFIG_OF_LIBFDT\n\n\t\tNew kernel versions are expecting firmware settings to be\n\t\tpassed using flattened device trees (based on open firmware\n\t\tconcepts).\n\n\t\tCONFIG_OF_LIBFDT\n\t\t * New libfdt-based support\n\t\t * Adds the \"fdt\" command\n\t\t * The bootm command automatically updates the fdt\n\n\t\tOF_CPU - The proper name of the cpus node (only required for\n\t\t\tMPC512X and MPC5xxx based boards).\n\t\tOF_SOC - The proper name of the soc node (only required for\n\t\t\tMPC512X and MPC5xxx based boards).\n\t\tOF_TBCLK - The timebase frequency.\n\t\tOF_STDOUT_PATH - The path to the console device\n\n\t\tboards with QUICC Engines require OF_QE to set UCC MAC\n\t\taddresses\n\n\t\tCONFIG_OF_BOARD_SETUP\n\n\t\tBoard code has addition modification that it wants to make\n\t\tto the flat device tree before handing it off to the kernel\n\n\t\tCONFIG_OF_BOOT_CPU\n\n\t\tThis define fills in the correct boot CPU in the boot\n\t\tparam header, the default value is zero if undefined.\n\n\t\tCONFIG_OF_IDE_FIXUP\n\n\t\tU-Boot can detect if an IDE device is present or not.\n\t\tIf not, and this new config option is activated, U-Boot\n\t\tremoves the ATA node from the DTS before booting Linux,\n\t\tso the Linux IDE driver does not probe the device and\n\t\tcrash. This is needed for buggy hardware (uc101) where\n\t\tno pull down resistor is connected to the signal IDE5V_DD7.\n\n\t\tCONFIG_MACH_TYPE\t[relevant for ARM only][mandatory]\n\n\t\tThis setting is mandatory for all boards that have only one\n\t\tmachine type and must be used to specify the machine type\n\t\tnumber as it appears in the ARM machine registry\n\t\t(see http://www.arm.linux.org.uk/developer/machines/).\n\t\tOnly boards that have multiple machine types supported\n\t\tin a single configuration file and the machine type is\n\t\truntime discoverable, do not have to use this setting.\n\n- vxWorks boot parameters:\n\n\t\tbootvx constructs a valid bootline using the following\n\t\tenvironments variables: bootfile, ipaddr, serverip, hostname.\n\t\tIt loads the vxWorks image pointed bootfile.\n\n\t\tCONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name\n\t\tCONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address\n\t\tCONFIG_SYS_VXWORKS_SERVERNAME - Name of the server\n\t\tCONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters\n\n\t\tCONFIG_SYS_VXWORKS_ADD_PARAMS\n\n\t\tAdd it at the end of the bootline. E.g \"u=username pw=secret\"\n\n\t\tNote: If a \"bootargs\" environment is defined, it will overwride\n\t\tthe defaults discussed just above.\n\n- Cache Configuration:\n\t\tCONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot\n\t\tCONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot\n\t\tCONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot\n\n- Cache Configuration for ARM:\n\t\tCONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache\n\t\t\t\t      controller\n\t\tCONFIG_SYS_PL310_BASE - Physical base address of PL310\n\t\t\t\t\tcontroller register space\n\n- Serial Ports:\n\t\tCONFIG_PL010_SERIAL\n\n\t\tDefine this if you want support for Amba PrimeCell PL010 UARTs.\n\n\t\tCONFIG_PL011_SERIAL\n\n\t\tDefine this if you want support for Amba PrimeCell PL011 UARTs.\n\n\t\tCONFIG_PL011_CLOCK\n\n\t\tIf you have Amba PrimeCell PL011 UARTs, set this variable to\n\t\tthe clock speed of the UARTs.\n\n\t\tCONFIG_PL01x_PORTS\n\n\t\tIf you have Amba PrimeCell PL010 or PL011 UARTs on your board,\n\t\tdefine this to a list of base addresses for each (supported)\n\t\tport. See e.g. include/configs/versatile.h\n\n\t\tCONFIG_PL011_SERIAL_RLCR\n\n\t\tSome vendor versions of PL011 serial ports (e.g. ST-Ericsson U8500)\n\t\thave separate receive and transmit line control registers.  Set\n\t\tthis variable to initialize the extra register.\n\n\t\tCONFIG_PL011_SERIAL_FLUSH_ON_INIT\n\n\t\tOn some platforms (e.g. U8500) U-Boot is loaded by a second stage\n\t\tboot loader that has already initialized the UART.  Define this\n\t\tvariable to flush the UART at init time.\n\n\n- Console Interface:\n\t\tDepending on board, define exactly one serial port\n\t\t(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,\n\t\tCONFIG_8xx_CONS_SCC1, ...), or switch off the serial\n\t\tconsole by defining CONFIG_8xx_CONS_NONE\n\n\t\tNote: if CONFIG_8xx_CONS_NONE is defined, the serial\n\t\tport routines must be defined elsewhere\n\t\t(i.e. serial_init(), serial_getc(), ...)\n\n\t\tCONFIG_CFB_CONSOLE\n\t\tEnables console device for a color framebuffer. Needs following\n\t\tdefines (cf. smiLynxEM, i8042)\n\t\t\tVIDEO_FB_LITTLE_ENDIAN\tgraphic memory organisation\n\t\t\t\t\t\t(default big endian)\n\t\t\tVIDEO_HW_RECTFILL\tgraphic chip supports\n\t\t\t\t\t\trectangle fill\n\t\t\t\t\t\t(cf. smiLynxEM)\n\t\t\tVIDEO_HW_BITBLT\t\tgraphic chip supports\n\t\t\t\t\t\tbit-blit (cf. smiLynxEM)\n\t\t\tVIDEO_VISIBLE_COLS\tvisible pixel columns\n\t\t\t\t\t\t(cols=pitch)\n\t\t\tVIDEO_VISIBLE_ROWS\tvisible pixel rows\n\t\t\tVIDEO_PIXEL_SIZE\tbytes per pixel\n\t\t\tVIDEO_DATA_FORMAT\tgraphic data format\n\t\t\t\t\t\t(0-5, cf. cfb_console.c)\n\t\t\tVIDEO_FB_ADRS\t\tframebuffer address\n\t\t\tVIDEO_KBD_INIT_FCT\tkeyboard int fct\n\t\t\t\t\t\t(i.e. i8042_kbd_init())\n\t\t\tVIDEO_TSTC_FCT\t\ttest char fct\n\t\t\t\t\t\t(i.e. i8042_tstc)\n\t\t\tVIDEO_GETC_FCT\t\tget char fct\n\t\t\t\t\t\t(i.e. i8042_getc)\n\t\t\tCONFIG_CONSOLE_CURSOR\tcursor drawing on/off\n\t\t\t\t\t\t(requires blink timer\n\t\t\t\t\t\tcf. i8042.c)\n\t\t\tCONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)\n\t\t\tCONFIG_CONSOLE_TIME\tdisplay time/date info in\n\t\t\t\t\t\tupper right corner\n\t\t\t\t\t\t(requires CONFIG_CMD_DATE)\n\t\t\tCONFIG_VIDEO_LOGO\tdisplay Linux logo in\n\t\t\t\t\t\tupper left corner\n\t\t\tCONFIG_VIDEO_BMP_LOGO\tuse bmp_logo.h instead of\n\t\t\t\t\t\tlinux_logo.h for logo.\n\t\t\t\t\t\tRequires CONFIG_VIDEO_LOGO\n\t\t\tCONFIG_CONSOLE_EXTRA_INFO\n\t\t\t\t\t\tadditional board info beside\n\t\t\t\t\t\tthe logo\n\n\t\tWhen CONFIG_CFB_CONSOLE_ANSI is defined, console will support\n\t\ta limited number of ANSI escape sequences (cursor control,\n\t\terase functions and limited graphics rendition control).\n\n\t\tWhen CONFIG_CFB_CONSOLE is defined, video console is\n\t\tdefault i/o. Serial console can be forced with\n\t\tenvironment 'console=serial'.\n\n\t\tWhen CONFIG_SILENT_CONSOLE is defined, all console\n\t\tmessages (by U-Boot and Linux!) can be silenced with\n\t\tthe \"silent\" environment variable. See\n\t\tdoc/README.silent for more information.\n\n- Console Baudrate:\n\t\tCONFIG_BAUDRATE - in bps\n\t\tSelect one of the baudrates listed in\n\t\tCONFIG_SYS_BAUDRATE_TABLE, see below.\n\t\tCONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale\n\n- Console Rx buffer length\n\t\tWith CONFIG_SYS_SMC_RXBUFLEN it is possible to define\n\t\tthe maximum receive buffer length for the SMC.\n\t\tThis option is actual only for 82xx and 8xx possible.\n\t\tIf using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE\n\t\tmust be defined, to setup the maximum idle timeout for\n\t\tthe SMC.\n\n- Pre-Console Buffer:\n\t\tPrior to the console being initialised (i.e. serial UART\n\t\tinitialised etc) all console output is silently discarded.\n\t\tDefining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to\n\t\tbuffer any console messages prior to the console being\n\t\tinitialised to a buffer of size CONFIG_PRE_CON_BUF_SZ\n\t\tbytes located at CONFIG_PRE_CON_BUF_ADDR. The buffer is\n\t\ta circular buffer, so if more than CONFIG_PRE_CON_BUF_SZ\n\t\tbytes are output before the console is initialised, the\n\t\tearlier bytes are discarded.\n\n\t\t'Sane' compilers will generate smaller code if\n\t\tCONFIG_PRE_CON_BUF_SZ is a power of 2\n\n- Safe printf() functions\n\t\tDefine CONFIG_SYS_VSNPRINTF to compile in safe versions of\n\t\tthe printf() functions. These are defined in\n\t\tinclude/vsprintf.h and include snprintf(), vsnprintf() and\n\t\tso on. Code size increase is approximately 300-500 bytes.\n\t\tIf this option is not given then these functions will\n\t\tsilently discard their buffer size argument - this means\n\t\tyou are not getting any overflow checking in this case.\n\n- Boot Delay:\tCONFIG_BOOTDELAY - in seconds\n\t\tDelay before automatically booting the default image;\n\t\tset to -1 to disable autoboot.\n\t\tset to -2 to autoboot with no delay and not check for abort\n\t\t(even when CONFIG_ZERO_BOOTDELAY_CHECK is defined).\n\n\t\tSee doc/README.autoboot for these options that\n\t\twork with CONFIG_BOOTDELAY. None are required.\n\t\tCONFIG_BOOT_RETRY_TIME\n\t\tCONFIG_BOOT_RETRY_MIN\n\t\tCONFIG_AUTOBOOT_KEYED\n\t\tCONFIG_AUTOBOOT_PROMPT\n\t\tCONFIG_AUTOBOOT_DELAY_STR\n\t\tCONFIG_AUTOBOOT_STOP_STR\n\t\tCONFIG_AUTOBOOT_DELAY_STR2\n\t\tCONFIG_AUTOBOOT_STOP_STR2\n\t\tCONFIG_ZERO_BOOTDELAY_CHECK\n\t\tCONFIG_RESET_TO_RETRY\n\n- Autoboot Command:\n\t\tCONFIG_BOOTCOMMAND\n\t\tOnly needed when CONFIG_BOOTDELAY is enabled;\n\t\tdefine a command string that is automatically executed\n\t\twhen no character is read on the console interface\n\t\twithin \"Boot Delay\" after reset.\n\n\t\tCONFIG_BOOTARGS\n\t\tThis can be used to pass arguments to the bootm\n\t\tcommand. The value of CONFIG_BOOTARGS goes into the\n\t\tenvironment value \"bootargs\".\n\n\t\tCONFIG_RAMBOOT and CONFIG_NFSBOOT\n\t\tThe value of these goes into the environment as\n\t\t\"ramboot\" and \"nfsboot\" respectively, and can be used\n\t\tas a convenience, when switching between booting from\n\t\tRAM and NFS.\n\n- Pre-Boot Commands:\n\t\tCONFIG_PREBOOT\n\n\t\tWhen this option is #defined, the existence of the\n\t\tenvironment variable \"preboot\" will be checked\n\t\timmediately before starting the CONFIG_BOOTDELAY\n\t\tcountdown and/or running the auto-boot command resp.\n\t\tentering interactive mode.\n\n\t\tThis feature is especially useful when \"preboot\" is\n\t\tautomatically generated or modified. For an example\n\t\tsee the LWMON board specific code: here \"preboot\" is\n\t\tmodified when the user holds down a certain\n\t\tcombination of keys on the (special) keyboard when\n\t\tbooting the systems\n\n- Serial Download Echo Mode:\n\t\tCONFIG_LOADS_ECHO\n\t\tIf defined to 1, all characters received during a\n\t\tserial download (using the \"loads\" command) are\n\t\techoed back. This might be needed by some terminal\n\t\temulations (like \"cu\"), but may as well just take\n\t\ttime on others. This setting #define's the initial\n\t\tvalue of the \"loads_echo\" environment variable.\n\n- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)\n\t\tCONFIG_KGDB_BAUDRATE\n\t\tSelect one of the baudrates listed in\n\t\tCONFIG_SYS_BAUDRATE_TABLE, see below.\n\n- Monitor Functions:\n\t\tMonitor commands can be included or excluded\n\t\tfrom the build by using the #include files\n\t\t\u003cconfig_cmd_all.h\u003e and #undef'ing unwanted\n\t\tcommands, or using \u003cconfig_cmd_default.h\u003e\n\t\tand augmenting with additional #define's\n\t\tfor wanted commands.\n\n\t\tThe default command configuration includes all commands\n\t\texcept those marked below with a \"*\".\n\n\t\tCONFIG_CMD_ASKENV\t* ask for env variable\n\t\tCONFIG_CMD_BDI\t\t  bdinfo\n\t\tCONFIG_CMD_BEDBUG\t* Include BedBug Debugger\n\t\tCONFIG_CMD_BMP\t\t* BMP support\n\t\tCONFIG_CMD_BSP\t\t* Board specific commands\n\t\tCONFIG_CMD_BOOTD\t  bootd\n\t\tCONFIG_CMD_CACHE\t* icache, dcache\n\t\tCONFIG_CMD_CONSOLE\t  coninfo\n\t\tCONFIG_CMD_CRC32\t* crc32\n\t\tCONFIG_CMD_DATE\t\t* support for RTC, date/time...\n\t\tCONFIG_CMD_DHCP\t\t* DHCP support\n\t\tCONFIG_CMD_DIAG\t\t* Diagnostics\n\t\tCONFIG_CMD_DS4510\t* ds4510 I2C gpio commands\n\t\tCONFIG_CMD_DS4510_INFO\t* ds4510 I2C info command\n\t\tCONFIG_CMD_DS4510_MEM\t* ds4510 I2C eeprom/sram commansd\n\t\tCONFIG_CMD_DS4510_RST\t* ds4510 I2C rst command\n\t\tCONFIG_CMD_DTT\t\t* Digital Therm and Thermostat\n\t\tCONFIG_CMD_ECHO\t\t  echo arguments\n\t\tCONFIG_CMD_EDITENV\t  edit env variable\n\t\tCONFIG_CMD_EEPROM\t* EEPROM read/write support\n\t\tCONFIG_CMD_ELF\t\t* bootelf, bootvx\n\t\tCONFIG_CMD_ENV_CALLBACK\t* display details about env callbacks\n\t\tCONFIG_CMD_ENV_FLAGS\t* display details about env flags\n\t\tCONFIG_CMD_EXPORTENV\t* export the environment\n\t\tCONFIG_CMD_EXT2\t\t* ext2 command support\n\t\tCONFIG_CMD_EXT4\t\t* ext4 command support\n\t\tCONFIG_CMD_SAVEENV\t  saveenv\n\t\tCONFIG_CMD_FDC\t\t* Floppy Disk Support\n\t\tCONFIG_CMD_FAT\t\t* FAT command support\n\t\tCONFIG_CMD_FDOS\t\t* Dos diskette Support\n\t\tCONFIG_CMD_FLASH\t  flinfo, erase, protect\n\t\tCONFIG_CMD_FPGA\t\t  FPGA device initialization support\n\t\tCONFIG_CMD_FUSE\t\t* Device fuse support\n\t\tCONFIG_CMD_GETTIME\t* Get time since boot\n\t\tCONFIG_CMD_GO\t\t* the 'go' command (exec code)\n\t\tCONFIG_CMD_GREPENV\t* search environment\n\t\tCONFIG_CMD_HASH\t\t* calculate hash / digest\n\t\tCONFIG_CMD_HWFLOW\t* RTS/CTS hw flow control\n\t\tCONFIG_CMD_I2C\t\t* I2C serial bus support\n\t\tCONFIG_CMD_IDE\t\t* IDE harddisk support\n\t\tCONFIG_CMD_IMI\t\t  iminfo\n\t\tCONFIG_CMD_IMLS\t\t  List all images found in NOR flash\n\t\tCONFIG_CMD_IMLS_NAND\t* List all images found in NAND flash\n\t\tCONFIG_CMD_IMMAP\t* IMMR dump support\n\t\tCONFIG_CMD_IMPORTENV\t* import an environment\n\t\tCONFIG_CMD_INI\t\t* import data from an ini file into the env\n\t\tCONFIG_CMD_IRQ\t\t* irqinfo\n\t\tCONFIG_CMD_ITEST\t  Integer/string test of 2 values\n\t\tCONFIG_CMD_JFFS2\t* JFFS2 Support\n\t\tCONFIG_CMD_KGDB\t\t* kgdb\n\t\tCONFIG_CMD_LDRINFO\t* ldrinfo (display Blackfin loader)\n\t\tCONFIG_CMD_LINK_LOCAL\t* link-local IP address auto-configuration\n\t\t\t\t\t  (169.254.*.*)\n\t\tCONFIG_CMD_LOADB\t  loadb\n\t\tCONFIG_CMD_LOADS\t  loads\n\t\tCONFIG_CMD_MD5SUM\t* print md5 message digest\n\t\t\t\t\t  (requires CONFIG_CMD_MEMORY and CONFIG_MD5)\n\t\tCONFIG_CMD_MEMINFO\t* Display detailed memory information\n\t\tCONFIG_CMD_MEMORY\t  md, mm, nm, mw, cp, cmp, crc, base,\n\t\t\t\t\t  loop, loopw\n\t\tCONFIG_CMD_MEMTEST\t* mtest\n\t\tCONFIG_CMD_MISC\t\t  Misc functions like sleep etc\n\t\tCONFIG_CMD_MMC\t\t* MMC memory mapped support\n\t\tCONFIG_CMD_MII\t\t* MII utility commands\n\t\tCONFIG_CMD_MTDPARTS\t* MTD partition support\n\t\tCONFIG_CMD_NAND\t\t* NAND support\n\t\tCONFIG_CMD_NET\t\t  bootp, tftpboot, rarpboot\n\t\tCONFIG_CMD_NFS\t\t  NFS support\n\t\tCONFIG_CMD_PCA953X\t* PCA953x I2C gpio commands\n\t\tCONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command\n\t\tCONFIG_CMD_PCI\t\t* pciinfo\n\t\tCONFIG_CMD_PCMCIA\t\t* PCMCIA support\n\t\tCONFIG_CMD_PING\t\t* send ICMP ECHO_REQUEST to network\n\t\t\t\t\t  host\n\t\tCONFIG_CMD_PORTIO\t* Port I/O\n\t\tCONFIG_CMD_READ\t\t* Read raw data from partition\n\t\tCONFIG_CMD_REGINFO\t* Register dump\n\t\tCONFIG_CMD_RUN\t\t  run command in env variable\n\t\tCONFIG_CMD_SANDBOX\t* sb command to access sandbox features\n\t\tCONFIG_CMD_SAVES\t* save S record dump\n\t\tCONFIG_CMD_SCSI\t\t* SCSI Support\n\t\tCONFIG_CMD_SDRAM\t* print SDRAM configuration information\n\t\t\t\t\t  (requires CONFIG_CMD_I2C)\n\t\tCONFIG_CMD_SETGETDCR\t  Support for DCR Register access\n\t\t\t\t\t  (4xx only)\n\t\tCONFIG_CMD_SF\t\t* Read/write/erase SPI NOR flash\n\t\tCONFIG_CMD_SHA1SUM\t* print sha1 memory digest\n\t\t\t\t\t  (requires CONFIG_CMD_MEMORY)\n\t\tCONFIG_CMD_SOFTSWITCH\t* Soft switch setting command for BF60x\n\t\tCONFIG_CMD_SOURCE\t  \"source\" command Support\n\t\tCONFIG_CMD_SPI\t\t* SPI serial bus support\n\t\tCONFIG_CMD_TFTPSRV\t* TFTP transfer in server mode\n\t\tCONFIG_CMD_TFTPPUT\t* TFTP put command (upload)\n\t\tCONFIG_CMD_TIME\t\t* run command and report execution time (ARM specific)\n\t\tCONFIG_CMD_TIMER\t* access to the system tick timer\n\t\tCONFIG_CMD_USB\t\t* USB support\n\t\tCONFIG_CMD_CDP\t\t* Cisco Discover Protocol support\n\t\tCONFIG_CMD_MFSL\t\t* Microblaze FSL support\n\t\tCONFIG_CMD_XIMG\t\t  Load part of Multi Image\n\n\n\t\tEXAMPLE: If you want all functions except of network\n\t\tsupport you can write:\n\n\t\t#include \"config_cmd_all.h\"\n\t\t#undef CONFIG_CMD_NET\n\n\tOther Commands:\n\t\tfdt (flattened device tree) command: CONFIG_OF_LIBFDT\n\n\tNote:\tDon't enable the \"icache\" and \"dcache\" commands\n\t\t(configuration option CONFIG_CMD_CACHE) unless you know\n\t\twhat you (and your U-Boot users) are doing. Data\n\t\tcache cannot be enabled on systems like the 8xx or\n\t\t8260 (where accesses to the IMMR region must be\n\t\tuncached), and it cannot be disabled on all other\n\t\tsystems where we (mis-) use the data cache to hold an\n\t\tinitial stack and some data.\n\n\n\t\tXXX - this list needs to get updated!\n\n- Regular expression support:\n\t\tCONFIG_REGEX\n                If this variable is defined, U-Boot is linked against\n                the SLRE (Super Light Regular Expression) library,\n                which adds regex support to some commands, as for\n                example \"env grep\" and \"setexpr\".\n\n- Device tree:\n\t\tCONFIG_OF_CONTROL\n\t\tIf this variable is defined, U-Boot will use a device tree\n\t\tto configure its devices, instead of relying on statically\n\t\tcompiled #defines in the board file. This option is\n\t\texperimental and only available on a few boards. The device\n\t\ttree is available in the global data as gd-\u003efdt_blob.\n\n\t\tU-Boot needs to get its device tree from somewhere. This can\n\t\tbe done using one of the two options below:\n\n\t\tCONFIG_OF_EMBED\n\t\tIf this variable is defined, U-Boot will embed a device tree\n\t\tbinary in its image. This device tree file should be in the\n\t\tboard directory and called \u003csoc\u003e-\u003cboard\u003e.dts. The binary file\n\t\tis then picked up in board_init_f() and made available through\n\t\tthe global data structure as gd-\u003eblob.\n\n\t\tCONFIG_OF_SEPARATE\n\t\tIf this variable is defined, U-Boot will build a device tree\n\t\tbinary. It will be called u-boot.dtb. Architecture-specific\n\t\tcode will locate it at run-time. Generally this works by:\n\n\t\t\tcat u-boot.bin u-boot.dtb \u003eimage.bin\n\n\t\tand in fact, U-Boot does this for you, creating a file called\n\t\tu-boot-dtb.bin which is useful in the common case. You can\n\t\tstill use the individual files if you need something more\n\t\texotic.\n\n- Watchdog:\n\t\tCONFIG_WATCHDOG\n\t\tIf this variable is defined, it enables watchdog\n\t\tsupport for the SoC. There must be support in the SoC\n\t\tspecific code for a watchdog. For the 8xx and 8260\n\t\tCPUs, the SIU Watchdog feature is enabled in the SYPCR\n\t\tregister.  When supported for a specific SoC is\n\t\tavailable, then no further board specific code should\n\t\tbe needed to use it.\n\n\t\tCONFIG_HW_WATCHDOG\n\t\tWhen using a watchdog circuitry external to the used\n\t\tSoC, then define this variable and provide board\n\t\tspecific code for the \"hw_watchdog_reset\" function.\n\n- U-Boot Version:\n\t\tCONFIG_VERSION_VARIABLE\n\t\tIf this variable is defined, an environment variable\n\t\tnamed \"ver\" is created by U-Boot showing the U-Boot\n\t\tversion as printed by the \"version\" command.\n\t\tAny change to this variable will be reverted at the\n\t\tnext reset.\n\n- Real-Time Clock:\n\n\t\tWhen CONFIG_CMD_DATE is selected, the type of the RTC\n\t\thas to be selected, too. Define exactly one of the\n\t\tfollowing options:\n\n\t\tCONFIG_RTC_MPC8xx\t- use internal RTC of MPC8xx\n\t\tCONFIG_RTC_PCF8563\t- use Philips PCF8563 RTC\n\t\tCONFIG_RTC_MC13XXX\t- use MC13783 or MC13892 RTC\n\t\tCONFIG_RTC_MC146818\t- use MC146818 RTC\n\t\tCONFIG_RTC_DS1307\t- use Maxim, Inc. DS1307 RTC\n\t\tCONFIG_RTC_DS1337\t- use Maxim, Inc. DS1337 RTC\n\t\tCONFIG_RTC_DS1338\t- use Maxim, Inc. DS1338 RTC\n\t\tCONFIG_RTC_DS164x\t- use Dallas DS164x RTC\n\t\tCONFIG_RTC_ISL1208\t- use Intersil ISL1208 RTC\n\t\tCONFIG_RTC_MAX6900\t- use Maxim, Inc. MAX6900 RTC\n\t\tCONFIG_SYS_RTC_DS1337_NOOSC\t- Turn off the OSC output for DS1337\n\t\tCONFIG_SYS_RV3029_TCR\t- enable trickle charger on\n\t\t\t\t\t  RV3029 RTC.\n\n\t\tNote that if the RTC uses I2C, then the I2C interface\n\t\tmust also be configured. See I2C Support, below.\n\n- GPIO Support:\n\t\tCONFIG_PCA953X\t\t- use NXP's PCA953X series I2C GPIO\n\t\tCONFIG_PCA953X_INFO\t- enable pca953x info command\n\n\t\tThe CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of\n\t\tchip-ngpio pairs that tell the PCA953X driver the number of\n\t\tpins supported by a particular chip.\n\n\t\tNote that if the GPIO device uses I2C, then the I2C interface\n\t\tmust also be configured. See I2C Support, below.\n\n- Timestamp Support:\n\n\t\tWhen CONFIG_TIMESTAMP is selected, the timestamp\n\t\t(date and time) of an image is printed by image\n\t\tcommands like bootm or iminfo. This option is\n\t\tautomatically enabled when you select CONFIG_CMD_DATE .\n\n- Partition Labels (disklabels) Supported:\n\t\tZero or more of the following:\n\t\tCONFIG_MAC_PARTITION   Apple's MacOS partition table.\n\t\tCONFIG_DOS_PARTITION   MS Dos partition table, traditional on the\n\t\t\t\t       Intel architecture, USB sticks, etc.\n\t\tCONFIG_ISO_PARTITION   ISO partition table, used on CDROM etc.\n\t\tCONFIG_EFI_PARTITION   GPT partition table, common when EFI is the\n\t\t\t\t       bootloader.  Note 2TB partition limit; see\n\t\t\t\t       disk/part_efi.c\n\t\tCONFIG_MTD_PARTITIONS  Memory Technology Device partition table.\n\n\t\tIf IDE or SCSI support is enabled (CONFIG_CMD_IDE or\n\t\tCONFIG_CMD_SCSI) you must configure support for at\n\t\tleast one non-MTD partition type as well.\n\n- IDE Reset method:\n\t\tCONFIG_IDE_RESET_ROUTINE - this is defined in several\n\t\tboard configurations files but used nowhere!\n\n\t\tCONFIG_IDE_RESET - is this is defined, IDE Reset will\n\t\tbe performed by calling the function\n\t\t\tide_set_reset(int reset)\n\t\twhich has to be defined in a board specific file\n\n- ATAPI Support:\n\t\tCONFIG_ATAPI\n\n\t\tSet this to enable ATAPI support.\n\n- LBA48 Support\n\t\tCONFIG_LBA48\n\n\t\tSet this to enable support for disks larger than 137GB\n\t\tAlso look at CONFIG_SYS_64BIT_LBA.\n\t\tWhithout these , LBA48 support uses 32bit variables and will 'only'\n\t\tsupport disks up to 2.1TB.\n\n\t\tCONFIG_SYS_64BIT_LBA:\n\t\t\tWhen enabled, makes the IDE subsystem use 64bit sector addresses.\n\t\t\tDefault is 32bit.\n\n- SCSI Support:\n\t\tAt the moment only there is only support for the\n\t\tSYM53C8XX SCSI controller; define\n\t\tCONFIG_SCSI_SYM53C8XX to enable it.\n\n\t\tCONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and\n\t\tCONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *\n\t\tCONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the\n\t\tmaximum numbers of LUNs, SCSI ID's and target\n\t\tdevices.\n\t\tCONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)\n\n                The environment variable 'scsidevs' is set to the number of\n                SCSI devices found during the last scan.\n\n- NETWORK Support (PCI):\n\t\tCONFIG_E1000\n\t\tSupport for Intel 8254x/8257x gigabit chips.\n\n\t\tCONFIG_E1000_SPI\n\t\tUtility code for direct access to the SPI bus on Intel 8257x.\n\t\tThis does not do anything useful unless you set at least one\n\t\tof CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC.\n\n\t\tCONFIG_E1000_SPI_GENERIC\n\t\tAllow generic access to the SPI bus on the Intel 8257x, for\n\t\texample with the \"sspi\" command.\n\n\t\tCONFIG_CMD_E1000\n\t\tManagement command for E1000 devices.  When used on devices\n\t\twith SPI support you can reprogram the EEPROM from U-Boot.\n\n\t\tCONFIG_E1000_FALLBACK_MAC\n\t\tdefault MAC for empty EEPROM after production.\n\n\t\tCONFIG_EEPRO100\n\t\tSupport for Intel 82557/82559/82559ER chips.\n\t\tOptional CONFIG_EEPRO100_SROM_WRITE enables EEPROM\n\t\twrite routine for first time initialisation.\n\n\t\tCONFIG_TULIP\n\t\tSupport for Digital 2114x chips.\n\t\tOptional CONFIG_TULIP_SELECT_MEDIA for board specific\n\t\tmodem chip initialisation (KS8761/QS6611).\n\n\t\tCONFIG_NATSEMI\n\t\tSupport for National dp83815 chips.\n\n\t\tCONFIG_NS8382X\n\t\tSupport for National dp8382[01] gigabit chips.\n\n- NETWORK Support (other):\n\n\t\tCONFIG_DRIVER_AT91EMAC\n\t\tSupport for AT91RM9200 EMAC.\n\n\t\t\tCONFIG_RMII\n\t\t\tDefine this to use reduced MII inteface\n\n\t\t\tCONFIG_DRIVER_AT91EMAC_QUIET\n\t\t\tIf this defined, the driver is quiet.\n\t\t\tThe driver doen't show link status messages.\n\n\t\tCONFIG_CALXEDA_XGMAC\n\t\tSupport for the Calxeda XGMAC device\n\n\t\tCONFIG_LAN91C96\n\t\tSupport for SMSC's LAN91C96 chips.\n\n\t\t\tCONFIG_LAN91C96_BASE\n\t\t\tDefine this to hold the physical address\n\t\t\tof the LAN91C96's I/O space\n\n\t\t\tCONFIG_LAN91C96_USE_32_BIT\n\t\t\tDefine this to enable 32 bit addressing\n\n\t\tCONFIG_SMC91111\n\t\tSupport for SMSC's LAN91C111 chip\n\n\t\t\tCONFIG_SMC91111_BASE\n\t\t\tDefine this to hold the physical address\n\t\t\tof the device (I/O space)\n\n\t\t\tCONFIG_SMC_USE_32_BIT\n\t\t\tDefine this if data bus is 32 bits\n\n\t\t\tCONFIG_SMC_USE_IOFUNCS\n\t\t\tDefine this to use i/o functions instead of macros\n\t\t\t(some hardware wont work with macros)\n\n\t\tCONFIG_DRIVER_TI_EMAC\n\t\tSupport for davinci emac\n\n\t\t\tCONFIG_SYS_DAVINCI_EMAC_PHY_COUNT\n\t\t\tDefine this if you have more then 3 PHYs.\n\n\t\tCONFIG_FTGMAC100\n\t\tSupport for Faraday's FTGMAC100 Gigabit SoC Ethernet\n\n\t\t\tCONFIG_FTGMAC100_EGIGA\n\t\t\tDefine this to use GE link update with gigabit PHY.\n\t\t\tDefine this if FTGMAC100 is connected to gigabit PHY.\n\t\t\tIf your system has 10/100 PHY only, it might not occur\n\t\t\twrong behavior. Because PHY usually return timeout or\n\t\t\tuseless data when polling gigabit status and gigabit\n\t\t\tcontrol registers. This behavior won't affect the\n\t\t\tcorrectnessof 10/100 link speed update.\n\n\t\tCONFIG_SMC911X\n\t\tSupport for SMSC's LAN911x and LAN921x chips\n\n\t\t\tCONFIG_SMC911X_BASE\n\t\t\tDefine this to hold the physical address\n\t\t\tof the device (I/O space)\n\n\t\t\tCONFIG_SMC911X_32_BIT\n\t\t\tDefine this if data bus is 32 bits\n\n\t\t\tCONFIG_SMC911X_16_BIT\n\t\t\tDefine this if data bus is 16 bits. If your processor\n\t\t\tautomatically converts one 32 bit word to two 16 bit\n\t\t\twords you may also try CONFIG_SMC911X_32_BIT.\n\n\t\tCONFIG_SH_ETHER\n\t\tSupport for Renesas on-chip Ethernet controller\n\n\t\t\tCONFIG_SH_ETHER_USE_PORT\n\t\t\tDefine the number of ports to be used\n\n\t\t\tCONFIG_SH_ETHER_PHY_ADDR\n\t\t\tDefine the ETH PHY's address\n\n\t\t\tCONFIG_SH_ETHER_CACHE_WRITEBACK\n\t\t\tIf this option is set, the driver enables cache flush.\n\n- TPM Support:\n\t\tCONFIG_TPM\n\t\tSupport TPM devices.\n\n\t\tCONFIG_TPM_TIS_I2C\n\t\tSupport for i2c bus TPM devices. Only one device\n\t\tper system is supported at this time.\n\n\t\t\tCONFIG_TPM_TIS_I2C_BUS_NUMBER\n\t\t\tDefine the the i2c bus number for the TPM device\n\n\t\t\tCONFIG_TPM_TIS_I2C_SLAVE_ADDRESS\n\t\t\tDefine the TPM's address on the i2c bus\n\n\t\t\tCONFIG_TPM_TIS_I2C_BURST_LIMITATION\n\t\t\tDefine the burst count bytes upper limit\n\n\t\tCONFIG_TPM_ATMEL_TWI\n\t\tSupport for Atmel TWI TPM device. Requires I2C support.\n\n\t\tCONFIG_TPM_TIS_LPC\n\t\tSupport for generic parallel port TPM devices. Only one device\n\t\tper system is supported at this time.\n\n\t\t\tCONFIG_TPM_TIS_BASE_ADDRESS\n\t\t\tBase address where the generic TPM device is mapped\n\t\t\tto. Contemporary x86 systems usually map it at\n\t\t\t0xfed40000.\n\n\t\tCONFIG_CMD_TPM\n\t\tAdd tpm monitor functions.\n\t\tRequires CONFIG_TPM. If CONFIG_TPM_AUTH_SESSIONS is set, also\n\t\tprovides monitor access to authorized functions.\n\n\t\tCONFIG_TPM\n\t\tDefine this to enable the TPM support library which provides\n\t\tfunctional interfaces to some TPM commands.\n\t\tRequires support for a TPM device.\n\n\t\tCONFIG_TPM_AUTH_SESSIONS\n\t\tDefine this to enable authorized functions in the TPM library.\n\t\tRequires CONFIG_TPM and CONFIG_SHA1.\n\n- USB Support:\n\t\tAt the moment only the UHCI host controller is\n\t\tsupported (PIP405, MIP405, MPC5200); define\n\t\tCONFIG_USB_UHCI to enable it.\n\t\tdefine CONFIG_USB_KEYBOARD to enable the USB Keyboard\n\t\tand define CONFIG_USB_STORAGE to enable the USB\n\t\tstorage devices.\n\t\tNote:\n\t\tSupported are USB Keyboards and USB Floppy drives\n\t\t(TEAC FD-05PUB).\n\t\tMPC5200 USB requires additional defines:\n\t\t\tCONFIG_USB_CLOCK\n\t\t\t\tfor 528 MHz Clock: 0x0001bbbb\n\t\t\tCONFIG_PSC3_USB\n\t\t\t\tfor USB on PSC3\n\t\t\tCONFIG_USB_CONFIG\n\t\t\t\tfor differential drivers: 0x00001000\n\t\t\t\tfor single ended drivers: 0x00005000\n\t\t\t\tfor differential drivers on PSC3: 0x00000100\n\t\t\t\tfor single ended drivers on PSC3: 0x00004100\n\t\t\tCONFIG_SYS_USB_EVENT_POLL\n\t\t\t\tMay be defined to allow interrupt polling\n\t\t\t\tinstead of using asynchronous interrupts\n\n\t\tCONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the\n\t\ttxfilltuning field in the EHCI controller on reset.\n\n\t\tCONFIG_USB_HUB_MIN_POWER_ON_DELAY defines the minimum\n\t\tinterval for usb hub power-on delay.(minimum 100msec)\n\n- USB Device:\n\t\tDefine the below if you wish to use the USB console.\n\t\tOnce firmware is rebuilt from a serial console issue the\n\t\tcommand \"setenv stdin usbtty; setenv stdout usbtty\" and\n\t\tattach your USB cable. The Unix command \"dmesg\" should print\n\t\tit has found a new device. The environment variable usbtty\n\t\tcan be set to gserial or cdc_acm to enable your device to\n\t\tappear to a USB host as a Linux gserial device or a\n\t\tCommon Device Class Abstract Control Model serial device.\n\t\tIf you select usbtty = gserial you should be able to enumerate\n\t\ta Linux host by\n\t\t# modprobe usbserial vendor=0xVendorID product=0xProductID\n\t\telse if using cdc_acm, simply setting the environment\n\t\tvariable usbtty to be cdc_acm should suffice. The following\n\t\tmight be defined in YourBoardName.h\n\n\t\t\tCONFIG_USB_DEVICE\n\t\t\tDefine this to build a UDC device\n\n\t\t\tCONFIG_USB_TTY\n\t\t\tDefine this to have a tty type of device available to\n\t\t\ttalk to the UDC device\n\n\t\t\tCONFIG_USBD_HS\n\t\t\tDefine this to enable the high speed support for usb\n\t\t\tdevice and usbtty. If this feature is enabled, a routine\n\t\t\tint is_usbd_high_speed(void)\n\t\t\talso needs to be defined by the driver to dynamically poll\n\t\t\twhether the enumeration has succeded at high speed or full\n\t\t\tspeed.\n\n\t\t\tCONFIG_SYS_CONSOLE_IS_IN_ENV\n\t\t\tDefine this if you want stdin, stdout \u0026/or stderr to\n\t\t\tbe set to usbtty.\n\n\t\t\tmpc8xx:\n\t\t\t\tCONFIG_SYS_USB_EXTC_CLK 0xBLAH\n\t\t\t\tDerive USB clock from external clock \"blah\"\n\t\t\t\t- CONFIG_SYS_USB_EXTC_CLK 0x02\n\n\t\t\t\tCONFIG_SYS_USB_BRG_CLK 0xBLAH\n\t\t\t\tDerive USB clock from brgclk\n\t\t\t\t- CONFIG_SYS_USB_BRG_CLK 0x04\n\n\t\tIf you have a USB-IF assigned VendorID then you may wish to\n\t\tdefine your own vendor specific values either in BoardName.h\n\t\tor directly in usbd_vendor_info.h. If you don't define\n\t\tCONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,\n\t\tCONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot\n\t\tshould pretend to be a Linux device to it's target host.\n\n\t\t\tCONFIG_USBD_MANUFACTURER\n\t\t\tDefine this string as the name of your company for\n\t\t\t- CONFIG_USBD_MANUFACTURER \"my company\"\n\n\t\t\tCONFIG_USBD_PRODUCT_NAME\n\t\t\tDefine this string as the name of your product\n\t\t\t- CONFIG_USBD_PRODUCT_NAME \"acme usb device\"\n\n\t\t\tCONFIG_USBD_VENDORID\n\t\t\tDefine this as your assigned Vendor ID from the USB\n\t\t\tImplementors Forum. This *must* be a genuine Vendor ID\n\t\t\tto avoid polluting the USB namespace.\n\t\t\t- CONFIG_USBD_VENDORID 0xFFFF\n\n\t\t\tCONFIG_USBD_PRODUCTID\n\t\t\tDefine this as the unique Product ID\n\t\t\tfor your device\n\t\t\t- CONFIG_USBD_PRODUCTID 0xFFFF\n\n- ULPI Layer Support:\n\t\tThe ULPI (UTMI Low Pin (count) Interface) PHYs are supported via\n\t\tthe generic ULPI layer. The generic layer accesses the ULPI PHY\n\t\tvia the platform viewport, so you need both the genric layer and\n\t\tthe viewport enabled. Currently only Chipidea/ARC based\n\t\tviewport is supported.\n\t\tTo enable the ULPI layer support, define CONFIG_USB_ULPI and\n\t\tCONFIG_USB_ULPI_VIEWPORT in your board configuration file.\n\t\tIf your ULPI phy needs a different reference clock than the\n\t\tstandard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to\n\t\tthe appropriate value in Hz.\n\n- MMC Support:\n\t\tThe MMC controller on the Intel PXA is supported. To\n\t\tenable this define CONFIG_MMC. The MMC can be\n\t\taccessed from the boot prompt by mapping the device\n\t\tto physical memory similar to flash. Command line is\n\t\tenabled with CONFIG_CMD_MMC. The MMC driver also works with\n\t\tthe FAT fs. This is enabled with CONFIG_CMD_FAT.\n\n\t\tCONFIG_SH_MMCIF\n\t\tSupport for Renesas on-chip MMCIF controller\n\n\t\t\tCONFIG_SH_MMCIF_ADDR\n\t\t\tDefine the base address of MMCIF registers\n\n\t\t\tCONFIG_SH_MMCIF_CLK\n\t\t\tDefine the clock frequency for MMCIF\n\n- USB Device Firmware Update (DFU) class support:\n\t\tCONFIG_DFU_FUNCTION\n\t\tThis enables the USB portion of the DFU USB class\n\n\t\tCONFIG_CMD_DFU\n\t\tThis enables the command \"dfu\" which is used to have\n\t\tU-Boot create a DFU class device via USB.  This command\n\t\trequires that the \"dfu_alt_info\" environment variable be\n\t\tset and define the alt settings to expose to the host.\n\n\t\tCONFIG_DFU_MMC\n\t\tThis enables support for exposing (e)MMC devices via DFU.\n\n\t\tCONFIG_DFU_NAND\n\t\tThis enables support for exposing NAND devices via DFU.\n\n\t\tCONFIG_SYS_DFU_DATA_BUF_SIZE\n\t\tDfu transfer uses a buffer before writing data to the\n\t\traw storage device. Make the size (in bytes) of this buffer\n\t\tconfigurable. The size of this buffer is also configurable\n\t\tthrough the \"dfu_bufsiz\" environment variable.\n\n\t\tCONFIG_SYS_DFU_MAX_FILE_SIZE\n\t\tWhen updating files rather than the raw storage device,\n\t\twe use a static buffer to copy the file into and then write\n\t\tthe buffer once we've been given the whole file.  Define\n\t\tthis to the maximum filesize (in bytes) for the buffer.\n\t\tDefault is 4 MiB if undefined.\n\n- Journaling Flash filesystem support:\n\t\tCONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,\n\t\tCONFIG_JFFS2_NAND_DEV\n\t\tDefine these for a default partition on a NAND device\n\n\t\tCONFIG_SYS_JFFS2_FIRST_SECTOR,\n\t\tCONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS\n\t\tDefine these for a default partition on a NOR device\n\n\t\tCONFIG_SYS_JFFS_CUSTOM_PART\n\t\tDefine this to create an own partition. You have to provide a\n\t\tfunction struct part_info* jffs2_part_info(int part_num)\n\n\t\tIf you define only one JFFS2 partition you may also want to\n\t\t#define CONFIG_SYS_JFFS_SINGLE_PART\t1\n\t\tto disable the command chpart. This is the default when you\n\t\thave not defined a custom partition\n\n- FAT(File Allocation Table) filesystem write function support:\n\t\tCONFIG_FAT_WRITE\n\n\t\tDefine this to enable support for saving memory data as a\n\t\tfile in FAT formatted partition.\n\n\t\tThis will also enable the command \"fatwrite\" enabling the\n\t\tuser to write files to FAT.\n\nCBFS (Coreboot Filesystem) support\n\t\tCONFIG_CMD_CBFS\n\n\t\tDefine this to enable support for reading from a Coreboot\n\t\tfilesystem. Available commands are cbfsinit, cbfsinfo, cbfsls\n\t\tand cbfsload.\n\n- Keyboard Support:\n\t\tCONFIG_ISA_KEYBOARD\n\n\t\tDefine this to enable standard (PC-Style) keyboard\n\t\tsupport\n\n\t\tCONFIG_I8042_KBD\n\t\tStandard PC keyboard driver with US (is default) and\n\t\tGERMAN key layout (switch via environment 'keymap=de') support.\n\t\tExport function i8042_kbd_init, i8042_tstc and i8042_getc\n\t\tfor cfb_console. Supports cursor blinking.\n\n\t\tCONFIG_CROS_EC_KEYB\n\t\tEnables a Chrome OS keyboard using the CROS_EC interface.\n\t\tThis uses CROS_EC to communicate with a second microcontroller\n\t\twhich provides key scans on request.\n\n- Video support:\n\t\tCONFIG_VIDEO\n\n\t\tDefine this to enable video support (for output to\n\t\tvideo).\n\n\t\tCONFIG_VIDEO_CT69000\n\n\t\tEnable Chips \u0026 Technologies 69000 Video chip\n\n\t\tCONFIG_VIDEO_SMI_LYNXEM\n\t\tEnable Silicon Motion SMI 712/710/810 Video chip. The\n\t\tvideo output is selected via environment 'videoout'\n\t\t(1 = LCD and 2 = CRT). If videoout is undefined, CRT is\n\t\tassumed.\n\n\t\tFor the CT69000 and SMI_LYNXEM drivers, videomode is\n\t\tselected via environment 'videomode'. Two different ways\n\t\tare possible:\n\t\t- \"videomode=num\"   'num' is a standard LiLo mode numbers.\n\t\tFollowing standard modes are supported\t(* is default):\n\n\t\t      Colors\t640x480 800x600 1024x768 1152x864 1280x1024\n\t\t-------------+---------------------------------------------\n\t\t      8 bits |\t0x301*\t0x303\t 0x305\t  0x161\t    0x307\n\t\t     15 bits |\t0x310\t0x313\t 0x316\t  0x162\t    0x319\n\t\t     16 bits |\t0x311\t0x314\t 0x317\t  0x163\t    0x31A\n\t\t     24 bits |\t0x312\t0x315\t 0x318\t    ?\t    0x31B\n\t\t-------------+---------------------------------------------\n\t\t(i.e. setenv videomode 317; saveenv; reset;)\n\n\t\t- \"videomode=bootargs\" all the video parameters are parsed\n\t\tfrom the bootargs. (See drivers/video/videomodes.c)\n\n\n\t\tCONFIG_VIDEO_SED13806\n\t\tEnable Epson SED13806 driver. This driver supports 8bpp\n\t\tand 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP\n\t\tor CONFIG_VIDEO_SED13806_16BPP\n\n\t\tCONFIG_FSL_DIU_FB\n\t\tEnable the Freescale DIU video driver.\tReference boards for\n\t\tSOCs that have a DIU should define this macro to enable DIU\n\t\tsupport, and should also define these other macros:\n\n\t\t\tCONFIG_SYS_DIU_ADDR\n\t\t\tCONFIG_VIDEO\n\t\t\tCONFIG_CMD_BMP\n\t\t\tCONFIG_CFB_CONSOLE\n\t\t\tCONFIG_VIDEO_SW_CURSOR\n\t\t\tCONFIG_VGA_AS_SINGLE_DEVICE\n\t\t\tCONFIG_VIDEO_LOGO\n\t\t\tCONFIG_VIDEO_BMP_LOGO\n\n\t\tThe DIU driver will look for the 'video-mode' environment\n\t\tvariable, and if defined, enable the DIU as a console during\n\t\tboot.  See the documentation file README.video for a\n\t\tdescription of this variable.\n\n\t\tCONFIG_VIDEO_VGA\n\n\t\tEnable the VGA video / BIOS for x86. The alternative if you\n\t\tare using coreboot is to use the coreboot frame buffer\n\t\tdriver.\n\n\n- Keyboard Support:\n\t\tCONFIG_KEYBOARD\n\n\t\tDefine this to enable a custom keyboard support.\n\t\tThis simply calls drv_keyboard_init() which must be\n\t\tdefined in your board-specific files.\n\t\tThe only board using this so far is RBC823.\n\n- LCD Support:\tCONFIG_LCD\n\n\t\tDefine this to enable LCD support (for output to LCD\n\t\tdisplay); also select one of the supported displays\n\t\tby defining one of these:\n\n\t\tCONFIG_ATMEL_LCD:\n\n\t\t\tHITACHI TX09D70VM1CCA, 3.5\", 240x320.\n\n\t\tCONFIG_NEC_NL6448AC33:\n\n\t\t\tNEC NL6448AC33-18. Active, color, single scan.\n\n\t\tCONFIG_NEC_NL6448BC20\n\n\t\t\tNEC NL6448BC20-08. 6.5\", 640x480.\n\t\t\tActive, color, single scan.\n\n\t\tCONFIG_NEC_NL6448BC33_54\n\n\t\t\tNEC NL6448BC33-54. 10.4\", 640x480.\n\t\t\tActive, color, single scan.\n\n\t\tCONFIG_SHARP_16x9\n\n\t\t\tSharp 320x240. Active, color, single scan.\n\t\t\tIt isn't 16x9, and I am not sure what it is.\n\n\t\tCONFIG_SHARP_LQ64D341\n\n\t\t\tSharp LQ64D341 display, 640x480.\n\t\t\tActive, color, single scan.\n\n\t\tCONFIG_HLD1045\n\n\t\t\tHLD1045 display, 640x480.\n\t\t\tActive, color, single scan.\n\n\t\tCONFIG_OPTREX_BW\n\n\t\t\tOptrex\t CBL50840-2 NF-FW 99 22 M5\n\t\t\tor\n\t\t\tHitachi\t LMG6912RPFC-00T\n\t\t\tor\n\t\t\tHitachi\t SP14Q002\n\n\t\t\t320x240. Black \u0026 white.\n\n\t\tNormally display is black on white background; define\n\t\tCONFIG_SYS_WHITE_ON_BLACK to get it inverted.\n\n\t\tCONFIG_LCD_ALIGNMENT\n\n\t\tNormally the LCD is page-aligned (tyically 4KB). If this is\n\t\tdefined then the LCD will be aligned to this value instead.\n\t\tFor ARM it is sometimes useful to use MMU_SECTION_SIZE\n\t\there, since it is cheaper to change data cache settings on\n\t\ta per-section basis.\n\n\t\tCONFIG_CONSOLE_SCROLL_LINES\n\n\t\tWhen the console need to be scrolled, this is the number of\n\t\tlines to scroll by. It defaults to 1. Increasing this makes\n\t\tthe console jump but can help speed up operation when scrolling\n\t\tis slow.\n\n\t\tCONFIG_LCD_BMP_RLE8\n\n\t\tSupport drawing of RLE8-compressed bitmaps on the LCD.\n\n\t\tCONFIG_I2C_EDID\n\n\t\tEnables an 'i2c edid' command which can read EDID\n\t\tinformation over I2C from an attached LCD display.\n\n- Splash Screen Support: CONFIG_SPLASH_SCREEN\n\n\t\tIf this option is set, the environment is checked for\n\t\ta variable \"splashimage\". If found, the usual display\n\t\tof logo, copyright and system information on the LCD\n\t\tis suppressed and the BMP image at the address\n\t\tspecified in \"splashimage\" is loaded instead. The\n\t\tconsole is redirected to the \"nulldev\", too. This\n\t\tallows for a \"silent\" boot where a splash screen is\n\t\tloaded very quickly after power-on.\n\n\t\tCONFIG_SPLASHIMAGE_GUARD\n\n\t\tIf this option is set, then U-Boot will prevent the environment\n\t\tvariable \"splashimage\" from being set to a problematic address\n\t\t(see README.displaying-bmps and README.arm-unaligned-accesses).\n\t\tThis option is useful for targets where, due to alignment\n\t\trestrictions, an improperly aligned BMP image will cause a data\n\t\tabort. If you think you will not have problems with unaligned\n\t\taccesses (for example because your toolchain prevents them)\n\t\tthere is no need to set this option.\n\n\t\tCONFIG_SPLASH_SCREEN_ALIGN\n\n\t\tIf this option is set the splash image can be freely positioned\n\t\ton the screen. Environment variable \"splashpos\" specifies the\n\t\tposition as \"x,y\". If a positive number is given it is used as\n\t\tnumber of pixel from left/top. If a negative number is given it\n\t\tis used as number of pixel from right/bottom. You can also\n\t\tspecify 'm' for centering the image.\n\n\t\tExample:\n\t\tsetenv splashpos m,m\n\t\t\t=\u003e image at center of screen\n\n\t\tsetenv splashpos 30,20\n\t\t\t=\u003e image at x = 30 and y = 20\n\n\t\tsetenv splashpos -10,m\n\t\t\t=\u003e vertically centered image\n\t\t\t   at x = dspWidth - bmpWidth - 9\n\n- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP\n\n\t\tIf this option is set, additionally to standard BMP\n\t\timages, gzipped BMP images can be displayed via the\n\t\tsplashscreen support or the bmp command.\n\n- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8\n\n\t\tIf this option is set, 8-bit RLE compressed BMP images\n\t\tcan be displayed via the splashscreen support or the\n\t\tbmp command.\n\n- Do compresssing for memory range:\n\t\tCONFIG_CMD_ZIP\n\n\t\tIf this option is set, it would use zlib deflate method\n\t\tto compress the specified memory at its best effort.\n\n- Compression support:\n\t\tCONFIG_BZIP2\n\n\t\tIf this option is set, support for bzip2 compressed\n\t\timages is included. If not, only uncompressed and gzip\n\t\tcompressed images are supported.\n\n\t\tNOTE: the bzip2 algorithm requires a lot of RAM, so\n\t\tthe malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should\n\t\tbe at least 4MB.\n\n\t\tCONFIG_LZMA\n\n\t\tIf this option is set, support for lzma compressed\n\t\timages is included.\n\n\t\tNote: The LZMA algorithm adds between 2 and 4KB of code and it\n\t\trequires an amount of dynamic memory that is given by the\n\t\tformula:\n\n\t\t\t(1846 + 768 \u003c\u003c (lc + lp)) * sizeof(uint16)\n\n\t\tWhere lc and lp stand for, respectively, Literal context bits\n\t\tand Literal pos bits.\n\n\t\tThis value is upper-bounded by 14MB in the worst case. Anyway,\n\t\tfor a ~4MB large kernel image, we have lc=3 and lp=0 for a\n\t\ttotal amount of (1846 + 768 \u003c\u003c (3 + 0)) * 2 = ~41KB... that is\n\t\ta very small buffer.\n\n\t\tUse the lzmainfo tool to determinate the lc and lp values and\n\t\tthen calculate the amount of needed dynamic memory (ensuring\n\t\tthe appropriate CONFIG_SYS_MALLOC_LEN value).\n\n- MII/PHY support:\n\t\tCONFIG_PHY_ADDR\n\n\t\tThe address of PHY on MII bus.\n\n\t\tCONFIG_PHY_CLOCK_FREQ (ppc4xx)\n\n\t\tThe clock frequency of the MII bus\n\n\t\tCONFIG_PHY_GIGE\n\n\t\tIf this option is set, support for speed/duplex\n\t\tdetection of gigabit PHY is included.\n\n\t\tCONFIG_PHY_RESET_DELAY\n\n\t\tSome PHY like Intel LXT971A need extra delay after\n\t\treset before any MII register access is possible.\n\t\tFor such PHY, set this option to the usec delay\n\t\trequired. (minimum 300usec for LXT971A)\n\n\t\tCONFIG_PHY_CMD_DELAY (ppc4xx)\n\n\t\tSome PHY like Intel LXT971A need extra delay after\n\t\tcommand issued before MII status register can be read\n\n- Ethernet address:\n\t\tCONFIG_ETHADDR\n\t\tCONFIG_ETH1ADDR\n\t\tCONFIG_ETH2ADDR\n\t\tCONFIG_ETH3ADDR\n\t\tCONFIG_ETH4ADDR\n\t\tCONFIG_ETH5ADDR\n\n\t\tDefine a default value for Ethernet address to use\n\t\tfor the respective Ethernet interface, in case this\n\t\tis not determined automatically.\n\n- IP address:\n\t\tCONFIG_IPADDR\n\n\t\tDefine a default value for the IP address to use for\n\t\tthe default Ethernet interface, in case this is not\n\t\tdetermined through e.g. bootp.\n\t\t(Environment variable \"ipaddr\")\n\n- Server IP address:\n\t\tCONFIG_SERVERIP\n\n\t\tDefines a default value for the IP address of a TFTP\n\t\tserver to contact when using the \"tftboot\" command.\n\t\t(Environment variable \"serverip\")\n\n\t\tCONFIG_KEEP_SERVERADDR\n\n\t\tKeeps the server's MAC address, in the env 'serveraddr'\n\t\tfor passing to bootargs (like Linux's netconsole option)\n\n- Gateway IP address:\n\t\tCONFIG_GATEWAYIP\n\n\t\tDefines a default value for the IP address of the\n\t\tdefault router where packets to other networks are\n\t\tsent to.\n\t\t(Environment variable \"gatewayip\")\n\n- Subnet mask:\n\t\tCONFIG_NETMASK\n\n\t\tDefines a default value for the subnet mask (or\n\t\trouting prefix) which is used to determine if an IP\n\t\taddress belongs to the local subnet or needs to be\n\t\tforwarded through a router.\n\t\t(Environment variable \"netmask\")\n\n- Multicast TFTP Mode:\n\t\tCONFIG_MCAST_TFTP\n\n\t\tDefines whether you want to support multicast TFTP as per\n\t\trfc-2090; for example to work with atftp.  Lets lots of targets\n\t\ttftp down the same boot image concurrently.  Note: the Ethernet\n\t\tdriver in use must provide a function: mcast() to join/leave a\n\t\tmulticast group.\n\n- BOOTP Recovery Mode:\n\t\tCONFIG_BOOTP_RANDOM_DELAY\n\n\t\tIf you have many targets in a network that try to\n\t\tboot using BOOTP, you may want to avoid that all\n\t\tsystems send out BOOTP requests at precisely the same\n\t\tmoment (which would happen for instance at recovery\n\t\tfrom a power failure, when all systems will try to\n\t\tboot, thus flooding the BOOTP server. Defining\n\t\tCONFIG_BOOTP_RANDOM_DELAY causes a random delay to be\n\t\tinserted before sending out BOOTP requests. The\n\t\tfollowing delays are inserted then:\n\n\t\t1st BOOTP request:\tdelay 0 ... 1 sec\n\t\t2nd BOOTP request:\tdelay 0 ... 2 sec\n\t\t3rd BOOTP request:\tdelay 0 ... 4 sec\n\t\t4th and following\n\t\tBOOTP requests:\t\tdelay 0 ... 8 sec\n\n- DHCP Advanced Options:\n\t\tYou can fine tune the DHCP functionality by defining\n\t\tCONFIG_BOOTP_* symbols:\n\n\t\tCONFIG_BOOTP_SUBNETMASK\n\t\tCONFIG_BOOTP_GATEWAY\n\t\tCONFIG_BOOTP_HOSTNAME\n\t\tCONFIG_BOOTP_NISDOMAIN\n\t\tCONFIG_BOOTP_BOOTPATH\n\t\tCONFIG_BOOTP_BOOTFILESIZE\n\t\tCONFIG_BOOTP_DNS\n\t\tCONFIG_BOOTP_DNS2\n\t\tCONFIG_BOOTP_SEND_HOSTNAME\n\t\tCONFIG_BOOTP_NTPSERVER\n\t\tCONFIG_BOOTP_TIMEOFFSET\n\t\tCONFIG_BOOTP_VENDOREX\n\t\tCONFIG_BOOTP_MAY_FAIL\n\n\t\tCONFIG_BOOTP_SERVERIP - TFTP server will be the serverip\n\t\tenvironment variable, not the BOOTP server.\n\n\t\tCONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found\n\t\tafter the configured retry count, the call will fail\n\t\tinstead of starting over.  This can be used to fail over\n\t\tto Link-local IP address configuration if the DHCP server\n\t\tis not available.\n\n\t\tCONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS\n\t\tserverip from a DHCP server, it is possible that more\n\t\tthan one DNS serverip is offered to the client.\n\t\tIf CONFIG_BOOTP_DNS2 is enabled, the secondary DNS\n\t\tserverip will be stored in the additional environment\n\t\tvariable \"dnsip2\". The first DNS serverip is always\n\t\tstored in the variable \"dnsip\", when CONFIG_BOOTP_DNS\n\t\tis defined.\n\n\t\tCONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable\n\t\tto do a dynamic update of a DNS server. To do this, they\n\t\tneed the hostname of the DHCP requester.\n\t\tIf CONFIG_BOOTP_SEND_HOSTNAME is defined, the content\n\t\tof the \"hostname\" environment variable is passed as\n\t\toption 12 to the DHCP server.\n\n\t\tCONFIG_BOOTP_DHCP_REQUEST_DELAY\n\n\t\tA 32bit value in microseconds for a delay between\n\t\treceiving a \"DHCP Offer\" and sending the \"DHCP Request\".\n\t\tThis fixes a problem with certain DHCP servers that don't\n\t\trespond 100% of the time to a \"DHCP request\". E.g. On an\n\t\tAT91RM9200 processor running at 180MHz, this delay needed\n\t\tto be *at least* 15,000 usec before a Windows Server 2003\n\t\tDHCP server would reply 100% of the time. I recommend at\n\t\tleast 50,000 usec to be safe. The alternative is to hope\n\t\tthat one of the retries will be successful but note that\n\t\tthe DHCP timeout and retry process takes a longer than\n\t\tthis delay.\n\n - Link-local IP address negotiation:\n\t\tNegotiate with other link-local clients on the local network\n\t\tfor an address that doesn't require explicit configuration.\n\t\tThis is especially useful if a DHCP server cannot be guaranteed\n\t\tto exist in all environments that the device must operate.\n\n\t\tSee doc/README.link-local for more information.\n\n - CDP Options:\n\t\tCONFIG_CDP_DEVICE_ID\n\n\t\tThe device id used in CDP trigger frames.\n\n\t\tCONFIG_CDP_DEVICE_ID_PREFIX\n\n\t\tA two character string which is prefixed to the MAC address\n\t\tof the device.\n\n\t\tCONFIG_CDP_PORT_ID\n\n\t\tA printf format string which contains the ascii name of\n\t\tthe port. Normally is set to \"eth%d\" which sets\n\t\teth0 for the first Ethernet, eth1 for the second etc.\n\n\t\tCONFIG_CDP_CAPABILITIES\n\n\t\tA 32bit integer which indicates the device capabilities;\n\t\t0x00000010 for a normal host which does not forwards.\n\n\t\tCONFIG_CDP_VERSION\n\n\t\tAn ascii string containing the version of the software.\n\n\t\tCONFIG_CDP_PLATFORM\n\n\t\tAn ascii string containing the name of the platform.\n\n\t\tCONFIG_CDP_TRIGGER\n\n\t\tA 32bit integer sent on the trigger.\n\n\t\tCONFIG_CDP_POWER_CONSUMPTION\n\n\t\tA 16bit integer containing the power consumption of the\n\t\tdevice in .1 of milliwatts.\n\n\t\tCONFIG_CDP_APPLIANCE_VLAN_TYPE\n\n\t\tA byte containing the id of the VLAN.\n\n- Status LED:\tCONFIG_STATUS_LED\n\n\t\tSeveral configurations allow to display the current\n\t\tstatus using a LED. For instance, the LED will blink\n\t\tfast while running U-Boot code, stop blinking as\n\t\tsoon as a reply to a BOOTP request was received, and\n\t\tstart blinking slow once the Linux kernel is running\n\t\t(supported by a status LED driver in the Linux\n\t\tkernel). Defining CONFIG_STATUS_LED enables this\n\t\tfeature in U-Boot.\n\n- CAN Support:\tCONFIG_CAN_DRIVER\n\n\t\tDefining CONFIG_CAN_DRIVER enables CAN driver support\n\t\ton those systems that support this (optional)\n\t\tfeature, like the TQM8xxL modules.\n\n- I2C Support:\tCONFIG_HARD_I2C | CONFIG_SOFT_I2C\n\n\t\tThese enable I2C serial bus commands. Defining either of\n\t\t(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will\n\t\tinclude the appropriate I2C driver for the selected CPU.\n\n\t\tThis will allow you to use i2c commands at the u-boot\n\t\tcommand line (as long as you set CONFIG_CMD_I2C in\n\t\tCONFIG_COMMANDS) and communicate with i2c based realtime\n\t\tclock chips. See common/cmd_i2c.c for a description of the\n\t\tcommand line interface.\n\n\t\tCONFIG_HARD_I2C selects a hardware I2C controller.\n\n\t\tCONFIG_SOFT_I2C configures u-boot to use a software (aka\n\t\tbit-banging) driver instead of CPM or similar hardware\n\t\tsupport for I2C.\n\n\t\tThere are several other quantities that must also be\n\t\tdefined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.\n\n\t\tIn both cases you will need to define CONFIG_SYS_I2C_SPEED\n\t\tto be the frequency (in Hz) at which you wish your i2c bus\n\t\tto run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie\n\t\tthe CPU's i2c node address).\n\n\t\tNow, the u-boot i2c code for the mpc8xx\n\t\t(arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node\n\t\tand so its address should therefore be cleared to 0 (See,\n\t\teg, MPC823e User's Manual p.16-473). So, set\n\t\tCONFIG_SYS_I2C_SLAVE to 0.\n\n\t\tCONFIG_SYS_I2C_INIT_MPC5XXX\n\n\t\tWhen a board is reset during an i2c bus transfer\n\t\tchips might think that the current transfer is still\n\t\tin progress.  Reset the slave devices by sending start\n\t\tcommands until the slave device responds.\n\n\t\tThat's all that's required for CONFIG_HARD_I2C.\n\n\t\tIf you use the software i2c interface (CONFIG_SOFT_I2C)\n\t\tthen the following macros need to be defined (examples are\n\t\tfrom include/configs/lwmon.h):\n\n\t\tI2C_INIT\n\n\t\t(Optional). Any commands necessary to enable the I2C\n\t\tcontroller or configure ports.\n\n\t\teg: #define I2C_INIT (immr-\u003eim_cpm.cp_pbdir |=\tPB_SCL)\n\n\t\tI2C_PORT\n\n\t\t(Only for MPC8260 CPU). The I/O port to use (the code\n\t\tassumes both bits are on the same port). Valid values\n\t\tare 0..3 for ports A..D.\n\n\t\tI2C_ACTIVE\n\n\t\tThe code necessary to make the I2C data line active\n\t\t(driven).  If the data line is open collector, this\n\t\tdefine can be null.\n\n\t\teg: #define I2C_ACTIVE (immr-\u003eim_cpm.cp_pbdir |=  PB_SDA)\n\n\t\tI2C_TRISTATE\n\n\t\tThe code necessary to make the I2C data line tri-stated\n\t\t(inactive).  If the data line is open collector, this\n\t\tdefine can be null.\n\n\t\teg: #define I2C_TRISTATE (immr-\u003eim_cpm.cp_pbdir \u0026= ~PB_SDA)\n\n\t\tI2C_READ\n\n\t\tCode that returns true if the I2C data line is high,\n\t\tfalse if it is low.\n\n\t\teg: #define I2C_READ ((immr-\u003eim_cpm.cp_pbdat \u0026 PB_SDA) != 0)\n\n\t\tI2C_SDA(bit)\n\n\t\tIf \u003cbit\u003e is true, sets the I2C data line high. If it\n\t\tis false, it clears it (low).\n\n\t\teg: #define I2C_SDA(bit) \\\n\t\t\tif(bit) immr-\u003eim_cpm.cp_pbdat |=  PB_SDA; \\\n\t\t\telse\timmr-\u003eim_cpm.cp_pbdat \u0026= ~PB_SDA\n\n\t\tI2C_SCL(bit)\n\n\t\tIf \u003cbit\u003e is true, sets the I2C clock line high. If it\n\t\tis false, it clears it (low).\n\n\t\teg: #define I2C_SCL(bit) \\\n\t\t\tif(bit) immr-\u003eim_cpm.cp_pbdat |=  PB_SCL; \\\n\t\t\telse\timmr-\u003eim_cpm.cp_pbdat \u0026= ~PB_SCL\n\n\t\tI2C_DELAY\n\n\t\tThis delay is invoked four times per clock cycle so this\n\t\tcontrols the rate of data transfer.  The data rate thus\n\t\tis 1 / (I2C_DELAY * 4). Often defined to be something\n\t\tlike:\n\n\t\t#define I2C_DELAY  udelay(2)\n\n\t\tCONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA\n\n\t\tIf your arch supports the generic GPIO framework (asm/gpio.h),\n\t\tthen you may alternatively define the two GPIOs that are to be\n\t\tused as SCL / SDA.  Any of the previous I2C_xxx macros will\n\t\thave GPIO-based defaults assigned to them as appropriate.\n\n\t\tYou should define these to the GPIO value as given directly to\n\t\tthe generic GPIO functions.\n\n\t\tCONFIG_SYS_I2C_INIT_BOARD\n\n\t\tWhen a board is reset during an i2c bus transfer\n\t\tchips might think that the current transfer is still\n\t\tin progress. On some boards it is possible to access\n\t\tthe i2c SCLK line directly, either by using the\n\t\tprocessor pin as a GPIO or by having a second pin\n\t\tconnected to the bus. If this option is defined a\n\t\tcustom i2c_init_board() routine in boards/xxx/board.c\n\t\tis run early in the boot sequence.\n\n\t\tCONFIG_SYS_I2C_BOARD_LATE_INIT\n\n\t\tAn alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is\n\t\tdefined a custom i2c_board_late_init() routine in\n\t\tboards/xxx/board.c is run AFTER the operations in i2c_init()\n\t\tis completed. This callpoint can be used to unreset i2c bus\n\t\tusing CPU i2c controller register accesses for CPUs whose i2c\n\t\tcontroller provide such a method. It is called at the end of\n\t\ti2c_init() to allow i2c_init operations to setup the i2c bus\n\t\tcontroller on the CPU (e.g. setting bus speed \u0026 slave address).\n\n\t\tCONFIG_I2CFAST (PPC405GP|PPC405EP only)\n\n\t\tThis option enables configuration of bi_iic_fast[] flags\n\t\tin u-boot bd_info structure based on u-boot environment\n\t\tvariable \"i2cfast\". (see also i2cfast)\n\n\t\tCONFIG_I2C_MULTI_BUS\n\n\t\tThis option allows the use of multiple I2C buses, each of which\n\t\tmust have a controller.\t At any point in time, only one bus is\n\t\tactive.\t To switch to a different bus, use the 'i2c dev' command.\n\t\tNote that bus numbering is zero-based.\n\n\t\tCONFIG_SYS_I2C_NOPROBES\n\n\t\tThis option specifies a list of I2C devices that will be skipped\n\t\twhen the 'i2c probe' command is issued.\t If CONFIG_I2C_MULTI_BUS\n\t\tis set, specify a list of bus-device pairs.  Otherwise, specify\n\t\ta 1D array of device addresses\n\n\t\te.g.\n\t\t\t#undef\tCONFIG_I2C_MULTI_BUS\n\t\t\t#define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}\n\n\t\twill skip addresses 0x50 and 0x68 on a board with one I2C bus\n\n\t\t\t#define CONFIG_I2C_MULTI_BUS\n\t\t\t#define CONFIG_SYS_I2C_MULTI_NOPROBES\t{{0,0x50},{0,0x68},{1,0x54}}\n\n\t\twill skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1\n\n\t\tCONFIG_SYS_SPD_BUS_NUM\n\n\t\tIf defined, then this indicates the I2C bus number for DDR SPD.\n\t\tIf not defined, then U-Boot assumes that SPD is on I2C bus 0.\n\n\t\tCONFIG_SYS_RTC_BUS_NUM\n\n\t\tIf defined, then this indicates the I2C bus number for the RTC.\n\t\tIf not defined, then U-Boot assumes that RTC is on I2C bus 0.\n\n\t\tCONFIG_SYS_DTT_BUS_NUM\n\n\t\tIf defined, then this indicates the I2C bus number for the DTT.\n\t\tIf not defined, then U-Boot assumes that DTT is on I2C bus 0.\n\n\t\tCONFIG_SYS_I2C_DTT_ADDR:\n\n\t\tIf defined, specifies the I2C address of the DTT device.\n\t\tIf not defined, then U-Boot uses predefined value for\n\t\tspecified DTT device.\n\n\t\tCONFIG_FSL_I2C\n\n\t\tDefine this option if you want to use Freescale's I2C driver in\n\t\tdrivers/i2c/fsl_i2c.c.\n\n\t\tCONFIG_I2C_MUX\n\n\t\tDefine this option if you have I2C devices reached over 1 .. n\n\t\tI2C Muxes like the pca9544a. This option addes a new I2C\n\t\tCommand \"i2c bus [muxtype:muxaddr:muxchannel]\" which adds a\n\t\tnew I2C Bus to the existing I2C Busses. If you select the\n\t\tnew Bus with \"i2c dev\", u-bbot sends first the commandos for\n\t\tthe muxes to activate this new \"bus\".\n\n\t\tCONFIG_I2C_MULTI_BUS must be also defined, to use this\n\t\tfeature!\n\n\t\tExample:\n\t\tAdding a new I2C Bus reached over 2 pca9544a muxes\n\t\t\tThe First mux with address 70 and channel 6\n\t\t\tThe Second mux with address 71 and channel 4\n\n\t\t=\u003e i2c bus pca9544a:70:6:pca9544a:71:4\n\n\t\tUse the \"i2c bus\" command without parameter, to get a list\n\t\tof I2C Busses with muxes:\n\n\t\t=\u003e i2c bus\n\t\tBusses reached over muxes:\n\t\tBus ID: 2\n\t\t  reached over Mux(es):\n\t\t    pca9544a@70 ch: 4\n\t\tBus ID: 3\n\t\t  reached over Mux(es):\n\t\t    pca9544a@70 ch: 6\n\t\t    pca9544a@71 ch: 4\n\t\t=\u003e\n\n\t\tIf you now switch to the new I2C Bus 3 with \"i2c dev 3\"\n\t\tu-boot first sends the command to the mux@70 to enable\n\t\tchannel 6, and then the command to the mux@71 to enable\n\t\tthe channel 4.\n\n\t\tAfter that, you can use the \"normal\" i2c commands as\n\t\tusual to communicate with your I2C devices behind\n\t\tthe 2 muxes.\n\n\t\tThis option is actually implemented for the bitbanging\n\t\talgorithm in common/soft_i2c.c and for the Hardware I2C\n\t\tBus on the MPC8260. But it should be not so difficult\n\t\tto add this option to other architectures.\n\n\t\tCONFIG_SOFT_I2C_READ_REPEATED_START\n\n\t\tdefining this will force the i2c_read() function in\n\t\tthe soft_i2c driver to perform an I2C repeated start\n\t\tbetween writing the address pointer and reading the\n\t\tdata.  If this define is omitted the default behaviour\n\t\tof doing a stop-start sequence will be used.  Most I2C\n\t\tdevices can use either method, but some require one or\n\t\tthe other.\n\n- SPI Support:\tCONFIG_SPI\n\n\t\tEnables SPI driver (so far only tested with\n\t\tSPI EEPROM, also an instance works with Crystal A/D and\n\t\tD/As on the SACSng board)\n\n\t\tCONFIG_SH_SPI\n\n\t\tEnables the driver for SPI controller on SuperH. Currently\n\t\tonly SH7757 is supported.\n\n\t\tCONFIG_SPI_X\n\n\t\tEnables extended (16-bit) SPI EEPROM addressing.\n\t\t(symmetrical to CONFIG_I2C_X)\n\n\t\tCONFIG_SOFT_SPI\n\n\t\tEnables a software (bit-bang) SPI driver rather than\n\t\tusing hardware support. This is a general purpose\n\t\tdriver that only requires three general I/O port pins\n\t\t(two outputs, one input) to function. If this is\n\t\tdefined, the board configuration must define several\n\t\tSPI configuration items (port pins to use, etc). For\n\t\tan example, see include/configs/sacsng.h.\n\n\t\tCONFIG_HARD_SPI\n\n\t\tEnables a hardware SPI driver for general-purpose reads\n\t\tand writes.  As with CONFIG_SOFT_SPI, the board configuration\n\t\tmust define a list of chip-select function pointers.\n\t\tCurrently supported on some MPC8xxx processors.\t For an\n\t\texample, see include/configs/mpc8349emds.h.\n\n\t\tCONFIG_MXC_SPI\n\n\t\tEnables the driver for the SPI controllers on i.MX and MXC\n\t\tSoCs. Currently i.MX31/35/51 are supported.\n\n- FPGA Support: CONFIG_FPGA\n\n\t\tEnables FPGA subsystem.\n\n\t\tCONFIG_FPGA_\u003cvendor\u003e\n\n\t\tEnables support for specific chip vendors.\n\t\t(ALTERA, XILINX)\n\n\t\tCONFIG_FPGA_\u003cfamily\u003e\n\n\t\tEnables support for FPGA family.\n\t\t(SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)\n\n\t\tCONFIG_FPGA_COUNT\n\n\t\tSpecify the number of FPGA devices to support.\n\n\t\tCONFIG_SYS_FPGA_PROG_FEEDBACK\n\n\t\tEnable printing of hash marks during FPGA configuration.\n\n\t\tCONFIG_SYS_FPGA_CHECK_BUSY\n\n\t\tEnable checks on FPGA configuration interface busy\n\t\tstatus by the configuration function. This option\n\t\twill require a board or device specific function to\n\t\tbe written.\n\n\t\tCONFIG_FPGA_DELAY\n\n\t\tIf defined, a function that provides delays in the FPGA\n\t\tconfiguration driver.\n\n\t\tCONFIG_SYS_FPGA_CHECK_CTRLC\n\t\tAllow Control-C to interrupt FPGA configuration\n\n\t\tCONFIG_SYS_FPGA_CHECK_ERROR\n\n\t\tCheck for configuration errors during FPGA bitfile\n\t\tloading. For example, abort during Virtex II\n\t\tconfiguration if the INIT_B line goes low (which\n\t\tindicated a CRC error).\n\n\t\tCONFIG_SYS_FPGA_WAIT_INIT\n\n\t\tMaximum time to wait for the INIT_B line to deassert\n\t\tafter PROB_B has been deasserted during a Virtex II\n\t\tFPGA configuration sequence. The default time is 500\n\t\tms.\n\n\t\tCONFIG_SYS_FPGA_WAIT_BUSY\n\n\t\tMaximum time to wait for BUSY to deassert during\n\t\tVirtex II FPGA configuration. The default is 5 ms.\n\n\t\tCONFIG_SYS_FPGA_WAIT_CONFIG\n\n\t\tTime to wait after FPGA configuration. The default is\n\t\t200 ms.\n\n- Configuration Management:\n\t\tCONFIG_IDENT_STRING\n\n\t\tIf defined, this string will be added to the U-Boot\n\t\tversion information (U_BOOT_VERSION)\n\n- Vendor Parameter Protection:\n\n\t\tU-Boot considers the values of the environment\n\t\tvariables \"serial#\" (Board Serial Number) and\n\t\t\"ethaddr\" (Ethernet Address) to be parameters that\n\t\tare set once by the board vendor / manufacturer, and\n\t\tprotects these variables from casual modification by\n\t\tthe user. Once set, these variables are read-only,\n\t\tand write or delete attempts are rejected. You can\n\t\tchange this behaviour:\n\n\t\tIf CONFIG_ENV_OVERWRITE is #defined in your config\n\t\tfile, the write protection for vendor parameters is\n\t\tcompletely disabled. Anybody can change or delete\n\t\tthese parameters.\n\n\t\tAlternatively, if you #define _both_ CONFIG_ETHADDR\n\t\t_and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default\n\t\tEthernet address is installed in the environment,\n\t\twhich can be changed exactly ONCE by the user. [The\n\t\tserial# is unaffected by this, i. e. it remains\n\t\tread-only.]\n\n\t\tThe same can be accomplished in a more flexible way\n\t\tfor any variable by configuring the type of access\n\t\tto allow for those variables in the \".flags\" variable\n\t\tor define CONFIG_ENV_FLAGS_LIST_STATIC.\n\n- Protected RAM:\n\t\tCONFIG_PRAM\n\n\t\tDefine this variable to enable the reservation of\n\t\t\"protected RAM\", i. e. RAM which is not overwritten\n\t\tby U-Boot. Define CONFIG_PRAM to hold the number of\n\t\tkB you want to reserve for pRAM. You can overwrite\n\t\tthis default value by defining an environment\n\t\tvariable \"pram\" to the number of kB you want to\n\t\treserve. Note that the board info structure will\n\t\tstill show the full amount of RAM. If pRAM is\n\t\treserved, a new environment variable \"mem\" will\n\t\tautomatically be defined to hold the amount of\n\t\tremaining RAM in a form that can be passed as boot\n\t\targument to Linux, for instance like that:\n\n\t\t\tsetenv bootargs ... mem=\\${mem}\n\t\t\tsaveenv\n\n\t\tThis way you can tell Linux not to use this memory,\n\t\teither, which results in a memory region that will\n\t\tnot be affected by reboots.\n\n\t\t*WARNING* If your board configuration uses automatic\n\t\tdetection of the RAM size, you must make sure that\n\t\tthis memory test is non-destructive. So far, the\n\t\tfollowing board configurations are known to be\n\t\t\"pRAM-clean\":\n\n\t\t\tIVMS8, IVML24, SPD8xx, TQM8xxL,\n\t\t\tHERMES, IP860, RPXlite, LWMON,\n\t\t\tFLAGADM, TQM8260\n\n- Access to physical memory region (\u003e 4GB)\n\t\tSome basic support is provided for operations on memory not\n\t\tnormally accessible to U-Boot - e.g. some architectures\n\t\tsupport access to more than 4GB of memory on 32-bit\n\t\tmachines using physical address extension or similar.\n\t\tDefine CONFIG_PHYSMEM to access this basic support, which\n\t\tcurrently only supports clearing the memory.\n\n- Error Recovery:\n\t\tCONFIG_PANIC_HANG\n\n\t\tDefine this variable to stop the system in case of a\n\t\tfatal error, so that you have to reset it manually.\n\t\tThis is probably NOT a good idea for an embedded\n\t\tsystem where you want the system to reboot\n\t\tautomatically as fast as possible, but it may be\n\t\tuseful during development since you can try to debug\n\t\tthe conditions that lead to the situation.\n\n\t\tCONFIG_NET_RETRY_COUNT\n\n\t\tThis variable defines the number of retries for\n\t\tnetwork operations like ARP, RARP, TFTP, or BOOTP\n\t\tbefore giving up the operation. If not defined, a\n\t\tdefault value of 5 is used.\n\n\t\tCONFIG_ARP_TIMEOUT\n\n\t\tTimeout waiting for an ARP reply in milliseconds.\n\n\t\tCONFIG_NFS_TIMEOUT\n\n\t\tTimeout in milliseconds used in NFS protocol.\n\t\tIf you encounter \"ERROR: Cannot umount\" in nfs command,\n\t\ttry longer timeout such as\n\t\t#define CONFIG_NFS_TIMEOUT 10000UL\n\n- Command Interpreter:\n\t\tCONFIG_AUTO_COMPLETE\n\n\t\tEnable auto completion of commands using TAB.\n\n\t\tNote that this feature has NOT been implemented yet\n\t\tfor the \"hush\" shell.\n\n\n\t\tCONFIG_SYS_HUSH_PARSER\n\n\t\tDefine this variable to enable the \"hush\" shell (from\n\t\tBusybox) as command line interpreter, thus enabling\n\t\tpowerful command line syntax like\n\t\tif...then...else...fi conditionals or `\u0026\u0026' and '||'\n\t\tconstructs (\"shell scripts\").\n\n\t\tIf undefined, you get the old, much simpler behaviour\n\t\twith a somewhat smaller memory footprint.\n\n\n\t\tCONFIG_SYS_PROMPT_HUSH_PS2\n\n\t\tThis defines the secondary prompt string, which is\n\t\tprinted when the command interpreter needs more input\n\t\tto complete a command. Usually \"\u003e \".\n\n\tNote:\n\n\t\tIn the current implementation, the local variables\n\t\tspace and global environment variables space are\n\t\tseparated. Local variables are those you define by\n\t\tsimply typing `name=value'. To access a local\n\t\tvariable later on, you have write `$name' or\n\t\t`${name}'; to execute the contents of a variable\n\t\tdirectly type `$name' at the command prompt.\n\n\t\tGlobal environment variables are those you use\n\t\tsetenv/printenv to work with. To run a command stored\n\t\tin such a variable, you need to use the run command,\n\t\tand you must not use the '$' sign to access them.\n\n\t\tTo store commands and special characters in a\n\t\tvariable, please use double quotation marks\n\t\tsurrounding the whole text of the variable, instead\n\t\tof the backslashes before semicolons and special\n\t\tsymbols.\n\n- Commandline Editing and History:\n\t\tCONFIG_CMDLINE_EDITING\n\n\t\tEnable editing and History functions for interactive\n\t\tcommandline input operations\n\n- Default Environment:\n\t\tCONFIG_EXTRA_ENV_SETTINGS\n\n\t\tDefine this to contain any number of null terminated\n\t\tstrings (variable = value pairs) that will be part of\n\t\tthe default environment compiled into the boot image.\n\n\t\tFor example, place something like this in your\n\t\tboard's config file:\n\n\t\t#define CONFIG_EXTRA_ENV_SETTINGS \\\n\t\t\t\"myvar1=value1\\0\" \\\n\t\t\t\"myvar2=value2\\0\"\n\n\t\tWarning: This method is based on knowledge about the\n\t\tinternal format how the environment is stored by the\n\t\tU-Boot code. This is NOT an official, exported\n\t\tinterface! Although it is unlikely that this format\n\t\twill change soon, there is no guarantee either.\n\t\tYou better know what you are doing here.\n\n\t\tNote: overly (ab)use of the default environment is\n\t\tdiscouraged. Make sure to check other ways to preset\n\t\tthe environment like the \"source\" command or the\n\t\tboot command first.\n\n\t\tCONFIG_ENV_VARS_UBOOT_CONFIG\n\n\t\tDefine this in order to add variables describing the\n\t\tU-Boot build configuration to the default environment.\n\t\tThese will be named arch, cpu, board, vendor, and soc.\n\n\t\tEnabling this option will cause the following to be defined:\n\n\t\t- CONFIG_SYS_ARCH\n\t\t- CONFIG_SYS_CPU\n\t\t- CONFIG_SYS_BOARD\n\t\t- CONFIG_SYS_VENDOR\n\t\t- CONFIG_SYS_SOC\n\n\t\tCONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG\n\n\t\tDefine this in order to add variables describing certain\n\t\trun-time determined information about the hardware to the\n\t\tenvironment.  These will be named board_name, board_rev.\n\n\t\tCONFIG_DELAY_ENVIRONMENT\n\n\t\tNormally the environment is loaded when the board is\n\t\tintialised so that it is available to U-Boot. This inhibits\n\t\tthat so that the environment is not available until\n\t\texplicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL\n\t\tthis is instead controlled by the value of\n\t\t/config/load-environment.\n\n- DataFlash Support:\n\t\tCONFIG_HAS_DATAFLASH\n\n\t\tDefining this option enables DataFlash features and\n\t\tallows to read/write in Dataflash via the standard\n\t\tcommands cp, md...\n\n- Serial Flash support\n\t\tCONFIG_CMD_SF\n\n\t\tDefining this option enables SPI flash commands\n\t\t'sf probe/read/write/erase/update'.\n\n\t\tUsage requires an initial 'probe' to define the serial\n\t\tflash parameters, followed by read/write/erase/update\n\t\tcommands.\n\n\t\tThe following defaults may be provided by the platform\n\t\tto handle the common case when only a single serial\n\t\tflash is present on the system.\n\n\t\tCONFIG_SF_DEFAULT_BUS\t\tBus identifier\n\t\tCONFIG_SF_DEFAULT_CS\t\tChip-select\n\t\tCONFIG_SF_DEFAULT_MODE \t\t(see include/spi.h)\n\t\tCONFIG_SF_DEFAULT_SPEED\t\tin Hz\n\n\t\tCONFIG_CMD_SF_TEST\n\n\t\tDefine this option to include a destructive SPI flash\n\t\ttest ('sf test').\n\n\t\tCONFIG_SPI_FLASH_BAR\t\tBan/Extended Addr Reg\n\n\t\tDefine this option to use the Bank addr/Extended addr\n\t\tsupport on SPI flashes which has size \u003e 16Mbytes.\n\n- SystemACE Support:\n\t\tCONFIG_SYSTEMACE\n\n\t\tAdding this option adds support for Xilinx SystemACE\n\t\tchips attached via some sort of local bus. The address\n\t\tof the chip must also be defined in the\n\t\tCONFIG_SYS_SYSTEMACE_BASE macro. For example:\n\n\t\t#define CONFIG_SYSTEMACE\n\t\t#define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000\n\n\t\tWhen SystemACE support is added, the \"ace\" device type\n\t\tbecomes available to the fat commands, i.e. fatls.\n\n- TFTP Fixed UDP Port:\n\t\tCONFIG_TFTP_PORT\n\n\t\tIf this is defined, the environment variable tftpsrcp\n\t\tis used to supply the TFTP UDP source port value.\n\t\tIf tftpsrcp isn't defined, the normal pseudo-random port\n\t\tnumber generator is used.\n\n\t\tAlso, the environment variable tftpdstp is used to supply\n\t\tthe TFTP UDP destination port value.  If tftpdstp isn't\n\t\tdefined, the normal port 69 is used.\n\n\t\tThe purpose for tftpsrcp is to allow a TFTP server to\n\t\tblindly start the TFTP transfer using the pre-configured\n\t\ttarget IP address and UDP port. This has the effect of\n\t\t\"punching through\" the (Windows XP) firewall, allowing\n\t\tthe remainder of the TFTP transfer to proceed normally.\n\t\tA better solution is to properly configure the firewall,\n\t\tbut sometimes that is not allowed.\n\n- Hashing support:\n\t\tCONFIG_CMD_HASH\n\n\t\tThis enables a generic 'hash' command which can produce\n\t\thashes / digests from a few algorithms (e.g. SHA1, SHA256).\n\n\t\tCONFIG_HASH_VERIFY\n\n\t\tEnable the hash verify command (hash -v). This adds to code\n\t\tsize a little.\n\n\t\tCONFIG_SHA1 - support SHA1 hashing\n\t\tCONFIG_SHA256 - support SHA256 hashing\n\n\t\tNote: There is also a sha1sum command, which should perhaps\n\t\tbe deprecated in favour of 'hash sha1'.\n\n- Signing support:\n\t\tCONFIG_RSA\n\n\t\tThis enables the RSA algorithm used for FIT image verification\n\t\tin U-Boot. See doc/uImage/signature for more information.\n\n\t\tThe signing part is build into mkimage regardless of this\n\t\toption.\n\n\n- Show boot progress:\n\t\tCONFIG_SHOW_BOOT_PROGRESS\n\n\t\tDefining this option allows to add some board-\n\t\tspecific code (calling a user-provided function\n\t\t\"show_boot_progress(int)\") that enables you to show\n\t\tthe system's boot progress on some display (for\n\t\texample, some LED's) on your board. At the moment,\n\t\tthe following checkpoints are implemented:\n\n- Detailed boot stage timing\n\t\tCONFIG_BOOTSTAGE\n\t\tDefine this option to get detailed timing of each stage\n\t\tof the boot process.\n\n\t\tCONFIG_BOOTSTAGE_USER_COUNT\n\t\tThis is the number of available user bootstage records.\n\t\tEach time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)\n\t\ta new ID will be allocated from this stash. If you exceed\n\t\tthe limit, recording will stop.\n\n\t\tCONFIG_BOOTSTAGE_REPORT\n\t\tDefine this to print a report before boot, similar to this:\n\n\t\tTimer summary in microseconds:\n\t\t       Mark    Elapsed  Stage\n\t\t\t  0          0  reset\n\t\t  3,575,678  3,575,678  board_init_f start\n\t\t  3,575,695         17  arch_cpu_init A9\n\t\t  3,575,777         82  arch_cpu_init done\n\t\t  3,659,598     83,821  board_init_r start\n\t\t  3,910,375    250,777  main_loop\n\t\t 29,916,167 26,005,792  bootm_start\n\t\t 30,361,327    445,160  start_kernel\n\n\t\tCONFIG_CMD_BOOTSTAGE\n\t\tAdd a 'bootstage' command which supports printing a report\n\t\tand un/stashing of bootstage data.\n\n\t\tCONFIG_BOOTSTAGE_FDT\n\t\tStash the bootstage information in the FDT. A root 'bootstage'\n\t\tnode is created with each bootstage id as a child. Each child\n\t\thas a 'name' property and either 'mark' containing the\n\t\tmark time in microsecond, or 'accum' containing the\n\t\taccumulated time for that bootstage id in microseconds.\n\t\tFor example:\n\n\t\tbootstage {\n\t\t\t154 {\n\t\t\t\tname = \"board_init_f\";\n\t\t\t\tmark = \u003c3575678\u003e;\n\t\t\t};\n\t\t\t170 {\n\t\t\t\tname = \"lcd\";\n\t\t\t\taccum = \u003c33482\u003e;\n\t\t\t};\n\t\t};\n\n\t\tCode in the Linux kernel can find this in /proc/devicetree.\n\nLegacy uImage format:\n\n  Arg\tWhere\t\t\tWhen\n    1\tcommon/cmd_bootm.c\tbefore attempting to boot an image\n   -1\tcommon/cmd_bootm.c\tImage header has bad\t magic number\n    2\tcommon/cmd_bootm.c\tImage header has correct magic number\n   -2\tcommon/cmd_bootm.c\tImage header has bad\t checksum\n    3\tcommon/cmd_bootm.c\tImage header has correct checksum\n   -3\tcommon/cmd_bootm.c\tImage data   has bad\t checksum\n    4\tcommon/cmd_bootm.c\tImage data   has correct checksum\n   -4\tcommon/cmd_bootm.c\tImage is for unsupported architecture\n    5\tcommon/cmd_bootm.c\tArchitecture check OK\n   -5\tcommon/cmd_bootm.c\tWrong Image Type (not kernel, multi)\n    6\tcommon/cmd_bootm.c\tImage Type check OK\n   -6\tcommon/cmd_bootm.c\tgunzip uncompression error\n   -7\tcommon/cmd_bootm.c\tUnimplemented compression type\n    7\tcommon/cmd_bootm.c\tUncompression OK\n    8\tcommon/cmd_bootm.c\tNo uncompress/copy overwrite error\n   -9\tcommon/cmd_bootm.c\tUnsupported OS (not Linux, BSD, VxWorks, QNX)\n\n    9\tcommon/image.c\t\tStart initial ramdisk verification\n  -10\tcommon/image.c\t\tRamdisk header has bad\t   magic number\n  -11\tcommon/image.c\t\tRamdisk header has bad\t   checksum\n   10\tcommon/image.c\t\tRamdisk header is OK\n  -12\tcommon/image.c\t\tRamdisk data   has bad\t   checksum\n   11\tcommon/image.c\t\tRamdisk data   has correct checksum\n   12\tcommon/image.c\t\tRamdisk verification complete, start loading\n  -13\tcommon/image.c\t\tWrong Image Type (not PPC Linux ramdisk)\n   13\tcommon/image.c\t\tStart multifile image verification\n   14\tcommon/image.c\t\tNo initial ramdisk, no multifile, continue.\n\n   15\tarch/\u003carch\u003e/lib/bootm.c All preparation done, transferring control to OS\n\n  -30\tarch/powerpc/lib/board.c\tFatal error, hang the system\n  -31\tpost/post.c\t\tPOST test failed, detected by post_output_backlog()\n  -32\tpost/post.c\t\tPOST test failed, detected by post_run_single()\n\n   34\tcommon/cmd_doc.c\tbefore loading a Image from a DOC device\n  -35\tcommon/cmd_doc.c\tBad usage of \"doc\" command\n   35\tcommon/cmd_doc.c\tcorrect usage of \"doc\" command\n  -36\tcommon/cmd_doc.c\tNo boot device\n   36\tcommon/cmd_doc.c\tcorrect boot device\n  -37\tcommon/cmd_doc.c\tUnknown Chip ID on boot device\n   37\tcommon/cmd_doc.c\tcorrect chip ID found, device available\n  -38\tcommon/cmd_doc.c\tRead Error on boot device\n   38\tcommon/cmd_doc.c\treading Image header from DOC device OK\n  -39\tcommon/cmd_doc.c\tImage header has bad magic number\n   39\tcommon/cmd_doc.c\tImage header has correct magic number\n  -40\tcommon/cmd_doc.c\tError reading Image from DOC device\n   40\tcommon/cmd_doc.c\tImage header has correct magic number\n   41\tcommon/cmd_ide.c\tbefore loading a Image from a IDE device\n  -42\tcommon/cmd_ide.c\tBad usage of \"ide\" command\n   42\tcommon/cmd_ide.c\tcorrect usage of \"ide\" command\n  -43\tcommon/cmd_ide.c\tNo boot device\n   43\tcommon/cmd_ide.c\tboot device found\n  -44\tcommon/cmd_ide.c\tDevice not available\n   44\tcommon/cmd_ide.c\tDevice available\n  -45\tcommon/cmd_ide.c\twrong partition selected\n   45\tcommon/cmd_ide.c\tpartition selected\n  -46\tcommon/cmd_ide.c\tUnknown partition table\n   46\tcommon/cmd_ide.c\tvalid partition table found\n  -47\tcommon/cmd_ide.c\tInvalid partition type\n   47\tcommon/cmd_ide.c\tcorrect partition type\n  -48\tcommon/cmd_ide.c\tError reading Image Header on boot device\n   48\tcommon/cmd_ide.c\treading Image Header from IDE device OK\n  -49\tcommon/cmd_ide.c\tImage header has bad magic number\n   49\tcommon/cmd_ide.c\tImage header has correct magic number\n  -50\tcommon/cmd_ide.c\tImage header has bad\t checksum\n   50\tcommon/cmd_ide.c\tImage header has correct checksum\n  -51\tcommon/cmd_ide.c\tError reading Image from IDE device\n   51\tcommon/cmd_ide.c\treading Image from IDE device OK\n   52\tcommon/cmd_nand.c\tbefore loading a Image from a NAND device\n  -53\tcommon/cmd_nand.c\tBad usage of \"nand\" command\n   53\tcommon/cmd_nand.c\tcorrect usage of \"nand\" command\n  -54\tcommon/cmd_nand.c\tNo boot device\n   54\tcommon/cmd_nand.c\tboot device found\n  -55\tcommon/cmd_nand.c\tUnknown Chip ID on boot device\n   55\tcommon/cmd_nand.c\tcorrect chip ID found, device available\n  -56\tcommon/cmd_nand.c\tError reading Image Header on boot device\n   56\tcommon/cmd_nand.c\treading Image Header from NAND device OK\n  -57\tcommon/cmd_nand.c\tImage header has bad magic number\n   57\tcommon/cmd_nand.c\tImage header has correct magic number\n  -58\tcommon/cmd_nand.c\tError reading Image from NAND device\n   58\tcommon/cmd_nand.c\treading Image from NAND device OK\n\n  -60\tcommon/env_common.c\tEnvironment has a bad CRC, using default\n\n   64\tnet/eth.c\t\tstarting with Ethernet configuration.\n  -64\tnet/eth.c\t\tno Ethernet found.\n   65\tnet/eth.c\t\tEthernet found.\n\n  -80\tcommon/cmd_net.c\tusage wrong\n   80\tcommon/cmd_net.c\tbefore calling NetLoop()\n  -81\tcommon/cmd_net.c\tsome error in NetLoop() occurred\n   81\tcommon/cmd_net.c\tNetLoop() back without error\n  -82\tcommon/cmd_net.c\tsize == 0 (File with size 0 loaded)\n   82\tcommon/cmd_net.c\ttrying automatic boot\n   83\tcommon/cmd_net.c\trunning \"source\" command\n  -83\tcommon/cmd_net.c\tsome error in automatic boot or \"source\" command\n   84\tcommon/cmd_net.c\tend without errors\n\nFIT uImage format:\n\n  Arg\tWhere\t\t\tWhen\n  100\tcommon/cmd_bootm.c\tKernel FIT Image has correct format\n -100\tcommon/cmd_bootm.c\tKernel FIT Image has incorrect format\n  101\tcommon/cmd_bootm.c\tNo Kernel subimage unit name, using configuration\n -101\tcommon/cmd_bootm.c\tCan't get configuration for kernel subimage\n  102\tcommon/cmd_bootm.c\tKernel unit name specified\n -103\tcommon/cmd_bootm.c\tCan't get kernel subimage node offset\n  103\tcommon/cmd_bootm.c\tFound configuration node\n  104\tcommon/cmd_bootm.c\tGot kernel subimage node offset\n -104\tcommon/cmd_bootm.c\tKernel subimage hash verification failed\n  105\tcommon/cmd_bootm.c\tKernel subimage hash verification OK\n -105\tcommon/cmd_bootm.c\tKernel subimage is for unsupported architecture\n  106\tcommon/cmd_bootm.c\tArchitecture check OK\n -106\tcommon/cmd_bootm.c\tKernel subimage has wrong type\n  107\tcommon/cmd_bootm.c\tKernel subimage type OK\n -107\tcommon/cmd_bootm.c\tCan't get kernel subimage data/size\n  108\tcommon/cmd_bootm.c\tGot kernel subimage data/size\n -108\tcommon/cmd_bootm.c\tWrong image type (not legacy, FIT)\n -109\tcommon/cmd_bootm.c\tCan't get kernel subimage type\n -110\tcommon/cmd_bootm.c\tCan't get kernel subimage comp\n -111\tcommon/cmd_bootm.c\tCan't get kernel subimage os\n -112\tcommon/cmd_bootm.c\tCan't get kernel subimage load address\n -113\tcommon/cmd_bootm.c\tImage uncompress/copy overwrite error\n\n  120\tcommon/image.c\t\tStart initial ramdisk verification\n -120\tcommon/image.c\t\tRamdisk FIT image has incorrect format\n  121\tcommon/image.c\t\tRamdisk FIT image has correct format\n  122\tcommon/image.c\t\tNo ramdisk subimage unit name, using configuration\n -122\tcommon/image.c\t\tCan't get configuration for ramdisk subimage\n  123\tcommon/image.c\t\tRamdisk unit name specified\n -124\tcommon/image.c\t\tCan't get ramdisk subimage node offset\n  125\tcommon/image.c\t\tGot ramdisk subimage node offset\n -125\tcommon/image.c\t\tRamdisk subimage hash verification failed\n  126\tcommon/image.c\t\tRamdisk subimage hash verification OK\n -126\tcommon/image.c\t\tRamdisk subimage for unsupported architecture\n  127\tcommon/image.c\t\tArchitecture check OK\n -127\tcommon/image.c\t\tCan't get ramdisk subimage data/size\n  128\tcommon/image.c\t\tGot ramdisk subimage data/size\n  129\tcommon/image.c\t\tCan't get ramdisk load address\n -129\tcommon/image.c\t\tGot ramdisk load address\n\n -130\tcommon/cmd_doc.c\tIncorrect FIT image format\n  131\tcommon/cmd_doc.c\tFIT image format OK\n\n -140\tcommon/cmd_ide.c\tIncorrect FIT image format\n  141\tcommon/cmd_ide.c\tFIT image format OK\n\n -150\tcommon/cmd_nand.c\tIncorrect FIT image format\n  151\tcommon/cmd_nand.c\tFIT image format OK\n\n- FIT image support:\n\t\tCONFIG_FIT\n\t\tEnable support for the FIT uImage format.\n\n\t\tCONFIG_FIT_BEST_MATCH\n\t\tWhen no configuration is explicitly selected, default to the\n\t\tone whose fdt's compatibility field best matches that of\n\t\tU-Boot itself. A match is considered \"best\" if it matches the\n\t\tmost specific compatibility entry of U-Boot's fdt's root node.\n\t\tThe order of entries in the configuration's fdt is ignored.\n\n\t\tCONFIG_FIT_SIGNATURE\n\t\tThis option enables signature verification of FIT uImages,\n\t\tusing a hash signed and verified using RSA. See\n\t\tdoc/uImage.FIT/signature.txt for more details.\n\n- Standalone program support:\n\t\tCONFIG_STANDALONE_LOAD_ADDR\n\n\t\tThis option defines a board specific value for the\n\t\taddress where standalone program gets loaded, thus\n\t\toverwriting the architecture dependent default\n\t\tsettings.\n\n- Frame Buffer Address:\n\t\tCONFIG_FB_ADDR\n\n\t\tDefine CONFIG_FB_ADDR if you want to use specific\n\t\taddress for frame buffer.  This is typically the case\n\t\twhen using a graphics controller has separate video\n\t\tmemory.  U-Boot will then place the frame buffer at\n\t\tthe given address instead of dynamically reserving it\n\t\tin system RAM by calling lcd_setmem(), which grabs\n\t\tthe memory for the frame buffer depending on the\n\t\tconfigured panel size.\n\n\t\tPlease see board_init_f function.\n\n- Automatic software updates via TFTP server\n\t\tCONFIG_UPDATE_TFTP\n\t\tCONFIG_UPDATE_TFTP_CNT_MAX\n\t\tCONFIG_UPDATE_TFTP_MSEC_MAX\n\n\t\tThese options enable and control the auto-update feature;\n\t\tfor a more detailed description refer to doc/README.update.\n\n- MTD Support (mtdparts command, UBI support)\n\t\tCONFIG_MTD_DEVICE\n\n\t\tAdds the MTD device infrastructure from the Linux kernel.\n\t\tNeeded for mtdparts command support.\n\n\t\tCONFIG_MTD_PARTITIONS\n\n\t\tAdds the MTD partitioning infrastructure from the Linux\n\t\tkernel. Needed for UBI support.\n\n- UBI support\n\t\tCONFIG_CMD_UBI\n\n\t\tAdds commands for interacting with MTD partitions formatted\n\t\twith the UBI flash translation layer\n\n\t\tRequires also defining CONFIG_RBTREE\n\n\t\tCONFIG_UBI_SILENCE_MSG\n\n\t\tMake the verbose messages from UBI stop printing.  This leaves\n\t\twarnings and errors enabled.\n\n- UBIFS support\n\t\tCONFIG_CMD_UBIFS\n\n\t\tAdds commands for interacting with UBI volumes formatted as\n\t\tUBIFS.  UBIFS is read-only in u-boot.\n\n\t\tRequires UBI support as well as CONFIG_LZO\n\n\t\tCONFIG_UBIFS_SILENCE_MSG\n\n\t\tMake the verbose messages from UBIFS stop printing.  This leaves\n\t\twarnings and errors enabled.\n\n- SPL framework\n\t\tCONFIG_SPL\n\t\tEnable building of SPL globally.\n\n\t\tCONFIG_SPL_LDSCRIPT\n\t\tLDSCRIPT for linking the SPL binary.\n\n\t\tCONFIG_SPL_MAX_FOOTPRINT\n\t\tMaximum size in memory allocated to the SPL, BSS included.\n\t\tWhen defined, the linker checks that the actual memory\n\t\tused by SPL from _start to __bss_end does not exceed it.\n\t\tCONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE\n\t\tmust not be both defined at the same time.\n\n\t\tCONFIG_SPL_MAX_SIZE\n\t\tMaximum size of the SPL image (text, data, rodata, and\n\t\tlinker lists sections), BSS excluded.\n\t\tWhen defined, the linker checks that the actual size does\n\t\tnot exceed it.\n\n\t\tCONFIG_SPL_TEXT_BASE\n\t\tTEXT_BASE for linking the SPL binary.\n\n\t\tCONFIG_SPL_RELOC_TEXT_BASE\n\t\tAddress to relocate to.  If unspecified, this is equal to\n\t\tCONFIG_SPL_TEXT_BASE (i.e. no relocation is done).\n\n\t\tCONFIG_SPL_BSS_START_ADDR\n\t\tLink address for the BSS within the SPL binary.\n\n\t\tCONFIG_SPL_BSS_MAX_SIZE\n\t\tMaximum size in memory allocated to the SPL BSS.\n\t\tWhen defined, the linker checks that the actual memory used\n\t\tby SPL from __bss_start to __bss_end does not exceed it.\n\t\tCONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE\n\t\tmust not be both defined at the same time.\n\n\t\tCONFIG_SPL_STACK\n\t\tAdress of the start of the stack SPL will use\n\n\t\tCONFIG_SPL_RELOC_STACK\n\t\tAdress of the start of the stack SPL will use after\n\t\trelocation.  If unspecified, this is equal to\n\t\tCONFIG_SPL_STACK.\n\n\t\tCONFIG_SYS_SPL_MALLOC_START\n\t\tStarting address of the malloc pool used in SPL.\n\n\t\tCONFIG_SYS_SPL_MALLOC_SIZE\n\t\tThe size of the malloc pool used in SPL.\n\n\t\tCONFIG_SPL_FRAMEWORK\n\t\tEnable the SPL framework under common/.  This framework\n\t\tsupports MMC, NAND and YMODEM loading of U-Boot and NAND\n\t\tNAND loading of the Linux Kernel.\n\n\t\tCONFIG_SPL_DISPLAY_PRINT\n\t\tFor ARM, enable an optional function to print more information\n\t\tabout the running system.\n\n\t\tCONFIG_SPL_INIT_MINIMAL\n\t\tArch init code should be built for a very small image\n\n\t\tCONFIG_SPL_LIBCOMMON_SUPPORT\n\t\tSupport for common/libcommon.o in SPL binary\n\n\t\tCONFIG_SPL_LIBDISK_SUPPORT\n\t\tSupport for disk/libdisk.o in SPL binary\n\n\t\tCONFIG_SPL_I2C_SUPPORT\n\t\tSupport for drivers/i2c/libi2c.o in SPL binary\n\n\t\tCONFIG_SPL_GPIO_SUPPORT\n\t\tSupport for drivers/gpio/libgpio.o in SPL binary\n\n\t\tCONFIG_SPL_MMC_SUPPORT\n\t\tSupport for drivers/mmc/libmmc.o in SPL binary\n\n\t\tCONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR,\n\t\tCONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS,\n\t\tCONFIG_SYS_MMC_SD_FAT_BOOT_PARTITION\n\t\tAddress, size and partition on the MMC to load U-Boot from\n\t\twhen the MMC is being used in raw mode.\n\n\t\tCONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR\n\t\tSector to load kernel uImage from when MMC is being\n\t\tused in raw mode (for Falcon mode)\n\n\t\tCONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR,\n\t\tCONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS\n\t\tSector and number of sectors to load kernel argument\n\t\tparameters from when MMC is being used in raw mode\n\t\t(for falcon mode)\n\n\t\tCONFIG_SPL_FAT_SUPPORT\n\t\tSupport for fs/fat/libfat.o in SPL binary\n\n\t\tCONFIG_SPL_FAT_LOAD_PAYLOAD_NAME\n\t\tFilename to read to load U-Boot when reading from FAT\n\n\t\tCONFIG_SPL_FAT_LOAD_KERNEL_NAME\n\t\tFilename to read to load kernel uImage when reading\n\t\tfrom FAT (for Falcon mode)\n\n\t\tCONFIG_SPL_FAT_LOAD_ARGS_NAME\n\t\tFilename to read to load kernel argument parameters\n\t\twhen reading from FAT (for Falcon mode)\n\n\t\tCONFIG_SPL_MPC83XX_WAIT_FOR_NAND\n\t\tSet this for NAND SPL on PPC mpc83xx targets, so that\n\t\tstart.S waits for the rest of the SPL to load before\n\t\tcontinuing (the hardware starts execution after just\n\t\tloading the first page rather than the full 4K).\n\n\t\tCONFIG_SPL_NAND_BASE\n\t\tInclude nand_base.c in the SPL.  Requires\n\t\tCONFIG_SPL_NAND_DRIVERS.\n\n\t\tCONFIG_SPL_NAND_DRIVERS\n\t\tSPL uses normal NAND drivers, not minimal drivers.\n\n\t\tCONFIG_SPL_NAND_ECC\n\t\tInclude standard software ECC in the SPL\n\n\t\tCONFIG_SPL_NAND_SIMPLE\n\t\tSupport for NAND boot using simple NAND drivers that\n\t\texpose the cmd_ctrl() interface.\n\n\t\tCONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT,\n\t\tCONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE,\n\t\tCONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS,\n\t\tCONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE,\n\t\tCONFIG_SYS_NAND_ECCBYTES\n\t\tDefines the size and behavior of the NAND that SPL uses\n\t\tto read U-Boot\n\n\t\tCONFIG_SYS_NAND_U_BOOT_OFFS\n\t\tLocation in NAND to read U-Boot from\n\n\t\tCONFIG_SYS_NAND_U_BOOT_DST\n\t\tLocation in memory to load U-Boot to\n\n\t\tCONFIG_SYS_NAND_U_BOOT_SIZE\n\t\tSize of image to load\n\n\t\tCONFIG_SYS_NAND_U_BOOT_START\n\t\tEntry point in loaded image to jump to\n\n\t\tCONFIG_SYS_NAND_HW_ECC_OOBFIRST\n\t\tDefine this if you need to first read the OOB and then the\n\t\tdata. This is used for example on davinci plattforms.\n\n\t\tCONFIG_SPL_OMAP3_ID_NAND\n\t\tSupport for an OMAP3-specific set of functions to return the\n\t\tID and MFR of the first attached NAND chip, if present.\n\n\t\tCONFIG_SPL_SERIAL_SUPPORT\n\t\tSupport for drivers/serial/libserial.o in SPL binary\n\n\t\tCONFIG_SPL_SPI_FLASH_SUPPORT\n\t\tSupport for drivers/mtd/spi/libspi_flash.o in SPL binary\n\n\t\tCONFIG_SPL_SPI_SUPPORT\n\t\tSupport for drivers/spi/libspi.o in SPL binary\n\n\t\tCONFIG_SPL_RAM_DEVICE\n\t\tSupport for running image already present in ram, in SPL binary\n\n\t\tCONFIG_SPL_LIBGENERIC_SUPPORT\n\t\tSupport for lib/libgeneric.o in SPL binary\n\n\t\tCONFIG_SPL_ENV_SUPPORT\n\t\tSupport for the environment operating in SPL binary\n\n\t\tCONFIG_SPL_NET_SUPPORT\n\t\tSupport for the net/libnet.o in SPL binary.\n\t\tIt conflicts with SPL env from storage medium specified by\n\t\tCONFIG_ENV_IS_xxx but CONFIG_ENV_IS_NOWHERE\n\n\t\tCONFIG_SPL_PAD_TO\n\t\tImage offset to which the SPL should be padded before appending\n\t\tthe SPL payload. By default, this is defined as\n\t\tCONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.\n\t\tCONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL\n\t\tpayload without any padding, or \u003e= CONFIG_SPL_MAX_SIZE.\n\n\t\tCONFIG_SPL_TARGET\n\t\tFinal target image containing SPL and payload.  Some SPLs\n\t\tuse an arch-specific makefile fragment instead, for\n\t\texample if more than one image needs to be produced.\n\n\t\tCONFIG_FIT_SPL_PRINT\n\t\tPrinting information about a FIT image adds quite a bit of\n\t\tcode to SPL. So this is normally disabled in SPL. Use this\n\t\toption to re-enable it. This will affect the output of the\n\t\tbootm command when booting a FIT image.\n\nModem Support:\n--------------\n\n[so far only for SMDK2400 boards]\n\n- Modem support enable:\n\t\tCONFIG_MODEM_SUPPORT\n\n- RTS/CTS Flow control enable:\n\t\tCONFIG_HWFLOW\n\n- Modem debug support:\n\t\tCONFIG_MODEM_SUPPORT_DEBUG\n\n\t\tEnables debugging stuff (char screen[1024], dbg())\n\t\tfor modem support. Useful only with BDI2000.\n\n- Interrupt support (PPC):\n\n\t\tThere are common interrupt_init() and timer_interrupt()\n\t\tfor all PPC archs. interrupt_init() calls interrupt_init_cpu()\n\t\tfor CPU specific initialization. interrupt_init_cpu()\n\t\tshould set decrementer_count to appropriate value. If\n\t\tCPU resets decrementer automatically after interrupt\n\t\t(ppc4xx) it should set decrementer_count to zero.\n\t\ttimer_interrupt() calls timer_interrupt_cpu() for CPU\n\t\tspecific handling. If board has watchdog / status_led\n\t\t/ other_activity_monitor it works automatically from\n\t\tgeneral timer_interrupt().\n\n- General:\n\n\t\tIn the target system modem support is enabled when a\n\t\tspecific key (key combination) is pressed during\n\t\tpower-on. Otherwise U-Boot will boot normally\n\t\t(autoboot). The key_pressed() function is called from\n\t\tboard_init(). Currently key_pressed() is a dummy\n\t\tfunction, returning 1 and thus enabling modem\n\t\tinitialization.\n\n\t\tIf there are no modem init strings in the\n\t\tenvironment, U-Boot proceed to autoboot; the\n\t\tprevious output (banner, info printfs) will be\n\t\tsuppressed, though.\n\n\t\tSee also: doc/README.Modem\n\nBoard initialization settings:\n------------------------------\n\nDuring Initialization u-boot calls a number of board specific functions\nto allow the preparation of board specific prerequisites, e.g. pin setup\nbefore drivers are initialized. To enable these callbacks the\nfollowing configuration macros have to be defined. Currently this is\narchitecture specific, so please check arch/your_architecture/lib/board.c\ntypically in board_init_f() and board_init_r().\n\n- CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f()\n- CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r()\n- CONFIG_BOARD_LATE_INIT: Call board_late_init()\n- CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init()\n\nConfiguration Settings:\n-----------------------\n\n- CONFIG_SYS_LONGHELP: Defined when you want long help messages included;\n\t\tundefine this when you're short of memory.\n\n- CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default\n\t\twidth of the commands listed in the 'help' command output.\n\n- CONFIG_SYS_PROMPT:\tThis is what U-Boot prints on the console to\n\t\tprompt for user input.\n\n- CONFIG_SYS_CBSIZE:\tBuffer size for input from the Console\n\n- CONFIG_SYS_PBSIZE:\tBuffer size for Console output\n\n- CONFIG_SYS_MAXARGS:\tmax. Number of arguments accepted for monitor commands\n\n- CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to\n\t\tthe application (usually a Linux kernel) when it is\n\t\tbooted\n\n- CONFIG_SYS_BAUDRATE_TABLE:\n\t\tList of legal baudrate settings for this board.\n\n- CONFIG_SYS_CONSOLE_INFO_QUIET\n\t\tSuppress display of console information at boot.\n\n- CONFIG_SYS_CONSOLE_IS_IN_ENV\n\t\tIf the board specific function\n\t\t\textern int overwrite_console (void);\n\t\treturns 1, the stdin, stderr and stdout are switched to the\n\t\tserial port, else the settings in the environment are used.\n\n- CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE\n\t\tEnable the call to overwrite_console().\n\n- CONFIG_SYS_CONSOLE_ENV_OVERWRITE\n\t\tEnable overwrite of previous console environment settings.\n\n- CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END:\n\t\tBegin and End addresses of the area used by the\n\t\tsimple memory test.\n\n- CONFIG_SYS_ALT_MEMTEST:\n\t\tEnable an alternate, more extensive memory test.\n\n- CONFIG_SYS_MEMTEST_SCRATCH:\n\t\tScratch address used by the alternate memory test\n\t\tYou only need to set this if address zero isn't writeable\n\n- CONFIG_SYS_MEM_TOP_HIDE (PPC only):\n\t\tIf CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,\n\t\tthis specified memory area will get subtracted from the top\n\t\t(end) of RAM and won't get \"touched\" at all by U-Boot. By\n\t\tfixing up gd-\u003eram_size the Linux kernel should gets passed\n\t\tthe now \"corrected\" memory size and won't touch it either.\n\t\tThis should work for arch/ppc and arch/powerpc. Only Linux\n\t\tboard ports in arch/powerpc with bootwrapper support that\n\t\trecalculate the memory size from the SDRAM controller setup\n\t\twill have to get fixed in Linux additionally.\n\n\t\tThis option can be used as a workaround for the 440EPx/GRx\n\t\tCHIP 11 errata where the last 256 bytes in SDRAM shouldn't\n\t\tbe touched.\n\n\t\tWARNING: Please make sure that this value is a multiple of\n\t\tthe Linux page size (normally 4k). If this is not the case,\n\t\tthen the end address of the Linux memory will be located at a\n\t\tnon page size aligned address and this could cause major\n\t\tproblems.\n\n- CONFIG_SYS_LOADS_BAUD_CHANGE:\n\t\tEnable temporary baudrate change while serial download\n\n- CONFIG_SYS_SDRAM_BASE:\n\t\tPhysical start address of SDRAM. _Must_ be 0 here.\n\n- CONFIG_SYS_MBIO_BASE:\n\t\tPhysical start address of Motherboard I/O (if using a\n\t\tCogent motherboard)\n\n- CONFIG_SYS_FLASH_BASE:\n\t\tPhysical start address of Flash memory.\n\n- CONFIG_SYS_MONITOR_BASE:\n\t\tPhysical start address of boot monitor code (set by\n\t\tmake config files to be same as the text base address\n\t\t(CONFIG_SYS_TEXT_BASE) used when linking) - same as\n\t\tCONFIG_SYS_FLASH_BASE when booting from flash.\n\n- CONFIG_SYS_MONITOR_LEN:\n\t\tSize of memory reserved for monitor code, used to\n\t\tdetermine _at_compile_time_ (!) if the environment is\n\t\tembedded within the U-Boot image, or in a separate\n\t\tflash sector.\n\n- CONFIG_SYS_MALLOC_LEN:\n\t\tSize of DRAM reserved for malloc() use.\n\n- CONFIG_SYS_BOOTM_LEN:\n\t\tNormally compressed uImages are limited to an\n\t\tuncompressed size of 8 MBytes. If this is not enough,\n\t\tyou can define CONFIG_SYS_BOOTM_LEN in your board config file\n\t\tto adjust this setting to your needs.\n\n- CONFIG_SYS_BOOTMAPSZ:\n\t\tMaximum size of memory mapped by the startup code of\n\t\tthe Linux kernel; all data that must be processed by\n\t\tthe Linux kernel (bd_info, boot arguments, FDT blob if\n\t\tused) must be put below this limit, unless \"bootm_low\"\n\t\tenviroment variable is defined and non-zero. In such case\n\t\tall data for the Linux kernel must be between \"bootm_low\"\n\t\tand \"bootm_low\" + CONFIG_SYS_BOOTMAPSZ.\t The environment\n\t\tvariable \"bootm_mapsize\" will override the value of\n\t\tCONFIG_SYS_BOOTMAPSZ.  If CONFIG_SYS_BOOTMAPSZ is undefined,\n\t\tthen the value in \"bootm_size\" will be used instead.\n\n- CONFIG_SYS_BOOT_RAMDISK_HIGH:\n\t\tEnable initrd_high functionality.  If defined then the\n\t\tinitrd_high feature is enabled and the bootm ramdisk subcommand\n\t\tis enabled.\n\n- CONFIG_SYS_BOOT_GET_CMDLINE:\n\t\tEnables allocating and saving kernel cmdline in space between\n\t\t\"bootm_low\" and \"bootm_low\" + BOOTMAPSZ.\n\n- CONFIG_SYS_BOOT_GET_KBD:\n\t\tEnables allocating and saving a kernel copy of the bd_info in\n\t\tspace between \"bootm_low\" and \"bootm_low\" + BOOTMAPSZ.\n\n- CONFIG_SYS_MAX_FLASH_BANKS:\n\t\tMax number of Flash memory banks\n\n- CONFIG_SYS_MAX_FLASH_SECT:\n\t\tMax number of sectors on a Flash chip\n\n- CONFIG_SYS_FLASH_ERASE_TOUT:\n\t\tTimeout for Flash erase operations (in ms)\n\n- CONFIG_SYS_FLASH_WRITE_TOUT:\n\t\tTimeout for Flash write operations (in ms)\n\n- CONFIG_SYS_FLASH_LOCK_TOUT\n\t\tTimeout for Flash set sector lock bit operation (in ms)\n\n- CONFIG_SYS_FLASH_UNLOCK_TOUT\n\t\tTimeout for Flash clear lock bits operation (in ms)\n\n- CONFIG_SYS_FLASH_PROTECTION\n\t\tIf defined, hardware flash sectors protection is used\n\t\tinstead of U-Boot software protection.\n\n- CONFIG_SYS_DIRECT_FLASH_TFTP:\n\n\t\tEnable TFTP transfers directly to flash memory;\n\t\twithout this option such a download has to be\n\t\tperformed in two steps: (1) download to RAM, and (2)\n\t\tcopy from RAM to flash.\n\n\t\tThe two-step approach is usually more reliable, since\n\t\tyou can check if the download worked before you erase\n\t\tthe flash, but in some situations (when system RAM is\n\t\ttoo limited to allow for a temporary copy of the\n\t\tdownloaded image) this option may be very useful.\n\n- CONFIG_SYS_FLASH_CFI:\n\t\tDefine if the flash driver uses extra elements in the\n\t\tcommon flash structure for storing flash geometry.\n\n- CONFIG_FLASH_CFI_DRIVER\n\t\tThis option also enables the building of the cfi_flash driver\n\t\tin the drivers directory\n\n- CONFIG_FLASH_CFI_MTD\n\t\tThis option enables the building of the cfi_mtd driver\n\t\tin the drivers directory. The driver exports CFI flash\n\t\tto the MTD layer.\n\n- CONFIG_SYS_FLASH_USE_BUFFER_WRITE\n\t\tUse buffered writes to flash.\n\n- CONFIG_FLASH_SPANSION_S29WS_N\n\t\ts29ws-n MirrorBit flash has non-standard addresses for buffered\n\t\twrite commands.\n\n- CONFIG_SYS_FLASH_QUIET_TEST\n\t\tIf this option is defined, the common CFI flash doesn't\n\t\tprint it's warning upon not recognized FLASH banks. This\n\t\tis useful, if some of the configured banks are only\n\t\toptionally available.\n\n- CONFIG_FLASH_SHOW_PROGRESS\n\t\tIf defined (must be an integer), print out countdown\n\t\tdigits and dots.  Recommended value: 45 (9..1) for 80\n\t\tcolumn displays, 15 (3..1) for 40 column displays.\n\n- CONFIG_FLASH_VERIFY\n\t\tIf defined, the content of the flash (destination) is compared\n\t\tagainst the source after the write operation. An error message\n\t\twill be printed when the contents are not identical.\n\t\tPlease note that this option is useless in nearly all cases,\n\t\tsince such flash programming errors usually are detected earlier\n\t\twhile unprotecting/erasing/programming. Please only enable\n\t\tthis option if you really know what you are doing.\n\n- CONFIG_SYS_RX_ETH_BUFFER:\n\t\tDefines the number of Ethernet receive buffers. On some\n\t\tEthernet controllers it is recommended to set this value\n\t\tto 8 or even higher (EEPRO100 or 405 EMAC), since all\n\t\tbuffers can be full shortly after enabling the interface\n\t\ton high Ethernet traffic.\n\t\tDefaults to 4 if not defined.\n\n- CONFIG_ENV_MAX_ENTRIES\n\n\tMaximum number of entries in the hash table that is used\n\tinternally to store the environment settings. The default\n\tsetting is supposed to be generous and should work in most\n\tcases. This setting can be used to tune behaviour; see\n\tlib/hashtable.c for details.\n\n- CONFIG_ENV_FLAGS_LIST_DEFAULT\n- CONFIG_ENV_FLAGS_LIST_STATIC\n\tEnable validation of the values given to enviroment variables when\n\tcalling env set.  Variables can be restricted to only decimal,\n\thexadecimal, or boolean.  If CONFIG_CMD_NET is also defined,\n\tthe variables can also be restricted to IP address or MAC address.\n\n\tThe format of the list is:\n\t\ttype_attribute = [s|d|x|b|i|m]\n\t\taccess_atribute = [a|r|o|c]\n\t\tattributes = type_attribute[access_atribute]\n\t\tentry = variable_name[:attributes]\n\t\tlist = entry[,list]\n\n\tThe type attributes are:\n\t\ts - String (default)\n\t\td - Decimal\n\t\tx - Hexadecimal\n\t\tb - Boolean ([1yYtT|0nNfF])\n\t\ti - IP address\n\t\tm - MAC address\n\n\tThe access attributes are:\n\t\ta - Any (default)\n\t\tr - Read-only\n\t\to - Write-once\n\t\tc - Change-default\n\n\t- CONFIG_ENV_FLAGS_LIST_DEFAULT\n\t\tDefine this to a list (string) to define the \".flags\"\n\t\tenvirnoment variable in the default or embedded environment.\n\n\t- CONFIG_ENV_FLAGS_LIST_STATIC\n\t\tDefine this to a list (string) to define validation that\n\t\tshould be done if an entry is not found in the \".flags\"\n\t\tenvironment variable.  To override a setting in the static\n\t\tlist, simply add an entry for the same variable name to the\n\t\t\".flags\" variable.\n\n- CONFIG_ENV_ACCESS_IGNORE_FORCE\n\tIf defined, don't allow the -f switch to env set override variable\n\taccess flags.\n\n- CONFIG_SYS_GENERIC_BOARD\n\tThis selects the architecture-generic board system instead of the\n\tarchitecture-specific board files. It is intended to move boards\n\tto this new framework over time. Defining this will disable the\n\tarch/foo/lib/board.c file and use common/board_f.c and\n\tcommon/board_r.c instead. To use this option your architecture\n\tmust support it (i.e. must define __HAVE_ARCH_GENERIC_BOARD in\n\tits config.mk file). If you find problems enabling this option on\n\tyour board please report the problem and send patches!\n\n- CONFIG_SYS_SYM_OFFSETS\n\tThis is set by architectures that use offsets for link symbols\n\tinstead of absolute values. So bss_start is obtained using an\n\toffset _bss_start_ofs from CONFIG_SYS_TEXT_BASE, rather than\n\tdirectly. You should not need to touch this setting.\n\n- CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC (OMAP only)\n\tThis is set by OMAP boards for the max time that reset should\n\tbe asserted. See doc/README.omap-reset-time for details on how\n\tthe value can be calulated on a given board.\n\nThe following definitions that deal with the placement and management\nof environment data (variable area); in general, we support the\nfollowing configurations:\n\n- CONFIG_BUILD_ENVCRC:\n\n\tBuilds up envcrc with the target environment so that external utils\n\tmay easily extract it and embed it in final U-Boot images.\n\n- CONFIG_ENV_IS_IN_FLASH:\n\n\tDefine this if the environment is in flash memory.\n\n\ta) The environment occupies one whole flash sector, which is\n\t   \"embedded\" in the text segment with the U-Boot code. This\n\t   happens usually with \"bottom boot sector\" or \"top boot\n\t   sector\" type flash chips, which have several smaller\n\t   sectors at the start or the end. For instance, such a\n\t   layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In\n\t   such a case you would place the environment in one of the\n\t   4 kB sectors - with U-Boot code before and after it. With\n\t   \"top boot sector\" type flash chips, you would put the\n\t   environment in one of the last sectors, leaving a gap\n\t   between U-Boot and the environment.\n\n\t- CONFIG_ENV_OFFSET:\n\n\t   Offset of environment data (variable area) to the\n\t   beginning of flash memory; for instance, with bottom boot\n\t   type flash chips the second sector can be used: the offset\n\t   for this sector is given here.\n\n\t   CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.\n\n\t- CONFIG_ENV_ADDR:\n\n\t   This is just another way to specify the start address of\n\t   the flash sector containing the environment (instead of\n\t   CONFIG_ENV_OFFSET).\n\n\t- CONFIG_ENV_SECT_SIZE:\n\n\t   Size of the sector containing the environment.\n\n\n\tb) Sometimes flash chips have few, equal sized, BIG sectors.\n\t   In such a case you don't want to spend a whole sector for\n\t   the environment.\n\n\t- CONFIG_ENV_SIZE:\n\n\t   If you use this in combination with CONFIG_ENV_IS_IN_FLASH\n\t   and CONFIG_ENV_SECT_SIZE, you can specify to use only a part\n\t   of this flash sector for the environment. This saves\n\t   memory for the RAM copy of the environment.\n\n\t   It may also save flash memory if you decide to use this\n\t   when your environment is \"embedded\" within U-Boot code,\n\t   since then the remainder of the flash sector could be used\n\t   for U-Boot code. It should be pointed out that this is\n\t   STRONGLY DISCOURAGED from a robustness point of view:\n\t   updating the environment in flash makes it always\n\t   necessary to erase the WHOLE sector. If something goes\n\t   wrong before the contents has been restored from a copy in\n\t   RAM, your target system will be dead.\n\n\t- CONFIG_ENV_ADDR_REDUND\n\t  CONFIG_ENV_SIZE_REDUND\n\n\t   These settings describe a second storage area used to hold\n\t   a redundant copy of the environment data, so that there is\n\t   a valid backup copy in case there is a power failure during\n\t   a \"saveenv\" operation.\n\nBE CAREFUL! Any changes to the flash layout, and some changes to the\nsource code will make it necessary to adapt \u003cboard\u003e/u-boot.lds*\naccordingly!\n\n\n- CONFIG_ENV_IS_IN_NVRAM:\n\n\tDefine this if you have some non-volatile memory device\n\t(NVRAM, battery buffered SRAM) which you want to use for the\n\tenvironment.\n\n\t- CONFIG_ENV_ADDR:\n\t- CONFIG_ENV_SIZE:\n\n\t  These two #defines are used to determine the memory area you\n\t  want to use for environment. It is assumed that this memory\n\t  can just be read and written to, without any special\n\t  provision.\n\nBE CAREFUL! The first access to the environment happens quite early\nin U-Boot initalization (when we try to get the setting of for the\nconsole baudrate). You *MUST* have mapped your NVRAM area then, or\nU-Boot will hang.\n\nPlease note that even with NVRAM we still use a copy of the\nenvironment in RAM: we could work on NVRAM directly, but we want to\nkeep settings there always unmodified except somebody uses \"saveenv\"\nto save the current settings.\n\n\n- CONFIG_ENV_IS_IN_EEPROM:\n\n\tUse this if you have an EEPROM or similar serial access\n\tdevice and a driver for it.\n\n\t- CONFIG_ENV_OFFSET:\n\t- CONFIG_ENV_SIZE:\n\n\t  These two #defines specify the offset and size of the\n\t  environment area within the total memory of your EEPROM.\n\n\t- CONFIG_SYS_I2C_EEPROM_ADDR:\n\t  If defined, specified the chip address of the EEPROM device.\n\t  The default address is zero.\n\n\t- CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:\n\t  If defined, the number of bits used to address bytes in a\n\t  single page in the EEPROM device.  A 64 byte page, for example\n\t  would require six bits.\n\n\t- CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:\n\t  If defined, the number of milliseconds to delay between\n\t  page writes.\tThe default is zero milliseconds.\n\n\t- CONFIG_SYS_I2C_EEPROM_ADDR_LEN:\n\t  The length in bytes of the EEPROM memory array address.  Note\n\t  that this is NOT the chip address length!\n\n\t- CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:\n\t  EEPROM chips that implement \"address overflow\" are ones\n\t  like Catalyst 24WC04/08/16 which has 9/10/11 bits of\n\t  address and the extra bits end up in the \"chip address\" bit\n\t  slots. This makes a 24WC08 (1Kbyte) chip look like four 256\n\t  byte chips.\n\n\t  Note that we consider the length of the address field to\n\t  still be one byte because the extra address bits are hidden\n\t  in the chip address.\n\n\t- CONFIG_SYS_EEPROM_SIZE:\n\t  The size in bytes of the EEPROM device.\n\n\t- CONFIG_ENV_EEPROM_IS_ON_I2C\n\t  define this, if you have I2C and SPI activated, and your\n\t  EEPROM, which holds the environment, is on the I2C bus.\n\n\t- CONFIG_I2C_ENV_EEPROM_BUS\n\t  if you have an Environment on an EEPROM reached over\n\t  I2C muxes, you can define here, how to reach this\n\t  EEPROM. For example:\n\n\t  #define CONFIG_I2C_ENV_EEPROM_BUS\t  \"pca9547:70:d\\0\"\n\n\t  EEPROM which holds the environment, is reached over\n\t  a pca9547 i2c mux with address 0x70, channel 3.\n\n- CONFIG_ENV_IS_IN_DATAFLASH:\n\n\tDefine this if you have a DataFlash memory device which you\n\twant to use for the environment.\n\n\t- CONFIG_ENV_OFFSET:\n\t- CONFIG_ENV_ADDR:\n\t- CONFIG_ENV_SIZE:\n\n\t  These three #defines specify the offset and size of the\n\t  environment area within the total memory of your DataFlash placed\n\t  at the specified address.\n\n- CONFIG_ENV_IS_IN_REMOTE:\n\n\tDefine this if you have a remote memory space which you\n\twant to use for the local device's environment.\n\n\t- CONFIG_ENV_ADDR:\n\t- CONFIG_ENV_SIZE:\n\n\t  These two #defines specify the address and size of the\n\t  environment area within the remote memory space. The\n\t  local device can get the environment from remote memory\n\t  space by SRIO or PCIE links.\n\nBE CAREFUL! For some special cases, the local device can not use\n\"saveenv\" command. For example, the local device will get the\nenvironment stored in a remote NOR flash by SRIO or PCIE link,\nbut it can not erase, write this NOR flash by SRIO or PCIE interface.\n\n- CONFIG_ENV_IS_IN_NAND:\n\n\tDefine this if you have a NAND device which you want to use\n\tfor the environment.\n\n\t- CONFIG_ENV_OFFSET:\n\t- CONFIG_ENV_SIZE:\n\n\t  These two #defines specify the offset and size of the environment\n\t  area within the first NAND device.  CONFIG_ENV_OFFSET must be\n\t  aligned to an erase block boundary.\n\n\t- CONFIG_ENV_OFFSET_REDUND (optional):\n\n\t  This setting describes a second storage area of CONFIG_ENV_SIZE\n\t  size used to hold a redundant copy of the environment data, so\n\t  that there is a valid backup copy in case there is a power failure\n\t  during a \"saveenv\" operation.\t CONFIG_ENV_OFFSET_RENDUND must be\n\t  aligned to an erase block boundary.\n\n\t- CONFIG_ENV_RANGE (optional):\n\n\t  Specifies the length of the region in which the environment\n\t  can be written.  This should be a multiple of the NAND device's\n\t  block size.  Specifying a range with more erase blocks than\n\t  are needed to hold CONFIG_ENV_SIZE allows bad blocks within\n\t  the range to be avoided.\n\n\t- CONFIG_ENV_OFFSET_OOB (optional):\n\n\t  Enables support for dynamically retrieving the offset of the\n\t  environment from block zero's out-of-band data.  The\n\t  \"nand env.oob\" command can be used to record this offset.\n\t  Currently, CONFIG_ENV_OFFSET_REDUND is not supported when\n\t  using CONFIG_ENV_OFFSET_OOB.\n\n- CONFIG_NAND_ENV_DST\n\n\tDefines address in RAM to which the nand_spl code should copy the\n\tenvironment. If redundant environment is used, it will be copied to\n\tCONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.\n\n- CONFIG_ENV_IS_IN_UBI:\n\n\tDefine this if you have an UBI volume that you want to use for the\n\tenvironment.  This has the benefit of wear-leveling the environment\n\taccesses, which is important on NAND.\n\n\t- CONFIG_ENV_UBI_PART:\n\n\t  Define this to a string that is the mtd partition containing the UBI.\n\n\t- CONFIG_ENV_UBI_VOLUME:\n\n\t  Define this to the name of the volume that you want to store the\n\t  environment in.\n\n\t- CONFIG_ENV_UBI_VOLUME_REDUND:\n\n\t  Define this to the name of another volume to store a second copy of\n\t  the environment in.  This will enable redundant environments in UBI.\n\t  It is assumed that both volumes are in the same MTD partition.\n\n\t- CONFIG_UBI_SILENCE_MSG\n\t- CONFIG_UBIFS_SILENCE_MSG\n\n\t  You will probably want to define these to avoid a really noisy system\n\t  when storing the env in UBI.\n\n- CONFIG_ENV_IS_IN_MMC:\n\n\tDefine this if you have an MMC device which you want to use for the\n\tenvironment.\n\n\t- CONFIG_SYS_MMC_ENV_DEV:\n\n\t  Specifies which MMC device the environment is stored in.\n\n\t- CONFIG_SYS_MMC_ENV_PART (optional):\n\n\t  Specifies which MMC partition the environment is stored in. If not\n\t  set, defaults to partition 0, the user area. Common values might be\n\t  1 (first MMC boot partition), 2 (second MMC boot partition).\n\n\t- CONFIG_ENV_OFFSET:\n\t- CONFIG_ENV_SIZE:\n\n\t  These two #defines specify the offset and size of the environment\n\t  area within the specified MMC device.\n\n\t  If offset is positive (the usual case), it is treated as relative to\n\t  the start of the MMC partition. If offset is negative, it is treated\n\t  as relative to the end of the MMC partition. This can be useful if\n\t  your board may be fitted with different MMC devices, which have\n\t  different sizes for the MMC partitions, and you always want the\n\t  environment placed at the very end of the partition, to leave the\n\t  maximum possible space before it, to store other data.\n\n\t  These two values are in units of bytes, but must be aligned to an\n\t  MMC sector boundary.\n\n\t- CONFIG_ENV_OFFSET_REDUND (optional):\n\n\t  Specifies a second storage area, of CONFIG_ENV_SIZE size, used to\n\t  hold a redundant copy of the environment data. This provides a\n\t  valid backup copy in case the other copy is corrupted, e.g. due\n\t  to a power failure during a \"saveenv\" operation.\n\n\t  This value may also be positive or negative; this is handled in the\n\t  same way as CONFIG_ENV_OFFSET.\n\n\t  This value is also in units of bytes, but must also be aligned to\n\t  an MMC sector boundary.\n\n\t- CONFIG_ENV_SIZE_REDUND (optional):\n\n\t  This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is\n\t  set. If this value is set, it must be set to the same value as\n\t  CONFIG_ENV_SIZE.\n\n- CONFIG_SYS_SPI_INIT_OFFSET\n\n\tDefines offset to the initial SPI buffer area in DPRAM. The\n\tarea is used at an early stage (ROM part) if the environment\n\tis configured to reside in the SPI EEPROM: We need a 520 byte\n\tscratch DPRAM area. It is used between the two initialization\n\tcalls (spi_init_f() and spi_init_r()). A value of 0xB00 seems\n\tto be a good choice since it makes it far enough from the\n\tstart of the data area as well as from the stack pointer.\n\nPlease note that the environment is read-only until the monitor\nhas been relocated to RAM and a RAM copy of the environment has been\ncreated; also, when using EEPROM you will have to use getenv_f()\nuntil then to read environment variables.\n\nThe environment is protected by a CRC32 checksum. Before the monitor\nis relocated into RAM, as a result of a bad CRC you will be working\nwith the compiled-in default environment - *silently*!!! [This is\nnecessary, because the first environment variable we need is the\n\"baudrate\" setting for the console - if we have a bad CRC, we don't\nhave any device yet where we could complain.]\n\nNote: once the monitor has been relocated, then it will complain if\nthe default environment is used; a new CRC is computed as soon as you\nuse the \"saveenv\" command to store a valid environment.\n\n- CONFIG_SYS_FAULT_ECHO_LINK_DOWN:\n\t\tEcho the inverted Ethernet link state to the fault LED.\n\n\t\tNote: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR\n\t\t      also needs to be defined.\n\n- CONFIG_SYS_FAULT_MII_ADDR:\n\t\tMII address of the PHY to check for the Ethernet link state.\n\n- CONFIG_NS16550_MIN_FUNCTIONS:\n\t\tDefine this if you desire to only have use of the NS16550_init\n\t\tand NS16550_putc functions for the serial driver located at\n\t\tdrivers/serial/ns16550.c.  This option is useful for saving\n\t\tspace for already greatly restricted images, including but not\n\t\tlimited to NAND_SPL configurations.\n\n- CONFIG_DISPLAY_BOARDINFO\n\t\tDisplay information about the board that U-Boot is running on\n\t\twhen U-Boot starts up. The board function checkboard() is called\n\t\tto do this.\n\n- CONFIG_DISPLAY_BOARDINFO_LATE\n\t\tSimilar to the previous option, but display this information\n\t\tlater, once stdio is running and output goes to the LCD, if\n\t\tpresent.\n\nLow Level (hardware related) configuration options:\n---------------------------------------------------\n\n- CONFIG_SYS_CACHELINE_SIZE:\n\t\tCache Line Size of the CPU.\n\n- CONFIG_SYS_DEFAULT_IMMR:\n\t\tDefault address of the IMMR after system reset.\n\n\t\tNeeded on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,\n\t\tand RPXsuper) to be able to adjust the position of\n\t\tthe IMMR register after a reset.\n\n- CONFIG_SYS_CCSRBAR_DEFAULT:\n\t\tDefault (power-on reset) physical address of CCSR on Freescale\n\t\tPowerPC SOCs.\n\n- CONFIG_SYS_CCSRBAR:\n\t\tVirtual address of CCSR.  On a 32-bit build, this is typically\n\t\tthe same value as CONFIG_SYS_CCSRBAR_DEFAULT.\n\n\t\tCONFIG_SYS_DEFAULT_IMMR must also be set to this value,\n\t\tfor cross-platform code that uses that macro instead.\n\n- CONFIG_SYS_CCSRBAR_PHYS:\n\t\tPhysical address of CCSR.  CCSR can be relocated to a new\n\t\tphysical address, if desired.  In this case, this macro should\n\t\tbe set to that address.\t Otherwise, it should be set to the\n\t\tsame value as CONFIG_SYS_CCSRBAR_DEFAULT.  For example, CCSR\n\t\tis typically relocated on 36-bit builds.  It is recommended\n\t\tthat this macro be defined via the _HIGH and _LOW macros:\n\n\t\t#define CONFIG_SYS_CCSRBAR_PHYS ((CONFIG_SYS_CCSRBAR_PHYS_HIGH\n\t\t\t* 1ull) \u003c\u003c 32 | CONFIG_SYS_CCSRBAR_PHYS_LOW)\n\n- CONFIG_SYS_CCSRBAR_PHYS_HIGH:\n\t\tBits 33-36 of CONFIG_SYS_CCSRBAR_PHYS.\tThis value is typically\n\t\teither 0 (32-bit build) or 0xF (36-bit build).\tThis macro is\n\t\tused in assembly code, so it must not contain typecasts or\n\t\tinteger size suffixes (e.g. \"ULL\").\n\n- CONFIG_SYS_CCSRBAR_PHYS_LOW:\n\t\tLower 32-bits of CONFIG_SYS_CCSRBAR_PHYS.  This macro is\n\t\tused in assembly code, so it must not contain typecasts or\n\t\tinteger size suffixes (e.g. \"ULL\").\n\n- CONFIG_SYS_CCSR_DO_NOT_RELOCATE:\n\t\tIf this macro is defined, then CONFIG_SYS_CCSRBAR_PHYS will be\n\t\tforced to a value that ensures that CCSR is not relocated.\n\n- Floppy Disk Support:\n\t\tCONFIG_SYS_FDC_DRIVE_NUMBER\n\n\t\tthe default drive number (default value 0)\n\n\t\tCONFIG_SYS_ISA_IO_STRIDE\n\n\t\tdefines the spacing between FDC chipset registers\n\t\t(default value 1)\n\n\t\tCONFIG_SYS_ISA_IO_OFFSET\n\n\t\tdefines the offset of register from address. It\n\t\tdepends on which part of the data bus is connected to\n\t\tthe FDC chipset. (default value 0)\n\n\t\tIf CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and\n\t\tCONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their\n\t\tdefault value.\n\n\t\tif CONFIG_SYS_FDC_HW_INIT is defined, then the function\n\t\tfdc_hw_init() is called at the beginning of the FDC\n\t\tsetup. fdc_hw_init() must be provided by the board\n\t\tsource code. It is used to make hardware dependant\n\t\tinitializations.\n\n- CONFIG_IDE_AHB:\n\t\tMost IDE controllers were designed to be connected with PCI\n\t\tinterface. Only few of them were designed for AHB interface.\n\t\tWhen software is doing ATA command and data transfer to\n\t\tIDE devices through IDE-AHB controller, some additional\n\t\tregisters accessing to these kind of IDE-AHB controller\n\t\tis requierd.\n\n- CONFIG_SYS_IMMR:\tPhysical address of the Internal Memory.\n\t\tDO NOT CHANGE unless you know exactly what you're\n\t\tdoing! (11-4) [MPC8xx/82xx systems only]\n\n- CONFIG_SYS_INIT_RAM_ADDR:\n\n\t\tStart address of memory area that can be used for\n\t\tinitial data and stack; please note that this must be\n\t\twritable memory that is working WITHOUT special\n\t\tinitialization, i. e. you CANNOT use normal RAM which\n\t\twill become available only after programming the\n\t\tmemory controller and running certain initialization\n\t\tsequences.\n\n\t\tU-Boot uses the following memory types:\n\t\t- MPC8xx and MPC8260: IMMR (internal memory of the CPU)\n\t\t- MPC824X: data cache\n\t\t- PPC4xx:  data cache\n\n- CONFIG_SYS_GBL_DATA_OFFSET:\n\n\t\tOffset of the initial data structure in the memory\n\t\tarea defined by CONFIG_SYS_INIT_RAM_ADDR. Usually\n\t\tCONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial\n\t\tdata is located at the end of the available space\n\t\t(sometimes written as (CONFIG_SYS_INIT_RAM_SIZE -\n\t\tCONFIG_SYS_INIT_DATA_SIZE), and the initial stack is just\n\t\tbelow that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +\n\t\tCONFIG_SYS_GBL_DATA_OFFSET) downward.\n\n\tNote:\n\t\tOn the MPC824X (or other systems that use the data\n\t\tcache for initial memory) the address chosen for\n\t\tCONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must\n\t\tpoint to an otherwise UNUSED address space between\n\t\tthe top of RAM and the start of the PCI space.\n\n- CONFIG_SYS_SIUMCR:\tSIU Module Configuration (11-6)\n\n- CONFIG_SYS_SYPCR:\tSystem Protection Control (11-9)\n\n- CONFIG_SYS_TBSCR:\tTime Base Status and Control (11-26)\n\n- CONFIG_SYS_PISCR:\tPeriodic Interrupt Status and Control (11-31)\n\n- CONFIG_SYS_PLPRCR:\tPLL, Low-Power, and Reset Control Register (15-30)\n\n- CONFIG_SYS_SCCR:\tSystem Clock and reset Control Register (15-27)\n\n- CONFIG_SYS_OR_TIMING_SDRAM:\n\t\tSDRAM timing\n\n- CONFIG_SYS_MAMR_PTA:\n\t\tperiodic timer for refresh\n\n- CONFIG_SYS_DER:\tDebug Event Register (37-47)\n\n- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,\n  CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,\n  CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,\n  CONFIG_SYS_BR1_PRELIM:\n\t\tMemory Controller Definitions: BR0/1 and OR0/1 (FLASH)\n\n- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,\n  CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,\n  CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:\n\t\tMemory Controller Definitions: BR2/3 and OR2/3 (SDRAM)\n\n- CONFIG_SYS_MAMR_PTA, CONFIG_SYS_MPTPR_2BK_4K, CONFIG_SYS_MPTPR_1BK_4K, CONFIG_SYS_MPTPR_2BK_8K,\n  CONFIG_SYS_MPTPR_1BK_8K, CONFIG_SYS_MAMR_8COL, CONFIG_SYS_MAMR_9COL:\n\t\tMachine Mode Register and Memory Periodic Timer\n\t\tPrescaler definitions (SDRAM timing)\n\n- CONFIG_SYS_I2C_UCODE_PATCH, CONFIG_SYS_I2C_DPMEM_OFFSET [0x1FC0]:\n\t\tenable I2C microcode relocation patch (MPC8xx);\n\t\tdefine relocation offset in DPRAM [DSP2]\n\n- CONFIG_SYS_SMC_UCODE_PATCH, CONFIG_SYS_SMC_DPMEM_OFFSET [0x1FC0]:\n\t\tenable SMC microcode relocation patch (MPC8xx);\n\t\tdefine relocation offset in DPRAM [SMC1]\n\n- CONFIG_SYS_SPI_UCODE_PATCH, CONFIG_SYS_SPI_DPMEM_OFFSET [0x1FC0]:\n\t\tenable SPI microcode relocation patch (MPC8xx);\n\t\tdefine relocation offset in DPRAM [SCC4]\n\n- CONFIG_SYS_USE_OSCCLK:\n\t\tUse OSCM clock mode on MBX8xx board. Be careful,\n\t\twrong setting might damage your board. Read\n\t\tdoc/README.MBX before setting this variable!\n\n- CONFIG_SYS_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)\n\t\tOffset of the bootmode word in DPRAM used by post\n\t\t(Power On Self Tests). This definition overrides\n\t\t#define'd default value in commproc.h resp.\n\t\tcpm_8260.h.\n\n- CONFIG_SYS_PCI_SLV_MEM_LOCAL, CONFIG_SYS_PCI_SLV_MEM_BUS, CONFIG_SYS_PICMR0_MASK_ATTRIB,\n  CONFIG_SYS_PCI_MSTR0_LOCAL, CONFIG_SYS_PCIMSK0_MASK, CONFIG_SYS_PCI_MSTR1_LOCAL,\n  CONFIG_SYS_PCIMSK1_MASK, CONFIG_SYS_PCI_MSTR_MEM_LOCAL, CONFIG_SYS_PCI_MSTR_MEM_BUS,\n  CONFIG_SYS_CPU_PCI_MEM_START, CONFIG_SYS_PCI_MSTR_MEM_SIZE, CONFIG_SYS_POCMR0_MASK_ATTRIB,\n  CONFIG_SYS_PCI_MSTR_MEMIO_LOCAL, CONFIG_SYS_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,\n  CONFIG_SYS_PCI_MSTR_MEMIO_SIZE, CONFIG_SYS_POCMR1_MASK_ATTRIB, CONFIG_SYS_PCI_MSTR_IO_LOCAL,\n  CONFIG_SYS_PCI_MSTR_IO_BUS, CONFIG_SYS_CPU_PCI_IO_START, CONFIG_SYS_PCI_MSTR_IO_SIZE,\n  CONFIG_SYS_POCMR2_MASK_ATTRIB: (MPC826x only)\n\t\tOverrides the default PCI memory map in arch/powerpc/cpu/mpc8260/pci.c if set.\n\n- CONFIG_PCI_DISABLE_PCIE:\n\t\tDisable PCI-Express on systems where it is supported but not\n\t\trequired.\n\n- CONFIG_PCI_ENUM_ONLY\n\t\tOnly scan through and get the devices on the busses.\n\t\tDon't do any setup work, presumably because someone or\n\t\tsomething has already done it, and we don't need to do it\n\t\ta second time.\tUseful for platforms that are pre-booted\n\t\tby coreboot or similar.\n\n- CONFIG_PCI_INDIRECT_BRIDGE:\n\t\tEnable support for indirect PCI bridges.\n\n- CONFIG_SYS_SRIO:\n\t\tChip has SRIO or not\n\n- CONFIG_SRIO1:\n\t\tBoard has SRIO 1 port available\n\n- CONFIG_SRIO2:\n\t\tBoard has SRIO 2 port available\n\n- CONFIG_SRIO_PCIE_BOOT_MASTER\n\t\tBoard can support master function for Boot from SRIO and PCIE\n\n- CONFIG_SYS_SRIOn_MEM_VIRT:\n\t\tVirtual Address of SRIO port 'n' memory region\n\n- CONFIG_SYS_SRIOn_MEM_PHYS:\n\t\tPhysical Address of SRIO port 'n' memory region\n\n- CONFIG_SYS_SRIOn_MEM_SIZE:\n\t\tSize of SRIO port 'n' memory region\n\n- CONFIG_SYS_NAND_BUSWIDTH_16BIT\n\t\tDefined to tell the NAND controller that the NAND chip is using\n\t\ta 16 bit bus.\n\t\tNot all NAND drivers use this symbol.\n\t\tExample of drivers that use it:\n\t\t- drivers/mtd/nand/ndfc.c\n\t\t- drivers/mtd/nand/mxc_nand.c\n\n- CONFIG_SYS_NDFC_EBC0_CFG\n\t\tSets the EBC0_CFG register for the NDFC. If not defined\n\t\ta default value will be used.\n\n- CONFIG_SPD_EEPROM\n\t\tGet DDR timing information from an I2C EEPROM. Common\n\t\twith pluggable memory modules such as SODIMMs\n\n  SPD_EEPROM_ADDRESS\n\t\tI2C address of the SPD EEPROM\n\n- CONFIG_SYS_SPD_BUS_NUM\n\t\tIf SPD EEPROM is on an I2C bus other than the first\n\t\tone, specify here. Note that the value must resolve\n\t\tto something your driver can deal with.\n\n- CONFIG_SYS_DDR_RAW_TIMING\n\t\tGet DDR timing information from other than SPD. Common with\n\t\tsoldered DDR chips onboard without SPD. DDR raw timing\n\t\tparameters are extracted from datasheet and hard-coded into\n\t\theader files or board specific files.\n\n- CONFIG_FSL_DDR_INTERACTIVE\n\t\tEnable interactive DDR debugging. See doc/README.fsl-ddr.\n\n- CONFIG_SYS_83XX_DDR_USES_CS0\n\t\tOnly for 83xx systems. If specified, then DDR should\n\t\tbe configured using CS0 and CS1 instead of CS2 and CS3.\n\n- CONFIG_ETHER_ON_FEC[12]\n\t\tDefine to enable FEC[12] on a 8xx series processor.\n\n- CONFIG_FEC[12]_PHY\n\t\tDefine to the hardcoded PHY address which corresponds\n\t\tto the given FEC; i. e.\n\t\t\t#define CONFIG_FEC1_PHY 4\n\t\tmeans that the PHY with address 4 is connected to FEC1\n\n\t\tWhen set to -1, means to probe for first available.\n\n- CONFIG_FEC[12]_PHY_NORXERR\n\t\tThe PHY does not have a RXERR line (RMII only).\n\t\t(so program the FEC to ignore it).\n\n- CONFIG_RMII\n\t\tEnable RMII mode for all FECs.\n\t\tNote that this is a global option, we can't\n\t\thave one FEC in standard MII mode and another in RMII mode.\n\n- CONFIG_CRC32_VERIFY\n\t\tAdd a verify option to the crc32 command.\n\t\tThe syntax is:\n\n\t\t=\u003e crc32 -v \u003caddress\u003e \u003ccount\u003e \u003ccrc32\u003e\n\n\t\tWhere address/count indicate a memory area\n\t\tand crc32 is the correct crc32 which the\n\t\tarea should have.\n\n- CONFIG_LOOPW\n\t\tAdd the \"loopw\" memory command. This only takes effect if\n\t\tthe memory commands are activated globally (CONFIG_CMD_MEM).\n\n- CONFIG_MX_CYCLIC\n\t\tAdd the \"mdc\" and \"mwc\" memory commands. These are cyclic\n\t\t\"md/mw\" commands.\n\t\tExamples:\n\n\t\t=\u003e mdc.b 10 4 500\n\t\tThis command will print 4 bytes (10,11,12,13) each 500 ms.\n\n\t\t=\u003e mwc.l 100 12345678 10\n\t\tThis command will write 12345678 to address 100 all 10 ms.\n\n\t\tThis only takes effect if the memory commands are activated\n\t\tglobally (CONFIG_CMD_MEM).\n\n- CONFIG_SKIP_LOWLEVEL_INIT\n\t\t[ARM, NDS32, MIPS only] If this variable is defined, then certain\n\t\tlow level initializations (like setting up the memory\n\t\tcontroller) are omitted and/or U-Boot does not\n\t\trelocate itself into RAM.\n\n\t\tNormally this variable MUST NOT be defined. The only\n\t\texception is when U-Boot is loaded (to RAM) by some\n\t\tother boot loader or by a debugger which performs\n\t\tthese initializations itself.\n\n- CONFIG_SPL_BUILD\n\t\tModifies the behaviour of start.S when compiling a loader\n\t\tthat is executed before the actual U-Boot. E.g. when\n\t\tcompiling a NAND SPL.\n\n- CONFIG_SYS_MPC85XX_NO_RESETVEC\n\t\tOnly for 85xx systems. If this variable is specified, the section\n\t\t.resetvec is not kept and the section .bootpg is placed in the\n\t\tprevious 4k of the .text section.\n\n- CONFIG_ARCH_MAP_SYSMEM\n\t\tGenerally U-Boot (and in particular the md command) uses\n\t\teffective address. It is therefore not necessary to regard\n\t\tU-Boot address as virtual addresses that need to be translated\n\t\tto physical addresses. However, sandbox requires this, since\n\t\tit maintains its own little RAM buffer which contains all\n\t\taddressable memory. This option causes some memory accesses\n\t\tto be mapped through map_sysmem() / unmap_sysmem().\n\n- CONFIG_USE_ARCH_MEMCPY\n  CONFIG_USE_ARCH_MEMSET\n\t\tIf these options are used a optimized version of memcpy/memset will\n\t\tbe used if available. These functions may be faster under some\n\t\tconditions but may increase the binary size.\n\n- CONFIG_X86_RESET_VECTOR\n\t\tIf defined, the x86 reset vector code is included. This is not\n\t\tneeded when U-Boot is running from Coreboot.\n\n- CONFIG_SYS_MPUCLK\n\t\tDefines the MPU clock speed (in MHz).\n\n\t\tNOTE : currently only supported on AM335x platforms.\n\nFreescale QE/FMAN Firmware Support:\n-----------------------------------\n\nThe Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the\nloading of \"firmware\", which is encoded in the QE firmware binary format.\nThis firmware often needs to be loaded during U-Boot booting, so macros\nare used to identify the storage device (NOR flash, SPI, etc) and the address\nwithin that device.\n\n- CONFIG_SYS_QE_FMAN_FW_ADDR\n\tThe address in the storage device where the firmware is located.  The\n\tmeaning of this address depends on which CONFIG_SYS_QE_FW_IN_xxx macro\n\tis also specified.\n\n- CONFIG_SYS_QE_FMAN_FW_LENGTH\n\tThe maximum possible size of the firmware.  The firmware binary format\n\thas a field that specifies the actual size of the firmware, but it\n\tmight not be possible to read any part of the firmware unless some\n\tlocal storage is allocated to hold the entire firmware first.\n\n- CONFIG_SYS_QE_FMAN_FW_IN_NOR\n\tSpecifies that QE/FMAN firmware is located in NOR flash, mapped as\n\tnormal addressable memory via the LBC.  CONFIG_SYS_FMAN_FW_ADDR is the\n\tvirtual address in NOR flash.\n\n- CONFIG_SYS_QE_FMAN_FW_IN_NAND\n\tSpecifies that QE/FMAN firmware is located in NAND flash.\n\tCONFIG_SYS_FMAN_FW_ADDR is the offset within NAND flash.\n\n- CONFIG_SYS_QE_FMAN_FW_IN_MMC\n\tSpecifies that QE/FMAN firmware is located on the primary SD/MMC\n\tdevice.  CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device.\n\n- CONFIG_SYS_QE_FMAN_FW_IN_SPIFLASH\n\tSpecifies that QE/FMAN firmware is located on the primary SPI\n\tdevice.  CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device.\n\n- CONFIG_SYS_QE_FMAN_FW_IN_REMOTE\n\tSpecifies that QE/FMAN firmware is located in the remote (master)\n\tmemory space.\tCONFIG_SYS_FMAN_FW_ADDR is a virtual address which\n\tcan be mapped from slave TLB-\u003eslave LAW-\u003eslave SRIO or PCIE outbound\n\twindow-\u003emaster inbound window-\u003emaster LAW-\u003ethe ucode address in\n\tmaster's memory space.\n\nBuilding the Software:\n======================\n\nBuilding U-Boot has been tested in several native build environments\nand in many different cross environments. Of course we cannot support\nall possibly existing versions of cross development tools in all\n(potentially obsolete) versions. In case of tool chain problems we\nrecommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK)\nwhich is extensively used to build and test U-Boot.\n\nIf you are not using a native environment, it is assumed that you\nhave GNU cross compiling tools available in your path. In this case,\nyou must set the environment variable CROSS_COMPILE in your shell.\nNote that no changes to the Makefile or any other source files are\nnecessary. For example using the ELDK on a 4xx CPU, please enter:\n\n\t$ CROSS_COMPILE=ppc_4xx-\n\t$ export CROSS_COMPILE\n\nNote: If you wish to generate Windows versions of the utilities in\n      the tools directory you can use the MinGW toolchain\n      (http://www.mingw.org).  Set your HOST tools to the MinGW\n      toolchain and execute 'make tools'.  For example:\n\n       $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools\n\n      Binaries such as tools/mkimage.exe will be created which can\n      be executed on computers running Windows.\n\nU-Boot is intended to be simple to build. After installing the\nsources you must configure U-Boot for one specific board type. This\nis done by typing:\n\n\tmake NAME_config\n\nwhere \"NAME_config\" is the name of one of the existing configu-\nrations; see boards.cfg for supported names.\n\nNote: for some board special configuration names may exist; check if\n      additional information is available from the board vendor; for\n      instance, the TQM823L systems are available without (standard)\n      or with LCD support. You can select such additional \"features\"\n      when choosing the configuration, i. e.\n\n      make TQM823L_config\n\t- will configure for a plain TQM823L, i. e. no LCD support\n\n      make TQM823L_LCD_config\n\t- will configure for a TQM823L with U-Boot console on LCD\n\n      etc.\n\n\nFinally, type \"make all\", and you should get some working U-Boot\nimages ready for download to / installation on your system:\n\n- \"u-boot.bin\" is a raw binary image\n- \"u-boot\" is an image in ELF binary format\n- \"u-boot.srec\" is in Motorola S-Record format\n\nBy default the build is performed locally and the objects are saved\nin the source directory. One of the two methods can be used to change\nthis behavior and build U-Boot to some external directory:\n\n1. Add O= to the make command line invocations:\n\n\tmake O=/tmp/build distclean\n\tmake O=/tmp/build NAME_config\n\tmake O=/tmp/build all\n\n2. Set environment variable BUILD_DIR to point to the desired location:\n\n\texport BUILD_DIR=/tmp/build\n\tmake distclean\n\tmake NAME_config\n\tmake all\n\nNote that the command line \"O=\" setting overrides the BUILD_DIR environment\nvariable.\n\n\nPlease be aware that the Makefiles assume you are using GNU make, so\nfor instance on NetBSD you might need to use \"gmake\" instead of\nnative \"make\".\n\n\nIf the system board that you have is not listed, then you will need\nto port U-Boot to your hardware platform. To do this, follow these\nsteps:\n\n1.  Add a new configuration option for your board to the toplevel\n    \"boards.cfg\" file, using the existing entries as examples.\n    Follow the instructions there to keep the boards in order.\n2.  Create a new directory to hold your board specific code. Add any\n    files you need. In your board directory, you will need at least\n    the \"Makefile\", a \"\u003cboard\u003e.c\", \"flash.c\" and \"u-boot.lds\".\n3.  Create a new configuration file \"include/configs/\u003cboard\u003e.h\" for\n    your board\n3.  If you're porting U-Boot to a new CPU, then also create a new\n    directory to hold your CPU specific code. Add any files you need.\n4.  Run \"make \u003cboard\u003e_config\" with your new name.\n5.  Type \"make\", and you should get a working \"u-boot.srec\" file\n    to be installed on your target system.\n6.  Debug and solve any problems that might arise.\n    [Of course, this last step is much harder than it sounds.]\n\n\nTesting of U-Boot Modifications, Ports to New Hardware, etc.:\n==============================================================\n\nIf you have modified U-Boot sources (for instance added a new board\nor support for new devices, a new CPU, etc.) you are expected to\nprovide feedback to the other developers. The feedback normally takes\nthe form of a \"patch\", i. e. a context diff against a certain (latest\nofficial or latest in the git repository) version of U-Boot sources.\n\nBut before you submit such a patch, please verify that your modifi-\ncation did not break existing code. At least make sure that *ALL* of\nthe supported boards compile WITHOUT ANY compiler warnings. To do so,\njust run the \"MAKEALL\" script, which will configure and build U-Boot\nfor ALL supported system. Be warned, this will take a while. You can\nselect which (cross) compiler to use by passing a `CROSS_COMPILE'\nenvironment variable to the script, i. e. to use the ELDK cross tools\nyou can type\n\n\tCROSS_COMPILE=ppc_8xx- MAKEALL\n\nor to build on a native PowerPC system you can type\n\n\tCROSS_COMPILE=' ' MAKEALL\n\nWhen using the MAKEALL script, the default behaviour is to build\nU-Boot in the source directory. This location can be changed by\nsetting the BUILD_DIR environment variable. Also, for each target\nbuilt, the MAKEALL script saves two log files (\u003ctarget\u003e.ERR and\n\u003ctarget\u003e.MAKEALL) in the \u003csource dir\u003e/LOG directory. This default\nlocation can be changed by setting the MAKEALL_LOGDIR environment\nvariable. For example:\n\n\texport BUILD_DIR=/tmp/build\n\texport MAKEALL_LOGDIR=/tmp/log\n\tCROSS_COMPILE=ppc_8xx- MAKEALL\n\nWith the above settings build objects are saved in the /tmp/build,\nlog files are saved in the /tmp/log and the source tree remains clean\nduring the whole build process.\n\n\nSee also \"U-Boot Porting Guide\" below.\n\n\nMonitor Commands - Overview:\n============================\n\ngo\t- start application at address 'addr'\nrun\t- run commands in an environment variable\nbootm\t- boot application image from memory\nbootp\t- boot image via network using BootP/TFTP protocol\nbootz   - boot zImage from memory\ntftpboot- boot image via network using TFTP protocol\n\t       and env variables \"ipaddr\" and \"serverip\"\n\t       (and eventually \"gatewayip\")\ntftpput - upload a file via network using TFTP protocol\nrarpboot- boot image via network using RARP/TFTP protocol\ndiskboot- boot from IDE devicebootd   - boot default, i.e., run 'bootcmd'\nloads\t- load S-Record file over serial line\nloadb\t- load binary file over serial line (kermit mode)\nmd\t- memory display\nmm\t- memory modify (auto-incrementing)\nnm\t- memory modify (constant address)\nmw\t- memory write (fill)\ncp\t- memory copy\ncmp\t- memory compare\ncrc32\t- checksum calculation\ni2c\t- I2C sub-system\nsspi\t- SPI utility commands\nbase\t- print or set address offset\nprintenv- print environment variables\nsetenv\t- set environment variables\nsaveenv - save environment variables to persistent storage\nprotect - enable or disable FLASH write protection\nerase\t- erase FLASH memory\nflinfo\t- print FLASH memory information\nnand\t- NAND memory operations (see doc/README.nand)\nbdinfo\t- print Board Info structure\niminfo\t- print header information for application image\nconinfo - print console devices and informations\nide\t- IDE sub-system\nloop\t- infinite loop on address range\nloopw\t- infinite write loop on address range\nmtest\t- simple RAM test\nicache\t- enable or disable instruction cache\ndcache\t- enable or disable data cache\nreset\t- Perform RESET of the CPU\necho\t- echo args to console\nversion - print monitor version\nhelp\t- print online help\n?\t- alias for 'help'\n\n\nMonitor Commands - Detailed Description:\n========================================\n\nTODO.\n\nFor now: just type \"help \u003ccommand\u003e\".\n\n\nEnvironment Variables:\n======================\n\nU-Boot supports user configuration using Environment Variables which\ncan be made persistent by saving to Flash memory.\n\nEnvironment Variables are set using \"setenv\", printed using\n\"printenv\", and saved to Flash using \"saveenv\". Using \"setenv\"\nwithout a value can be used to delete a variable from the\nenvironment. As long as you don't save the environment you are\nworking with an in-memory copy. In case the Flash area containing the\nenvironment is erased by accident, a default environment is provided.\n\nSome configuration options can be set using Environment Variables.\n\nList of environment variables (most likely not complete):\n\n  baudrate\t- see CONFIG_BAUDRATE\n\n  bootdelay\t- see CONFIG_BOOTDELAY\n\n  bootcmd\t- see CONFIG_BOOTCOMMAND\n\n  bootargs\t- Boot arguments when booting an RTOS image\n\n  bootfile\t- Name of the image to load with TFTP\n\n  bootm_low\t- Memory range available for image processing in the bootm\n\t\t  command can be restricted. This variable is given as\n\t\t  a hexadecimal number and defines lowest address allowed\n\t\t  for use by the bootm command. See also \"bootm_size\"\n\t\t  environment variable. Address defined by \"bootm_low\" is\n\t\t  also the base of the initial memory mapping for the Linux\n\t\t  kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and\n\t\t  bootm_mapsize.\n\n  bootm_mapsize - Size of the initial memory mapping for the Linux kernel.\n\t\t  This variable is given as a hexadecimal number and it\n\t\t  defines the size of the memory region starting at base\n\t\t  address bootm_low that is accessible by the Linux kernel\n\t\t  during early boot.  If unset, CONFIG_SYS_BOOTMAPSZ is used\n\t\t  as the default value if it is defined, and bootm_size is\n\t\t  used otherwise.\n\n  bootm_size\t- Memory range available for image processing in the bootm\n\t\t  command can be restricted. This variable is given as\n\t\t  a hexadecimal number and defines the size of the region\n\t\t  allowed for use by the bootm command. See also \"bootm_low\"\n\t\t  environment variable.\n\n  updatefile\t- Location of the software update file on a TFTP server, used\n\t\t  by the automatic software update feature. Please refer to\n\t\t  documentation in doc/README.update for more details.\n\n  autoload\t- if set to \"no\" (any string beginning with 'n'),\n\t\t  \"bootp\" will just load perform a lookup of the\n\t\t  configuration from the BOOTP server, but not try to\n\t\t  load any image using TFTP\n\n  autostart\t- if set to \"yes\", an image loaded using the \"bootp\",\n\t\t  \"rarpboot\", \"tftpboot\" or \"diskboot\" commands will\n\t\t  be automatically started (by internally calling\n\t\t  \"bootm\")\n\n\t\t  If set to \"no\", a standalone image passed to the\n\t\t  \"bootm\" command will be copied to the load address\n\t\t  (and eventually uncompressed), but NOT be started.\n\t\t  This can be used to load and uncompress arbitrary\n\t\t  data.\n\n  fdt_high\t- if set this restricts the maximum address that the\n\t\t  flattened device tree will be copied into upon boot.\n\t\t  For example, if you have a system with 1 GB memory\n\t\t  at physical address 0x10000000, while Linux kernel\n\t\t  only recognizes the first 704 MB as low memory, you\n\t\t  may need to set fdt_high as 0x3C000000 to have the\n\t\t  device tree blob be copied to the maximum address\n\t\t  of the 704 MB low memory, so that Linux kernel can\n\t\t  access it during the boot procedure.\n\n\t\t  If this is set to the special value 0xFFFFFFFF then\n\t\t  the fdt will not be copied at all on boot.  For this\n\t\t  to work it must reside in writable memory, have\n\t\t  sufficient padding on the end of it for u-boot to\n\t\t  add the information it needs into it, and the memory\n\t\t  must be accessible by the kernel.\n\n  fdtcontroladdr- if set this is the address of the control flattened\n\t\t  device tree used by U-Boot when CONFIG_OF_CONTROL is\n\t\t  defined.\n\n  i2cfast\t- (PPC405GP|PPC405EP only)\n\t\t  if set to 'y' configures Linux I2C driver for fast\n\t\t  mode (400kHZ). This environment variable is used in\n\t\t  initialization code. So, for changes to be effective\n\t\t  it must be saved and board must be reset.\n\n  initrd_high\t- restrict positioning of initrd images:\n\t\t  If this variable is not set, initrd images will be\n\t\t  copied to the highest possible address in RAM; this\n\t\t  is usually what you want since it allows for\n\t\t  maximum initrd size. If for some reason you want to\n\t\t  make sure that the initrd image is loaded below the\n\t\t  CONFIG_SYS_BOOTMAPSZ limit, you can set this environment\n\t\t  variable to a value of \"no\" or \"off\" or \"0\".\n\t\t  Alternatively, you can set it to a maximum upper\n\t\t  address to use (U-Boot will still check that it\n\t\t  does not overwrite the U-Boot stack and data).\n\n\t\t  For instance, when you have a system with 16 MB\n\t\t  RAM, and want to reserve 4 MB from use by Linux,\n\t\t  you can do this by adding \"mem=12M\" to the value of\n\t\t  the \"bootargs\" variable. However, now you must make\n\t\t  sure that the initrd image is placed in the first\n\t\t  12 MB as well - this can be done with\n\n\t\t  setenv initrd_high 00c00000\n\n\t\t  If you set initrd_high to 0xFFFFFFFF, this is an\n\t\t  indication to U-Boot that all addresses are legal\n\t\t  for the Linux kernel, including addresses in flash\n\t\t  memory. In this case U-Boot will NOT COPY the\n\t\t  ramdisk at all. This may be useful to reduce the\n\t\t  boot time on your system, but requires that this\n\t\t  feature is supported by your Linux kernel.\n\n  ipaddr\t- IP address; needed for tftpboot command\n\n  loadaddr\t- Default load address for commands like \"bootp\",\n\t\t  \"rarpboot\", \"tftpboot\", \"loadb\" or \"diskboot\"\n\n  loads_echo\t- see CONFIG_LOADS_ECHO\n\n  serverip\t- TFTP server IP address; needed for tftpboot command\n\n  bootretry\t- see CONFIG_BOOT_RETRY_TIME\n\n  bootdelaykey\t- see CONFIG_AUTOBOOT_DELAY_STR\n\n  bootstopkey\t- see CONFIG_AUTOBOOT_STOP_STR\n\n  ethprime\t- controls which interface is used first.\n\n  ethact\t- controls which interface is currently active.\n\t\t  For example you can do the following\n\n\t\t  =\u003e setenv ethact FEC\n\t\t  =\u003e ping 192.168.0.1 # traffic sent on FEC\n\t\t  =\u003e setenv ethact SCC\n\t\t  =\u003e ping 10.0.0.1 # traffic sent on SCC\n\n  ethrotate\t- When set to \"no\" U-Boot does not go through all\n\t\t  available network interfaces.\n\t\t  It just stays at the currently selected interface.\n\n  netretry\t- When set to \"no\" each network operation will\n\t\t  either succeed or fail without retrying.\n\t\t  When set to \"once\" the network operation will\n\t\t  fail when all the available network interfaces\n\t\t  are tried once without success.\n\t\t  Useful on scripts which control the retry operation\n\t\t  themselves.\n\n  npe_ucode\t- set load address for the NPE microcode\n\n  tftpsrcport\t- If this is set, the value is used for TFTP's\n\t\t  UDP source port.\n\n  tftpdstport\t- If this is set, the value is used for TFTP's UDP\n\t\t  destination port instead of the Well Know Port 69.\n\n  tftpblocksize - Block size to use for TFTP transfers; if not set,\n\t\t  we use the TFTP server's default block size\n\n  tftptimeout\t- Retransmission timeout for TFTP packets (in milli-\n\t\t  seconds, minimum value is 1000 = 1 second). Defines\n\t\t  when a packet is considered to be lost so it has to\n\t\t  be retransmitted. The default is 5000 = 5 seconds.\n\t\t  Lowering this value may make downloads succeed\n\t\t  faster in networks with high packet loss rates or\n\t\t  with unreliable TFTP servers.\n\n  vlan\t\t- When set to a value \u003c 4095 the traffic over\n\t\t  Ethernet is encapsulated/received over 802.1q\n\t\t  VLAN tagged frames.\n\nThe following image location variables contain the location of images\nused in booting. The \"Image\" column gives the role of the image and is\nnot an environment variable name. The other columns are environment\nvariable names. \"File Name\" gives the name of the file on a TFTP\nserver, \"RAM Address\" gives the location in RAM the image will be\nloaded to, and \"Flash Location\" gives the image's address in NOR\nflash or offset in NAND flash.\n\n*Note* - these variables don't have to be defined for all boards, some\nboards currenlty use other variables for these purposes, and some\nboards use these variables for other purposes.\n\nImage\t\t    File Name\t     RAM Address       Flash Location\n-----\t\t    ---------\t     -----------       --------------\nu-boot\t\t    u-boot\t     u-boot_addr_r     u-boot_addr\nLinux kernel\t    bootfile\t     kernel_addr_r     kernel_addr\ndevice tree blob    fdtfile\t     fdt_addr_r\t       fdt_addr\nramdisk\t\t    ramdiskfile\t     ramdisk_addr_r    ramdisk_addr\n\nThe following environment variables may be used and automatically\nupdated by the network boot commands (\"bootp\" and \"rarpboot\"),\ndepending the information provided by your boot server:\n\n  bootfile\t- see above\n  dnsip\t\t- IP address of your Domain Name Server\n  dnsip2\t- IP address of your secondary Domain Name Server\n  gatewayip\t- IP address of the Gateway (Router) to use\n  hostname\t- Target hostname\n  ipaddr\t- see above\n  netmask\t- Subnet Mask\n  rootpath\t- Pathname of the root filesystem on the NFS server\n  serverip\t- see above\n\n\nThere are two special Environment Variables:\n\n  serial#\t- contains hardware identification information such\n\t\t  as type string and/or serial number\n  ethaddr\t- Ethernet address\n\nThese variables can be set only once (usually during manufacturing of\nthe board). U-Boot refuses to delete or overwrite these variables\nonce they have been set once.\n\n\nFurther special Environment Variables:\n\n  ver\t\t- Contains the U-Boot version string as printed\n\t\t  with the \"version\" command. This variable is\n\t\t  readonly (see CONFIG_VERSION_VARIABLE).\n\n\nPlease note that changes to some configuration parameters may take\nonly effect after the next boot (yes, that's just like Windoze :-).\n\n\nCallback functions for environment variables:\n---------------------------------------------\n\nFor some environment variables, the behavior of u-boot needs to change\nwhen their values are changed.  This functionailty allows functions to\nbe associated with arbitrary variables.  On creation, overwrite, or\ndeletion, the callback will provide the opportunity for some side\neffect to happen or for the change to be rejected.\n\nThe callbacks are named and associated with a function using the\nU_BOOT_ENV_CALLBACK macro in your board or driver code.\n\nThese callbacks are associated with variables in one of two ways.  The\nstatic list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC\nin the board configuration to a string that defines a list of\nassociations.  The list must be in the following format:\n\n\tentry = variable_name[:callback_name]\n\tlist = entry[,list]\n\nIf the callback name is not specified, then the callback is deleted.\nSpaces are also allowed anywhere in the list.\n\nCallbacks can also be associated by defining the \".callbacks\" variable\nwith the same list format above.  Any association in \".callbacks\" will\noverride any association in the static list. You can define\nCONFIG_ENV_CALLBACK_LIST_DEFAULT to a list (string) to define the\n\".callbacks\" envirnoment variable in the default or embedded environment.\n\n\nCommand Line Parsing:\n=====================\n\nThere are two different command line parsers available with U-Boot:\nthe old \"simple\" one, and the much more powerful \"hush\" shell:\n\nOld, simple command line parser:\n--------------------------------\n\n- supports environment variables (through setenv / saveenv commands)\n- several commands on one line, separated by ';'\n- variable substitution using \"... ${name} ...\" syntax\n- special characters ('$', ';') can be escaped by prefixing with '\\',\n  for example:\n\tsetenv bootcmd bootm \\${address}\n- You can also escape text by enclosing in single apostrophes, for example:\n\tsetenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'\n\nHush shell:\n-----------\n\n- similar to Bourne shell, with control structures like\n  if...then...else...fi, for...do...done; while...do...done,\n  until...do...done, ...\n- supports environment (\"global\") variables (through setenv / saveenv\n  commands) and local shell variables (through standard shell syntax\n  \"name=value\"); only environment variables can be used with \"run\"\n  command\n\nGeneral rules:\n--------------\n\n(1) If a command line (or an environment variable executed by a \"run\"\n    command) contains several commands separated by semicolon, and\n    one of these commands fails, then the remaining commands will be\n    executed anyway.\n\n(2) If you execute several variables with one call to run (i. e.\n    calling run with a list of variables as arguments), any failing\n    command will cause \"run\" to terminate, i. e. the remaining\n    variables are not executed.\n\nNote for Redundant Ethernet Interfaces:\n=======================================\n\nSome boards come with redundant Ethernet interfaces; U-Boot supports\nsuch configurations and is capable of automatic selection of a\n\"working\" interface when needed. MAC assignment works as follows:\n\nNetwork interfaces are numbered eth0, eth1, eth2, ... Corresponding\nMAC addresses can be stored in the environment as \"ethaddr\" (=\u003eeth0),\n\"eth1addr\" (=\u003eeth1), \"eth2addr\", ...\n\nIf the network interface stores some valid MAC address (for instance\nin SROM), this is used as default address if there is NO correspon-\nding setting in the environment; if the corresponding environment\nvariable is set, this overrides the settings in the card; that means:\n\no If the SROM has a valid MAC address, and there is no address in the\n  environment, the SROM's address is used.\n\no If there is no valid address in the SROM, and a definition in the\n  environment exists, then the value from the environment variable is\n  used.\n\no If both the SROM and the environment contain a MAC address, and\n  both addresses are the same, this MAC address is used.\n\no If both the SROM and the environment contain a MAC address, and the\n  addresses differ, the value from the environment is used and a\n  warning is printed.\n\no If neither SROM nor the environment contain a MAC address, an error\n  is raised.\n\nIf Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses\nwill be programmed into hardware as part of the initialization process.\t This\nmay be skipped by setting the appropriate 'ethmacskip' environment variable.\nThe naming convention is as follows:\n\"ethmacskip\" (=\u003eeth0), \"eth1macskip\" (=\u003eeth1) etc.\n\nImage Formats:\n==============\n\nU-Boot is capable of booting (and performing other auxiliary operations on)\nimages in two formats:\n\nNew uImage format (FIT)\n-----------------------\n\nFlexible and powerful format based on Flattened Image Tree -- FIT (similar\nto Flattened Device Tree). It allows the use of images with multiple\ncomponents (several kernels, ramdisks, etc.), with contents protected by\nSHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.\n\n\nOld uImage format\n-----------------\n\nOld image format is based on binary files which can be basically anything,\npreceded by a special header; see the definitions in include/image.h for\ndetails; basically, the header defines the following image properties:\n\n* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,\n  4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,\n  LynxOS, pSOS, QNX, RTEMS, INTEGRITY;\n  Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,\n  INTEGRITY).\n* Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86,\n  IA64, MIPS, NDS32, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;\n  Currently supported: ARM, AVR32, Intel x86, MIPS, NDS32, Nios II, PowerPC).\n* Compression Type (uncompressed, gzip, bzip2)\n* Load Address\n* Entry Point\n* Image Name\n* Image Timestamp\n\nThe header is marked by a special Magic Number, and both the header\nand the data portions of the image are secured against corruption by\nCRC32 checksums.\n\n\nLinux Support:\n==============\n\nAlthough U-Boot should support any OS or standalone application\neasily, the main focus has always been on Linux during the design of\nU-Boot.\n\nU-Boot includes many features that so far have been part of some\nspecial \"boot loader\" code within the Linux kernel. Also, any\n\"initrd\" images to be used are no longer part of one big Linux image;\ninstead, kernel and \"initrd\" are separate images. This implementation\nserves several purposes:\n\n- the same features can be used for other OS or standalone\n  applications (for instance: using compressed images to reduce the\n  Flash memory footprint)\n\n- it becomes much easier to port new Linux kernel versions because\n  lots of low-level, hardware dependent stuff are done by U-Boot\n\n- the same Linux kernel image can now be used with different \"initrd\"\n  images; of course this also means that different kernel images can\n  be run with the same \"initrd\". This makes testing easier (you don't\n  have to build a new \"zImage.initrd\" Linux image when you just\n  change a file in your \"initrd\"). Also, a field-upgrade of the\n  software is easier now.\n\n\nLinux HOWTO:\n============\n\nPorting Linux to U-Boot based systems:\n---------------------------------------\n\nU-Boot cannot save you from doing all the necessary modifications to\nconfigure the Linux device drivers for use with your target hardware\n(no, we don't intend to provide a full virtual machine interface to\nLinux :-).\n\nBut now you can ignore ALL boot loader code (in arch/powerpc/mbxboot).\n\nJust make sure your machine specific header file (for instance\ninclude/asm-ppc/tqm8xx.h) includes the same definition of the Board\nInformation structure as we define in include/asm-\u003carch\u003e/u-boot.h,\nand make sure that your definition of IMAP_ADDR uses the same value\nas your U-Boot configuration in CONFIG_SYS_IMMR.\n\n\nConfiguring the Linux kernel:\n-----------------------------\n\nNo specific requirements for U-Boot. Make sure you have some root\ndevice (initial ramdisk, NFS) for your target system.\n\n\nBuilding a Linux Image:\n-----------------------\n\nWith U-Boot, \"normal\" build targets like \"zImage\" or \"bzImage\" are\nnot used. If you use recent kernel source, a new build target\n\"uImage\" will exist which automatically builds an image usable by\nU-Boot. Most older kernels also have support for a \"pImage\" target,\nwhich was introduced for our predecessor project PPCBoot and uses a\n100% compatible format.\n\nExample:\n\n\tmake TQM850L_config\n\tmake oldconfig\n\tmake dep\n\tmake uImage\n\nThe \"uImage\" build target uses a special tool (in 'tools/mkimage') to\nencapsulate a compressed Linux kernel image with header\t information,\nCRC32 checksum etc. for use with U-Boot. This is what we are doing:\n\n* build a standard \"vmlinux\" kernel image (in ELF binary format):\n\n* convert the kernel into a raw binary image:\n\n\t${CROSS_COMPILE}-objcopy -O binary \\\n\t\t\t\t -R .note -R .comment \\\n\t\t\t\t -S vmlinux linux.bin\n\n* compress the binary image:\n\n\tgzip -9 linux.bin\n\n* package compressed binary image for U-Boot:\n\n\tmkimage -A ppc -O linux -T kernel -C gzip \\\n\t\t-a 0 -e 0 -n \"Linux Kernel Image\" \\\n\t\t-d linux.bin.gz uImage\n\n\nThe \"mkimage\" tool can also be used to create ramdisk images for use\nwith U-Boot, either separated from the Linux kernel image, or\ncombined into one file. \"mkimage\" encapsulates the images with a 64\nbyte header containing information about target architecture,\noperating system, image type, compression method, entry points, time\nstamp, CRC32 checksums, etc.\n\n\"mkimage\" can be called in two ways: to verify existing images and\nprint the header information, or to build new images.\n\nIn the first form (with \"-l\" option) mkimage lists the information\ncontained in the header of an existing U-Boot image; this includes\nchecksum verification:\n\n\ttools/mkimage -l image\n\t  -l ==\u003e list image header information\n\nThe second form (with \"-d\" option) is used to build a U-Boot image\nfrom a \"data file\" which is used as image payload:\n\n\ttools/mkimage -A arch -O os -T type -C comp -a addr -e ep \\\n\t\t      -n name -d data_file image\n\t  -A ==\u003e set architecture to 'arch'\n\t  -O ==\u003e set operating system to 'os'\n\t  -T ==\u003e set image type to 'type'\n\t  -C ==\u003e set compression type 'comp'\n\t  -a ==\u003e set load address to 'addr' (hex)\n\t  -e ==\u003e set entry point to 'ep' (hex)\n\t  -n ==\u003e set image name to 'name'\n\t  -d ==\u003e use image data from 'datafile'\n\nRight now, all Linux kernels for PowerPC systems use the same load\naddress (0x00000000), but the entry point address depends on the\nkernel version:\n\n- 2.2.x kernels have the entry point at 0x0000000C,\n- 2.3.x and later kernels have the entry point at 0x00000000.\n\nSo a typical call to build a U-Boot image would read:\n\n\t-\u003e tools/mkimage -n '2.4.4 kernel for TQM850L' \\\n\t\u003e -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \\\n\t\u003e -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \\\n\t\u003e examples/uImage.TQM850L\n\tImage Name:   2.4.4 kernel for TQM850L\n\tCreated:      Wed Jul 19 02:34:59 2000\n\tImage Type:   PowerPC Linux Kernel Image (gzip compressed)\n\tData Size:    335725 Bytes = 327.86 kB = 0.32 MB\n\tLoad Address: 0x00000000\n\tEntry Point:  0x00000000\n\nTo verify the contents of the image (or check for corruption):\n\n\t-\u003e tools/mkimage -l examples/uImage.TQM850L\n\tImage Name:   2.4.4 kernel for TQM850L\n\tCreated:      Wed Jul 19 02:34:59 2000\n\tImage Type:   PowerPC Linux Kernel Image (gzip compressed)\n\tData Size:    335725 Bytes = 327.86 kB = 0.32 MB\n\tLoad Address: 0x00000000\n\tEntry Point:  0x00000000\n\nNOTE: for embedded systems where boot time is critical you can trade\nspeed for memory and install an UNCOMPRESSED image instead: this\nneeds more space in Flash, but boots much faster since it does not\nneed to be uncompressed:\n\n\t-\u003e gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz\n\t-\u003e tools/mkimage -n '2.4.4 kernel for TQM850L' \\\n\t\u003e -A ppc -O linux -T kernel -C none -a 0 -e 0 \\\n\t\u003e -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \\\n\t\u003e examples/uImage.TQM850L-uncompressed\n\tImage Name:   2.4.4 kernel for TQM850L\n\tCreated:      Wed Jul 19 02:34:59 2000\n\tImage Type:   PowerPC Linux Kernel Image (uncompressed)\n\tData Size:    792160 Bytes = 773.59 kB = 0.76 MB\n\tLoad Address: 0x00000000\n\tEntry Point:  0x00000000\n\n\nSimilar you can build U-Boot images from a 'ramdisk.image.gz' file\nwhen your kernel is intended to use an initial ramdisk:\n\n\t-\u003e tools/mkimage -n 'Simple Ramdisk Image' \\\n\t\u003e -A ppc -O linux -T ramdisk -C gzip \\\n\t\u003e -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd\n\tImage Name:   Simple Ramdisk Image\n\tCreated:      Wed Jan 12 14:01:50 2000\n\tImage Type:   PowerPC Linux RAMDisk Image (gzip compressed)\n\tData Size:    566530 Bytes = 553.25 kB = 0.54 MB\n\tLoad Address: 0x00000000\n\tEntry Point:  0x00000000\n\n\nInstalling a Linux Image:\n-------------------------\n\nTo downloading a U-Boot image over the serial (console) interface,\nyou must convert the image to S-Record format:\n\n\tobjcopy -I binary -O srec examples/image examples/image.srec\n\nThe 'objcopy' does not understand the information in the U-Boot\nimage header, so the resulting S-Record file will be relative to\naddress 0x00000000. To load it to a given address, you need to\nspecify the target address as 'offset' parameter with the 'loads'\ncommand.\n\nExample: install the image to address 0x40100000 (which on the\nTQM8xxL is in the first Flash bank):\n\n\t=\u003e erase 40100000 401FFFFF\n\n\t.......... done\n\tErased 8 sectors\n\n\t=\u003e loads 40100000\n\t## Ready for S-Record download ...\n\t~\u003eexamples/image.srec\n\t1 2 3 4 5 6 7 8 9 10 11 12 13 ...\n\t...\n\t15989 15990 15991 15992\n\t[file transfer complete]\n\t[connected]\n\t## Start Addr = 0x00000000\n\n\nYou can check the success of the download using the 'iminfo' command;\nthis includes a checksum verification so you can be sure no data\ncorruption happened:\n\n\t=\u003e imi 40100000\n\n\t## Checking Image at 40100000 ...\n\t   Image Name:\t 2.2.13 for initrd on TQM850L\n\t   Image Type:\t PowerPC Linux Kernel Image (gzip compressed)\n\t   Data Size:\t 335725 Bytes = 327 kB = 0 MB\n\t   Load Address: 00000000\n\t   Entry Point:\t 0000000c\n\t   Verifying Checksum ... OK\n\n\nBoot Linux:\n-----------\n\nThe \"bootm\" command is used to boot an application that is stored in\nmemory (RAM or Flash). In case of a Linux kernel image, the contents\nof the \"bootargs\" environment variable is passed to the kernel as\nparameters. You can check and modify this variable using the\n\"printenv\" and \"setenv\" commands:\n\n\n\t=\u003e printenv bootargs\n\tbootargs=root=/dev/ram\n\n\t=\u003e setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2\n\n\t=\u003e printenv bootargs\n\tbootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2\n\n\t=\u003e bootm 40020000\n\t## Booting Linux kernel at 40020000 ...\n\t   Image Name:\t 2.2.13 for NFS on TQM850L\n\t   Image Type:\t PowerPC Linux Kernel Image (gzip compressed)\n\t   Data Size:\t 381681 Bytes = 372 kB = 0 MB\n\t   Load Address: 00000000\n\t   Entry Point:\t 0000000c\n\t   Verifying Checksum ... OK\n\t   Uncompressing Kernel Image ... OK\n\tLinux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000\n\tBoot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2\n\ttime_init: decrementer frequency = 187500000/60\n\tCalibrating delay loop... 49.77 BogoMIPS\n\tMemory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]\n\t...\n\nIf you want to boot a Linux kernel with initial RAM disk, you pass\nthe memory addresses of both the kernel and the initrd image (PPBCOOT\nformat!) to the \"bootm\" command:\n\n\t=\u003e imi 40100000 40200000\n\n\t## Checking Image at 40100000 ...\n\t   Image Name:\t 2.2.13 for initrd on TQM850L\n\t   Image Type:\t PowerPC Linux Kernel Image (gzip compressed)\n\t   Data Size:\t 335725 Bytes = 327 kB = 0 MB\n\t   Load Address: 00000000\n\t   Entry Point:\t 0000000c\n\t   Verifying Checksum ... OK\n\n\t## Checking Image at 40200000 ...\n\t   Image Name:\t Simple Ramdisk Image\n\t   Image Type:\t PowerPC Linux RAMDisk Image (gzip compressed)\n\t   Data Size:\t 566530 Bytes = 553 kB = 0 MB\n\t   Load Address: 00000000\n\t   Entry Point:\t 00000000\n\t   Verifying Checksum ... OK\n\n\t=\u003e bootm 40100000 40200000\n\t## Booting Linux kernel at 40100000 ...\n\t   Image Name:\t 2.2.13 for initrd on TQM850L\n\t   Image Type:\t PowerPC Linux Kernel Image (gzip compressed)\n\t   Data Size:\t 335725 Bytes = 327 kB = 0 MB\n\t   Load Address: 00000000\n\t   Entry Point:\t 0000000c\n\t   Verifying Checksum ... OK\n\t   Uncompressing Kernel Image ... OK\n\t## Loading RAMDisk Image at 40200000 ...\n\t   Image Name:\t Simple Ramdisk Image\n\t   Image Type:\t PowerPC Linux RAMDisk Image (gzip compressed)\n\t   Data Size:\t 566530 Bytes = 553 kB = 0 MB\n\t   Load Address: 00000000\n\t   Entry Point:\t 00000000\n\t   Verifying Checksum ... OK\n\t   Loading Ramdisk ... OK\n\tLinux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000\n\tBoot arguments: root=/dev/ram\n\ttime_init: decrementer frequency = 187500000/60\n\tCalibrating delay loop... 49.77 BogoMIPS\n\t...\n\tRAMDISK: Compressed image found at block 0\n\tVFS: Mounted root (ext2 filesystem).\n\n\tbash#\n\nBoot Linux and pass a flat device tree:\n-----------\n\nFirst, U-Boot must be compiled with the appropriate defines. See the section\ntitled \"Linux Kernel Interface\" above for a more in depth explanation. The\nfollowing is an example of how to start a kernel and pass an updated\nflat device tree:\n\n=\u003e print oftaddr\noftaddr=0x300000\n=\u003e print oft\noft=oftrees/mpc8540ads.dtb\n=\u003e tftp $oftaddr $oft\nSpeed: 1000, full duplex\nUsing TSEC0 device\nTFTP from server 192.168.1.1; our IP address is 192.168.1.101\nFilename 'oftrees/mpc8540ads.dtb'.\nLoad address: 0x300000\nLoading: #\ndone\nBytes transferred = 4106 (100a hex)\n=\u003e tftp $loadaddr $bootfile\nSpeed: 1000, full duplex\nUsing TSEC0 device\nTFTP from server 192.168.1.1; our IP address is 192.168.1.2\nFilename 'uImage'.\nLoad address: 0x200000\nLoading:############\ndone\nBytes transferred = 1029407 (fb51f hex)\n=\u003e print loadaddr\nloadaddr=200000\n=\u003e print oftaddr\noftaddr=0x300000\n=\u003e bootm $loadaddr - $oftaddr\n## Booting image at 00200000 ...\n   Image Name:\t Linux-2.6.17-dirty\n   Image Type:\t PowerPC Linux Kernel Image (gzip compressed)\n   Data Size:\t 1029343 Bytes = 1005.2 kB\n   Load Address: 00000000\n   Entry Point:\t 00000000\n   Verifying Checksum ... OK\n   Uncompressing Kernel Image ... OK\nBooting using flat device tree at 0x300000\nUsing MPC85xx ADS machine description\nMemory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb\n[snip]\n\n\nMore About U-Boot Image Types:\n------------------------------\n\nU-Boot supports the following image types:\n\n   \"Standalone Programs\" are directly runnable in the environment\n\tprovided by U-Boot; it is expected that (if they behave\n\twell) you can continue to work in U-Boot after return from\n\tthe Standalone Program.\n   \"OS Kernel Images\" are usually images of some Embedded OS which\n\twill take over control completely. Usually these programs\n\twill install their own set of exception handlers, device\n\tdrivers, set up the MMU, etc. - this means, that you cannot\n\texpect to re-enter U-Boot except by resetting the CPU.\n   \"RAMDisk Images\" are more or less just data blocks, and their\n\tparameters (address, size) are passed to an OS kernel that is\n\tbeing started.\n   \"Multi-File Images\" contain several images, typically an OS\n\t(Linux) kernel image and one or more data images like\n\tRAMDisks. This construct is useful for instance when you want\n\tto boot over the network using BOOTP etc., where the boot\n\tserver provides just a single image file, but you want to get\n\tfor instance an OS kernel and a RAMDisk image.\n\n\t\"Multi-File Images\" start with a list of image sizes, each\n\timage size (in bytes) specified by an \"uint32_t\" in network\n\tbyte order. This list is terminated by an \"(uint32_t)0\".\n\tImmediately after the terminating 0 follow the images, one by\n\tone, all aligned on \"uint32_t\" boundaries (size rounded up to\n\ta multiple of 4 bytes).\n\n   \"Firmware Images\" are binary images containing firmware (like\n\tU-Boot or FPGA images) which usually will be programmed to\n\tflash memory.\n\n   \"Script files\" are command sequences that will be executed by\n\tU-Boot's command interpreter; this feature is especially\n\tuseful when you configure U-Boot to use a real shell (hush)\n\tas command interpreter.\n\nBooting the Linux zImage:\n-------------------------\n\nOn some platforms, it's possible to boot Linux zImage. This is done\nusing the \"bootz\" command. The syntax of \"bootz\" command is the same\nas the syntax of \"bootm\" command.\n\nNote, defining the CONFIG_SUPPORT_RAW_INITRD allows user to supply\nkernel with raw initrd images. The syntax is slightly different, the\naddress of the initrd must be augmented by it's size, in the following\nformat: \"\u003cinitrd addres\u003e:\u003cinitrd size\u003e\".\n\n\nStandalone HOWTO:\n=================\n\nOne of the features of U-Boot is that you can dynamically load and\nrun \"standalone\" applications, which can use some resources of\nU-Boot like console I/O functions or interrupt services.\n\nTwo simple examples are included with the sources:\n\n\"Hello World\" Demo:\n-------------------\n\n'examples/hello_world.c' contains a small \"Hello World\" Demo\napplication; it is automatically compiled when you build U-Boot.\nIt's configured to run at address 0x00040004, so you can play with it\nlike that:\n\n\t=\u003e loads\n\t## Ready for S-Record download ...\n\t~\u003eexamples/hello_world.srec\n\t1 2 3 4 5 6 7 8 9 10 11 ...\n\t[file transfer complete]\n\t[connected]\n\t## Start Addr = 0x00040004\n\n\t=\u003e go 40004 Hello World! This is a test.\n\t## Starting application at 0x00040004 ...\n\tHello World\n\targc = 7\n\targv[0] = \"40004\"\n\targv[1] = \"Hello\"\n\targv[2] = \"World!\"\n\targv[3] = \"This\"\n\targv[4] = \"is\"\n\targv[5] = \"a\"\n\targv[6] = \"test.\"\n\targv[7] = \"\u003cNULL\u003e\"\n\tHit any key to exit ...\n\n\t## Application terminated, rc = 0x0\n\nAnother example, which demonstrates how to register a CPM interrupt\nhandler with the U-Boot code, can be found in 'examples/timer.c'.\nHere, a CPM timer is set up to generate an interrupt every second.\nThe interrupt service routine is trivial, just printing a '.'\ncharacter, but this is just a demo program. The application can be\ncontrolled by the following keys:\n\n\t? - print current values og the CPM Timer registers\n\tb - enable interrupts and start timer\n\te - stop timer and disable interrupts\n\tq - quit application\n\n\t=\u003e loads\n\t## Ready for S-Record download ...\n\t~\u003eexamples/timer.srec\n\t1 2 3 4 5 6 7 8 9 10 11 ...\n\t[file transfer complete]\n\t[connected]\n\t## Start Addr = 0x00040004\n\n\t=\u003e go 40004\n\t## Starting application at 0x00040004 ...\n\tTIMERS=0xfff00980\n\tUsing timer 1\n\t  tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0\n\nHit 'b':\n\t[q, b, e, ?] Set interval 1000000 us\n\tEnabling timer\nHit '?':\n\t[q, b, e, ?] ........\n\ttgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0\nHit '?':\n\t[q, b, e, ?] .\n\ttgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0\nHit '?':\n\t[q, b, e, ?] .\n\ttgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0\nHit '?':\n\t[q, b, e, ?] .\n\ttgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0\nHit 'e':\n\t[q, b, e, ?] ...Stopping timer\nHit 'q':\n\t[q, b, e, ?] ## Application terminated, rc = 0x0\n\n\nMinicom warning:\n================\n\nOver time, many people have reported problems when trying to use the\n\"minicom\" terminal emulation program for serial download. I (wd)\nconsider minicom to be broken, and recommend not to use it. Under\nUnix, I recommend to use C-Kermit for general purpose use (and\nespecially for kermit binary protocol download (\"loadb\" command), and\nuse \"cu\" for S-Record download (\"loads\" command).  See\nhttp://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3.\nfor help with kermit.\n\n\nNevertheless, if you absolutely want to use it try adding this\nconfiguration to your \"File transfer protocols\" section:\n\n\t   Name\t   Program\t\t\tName U/D FullScr IO-Red. Multi\n\tX  kermit  /usr/bin/kermit -i -l %l -s\t Y    U\t   Y\t   N\t  N\n\tY  kermit  /usr/bin/kermit -i -l %l -r\t N    D\t   Y\t   N\t  N\n\n\nNetBSD Notes:\n=============\n\nStarting at version 0.9.2, U-Boot supports NetBSD both as host\n(build U-Boot) and target system (boots NetBSD/mpc8xx).\n\nBuilding requires a cross environment; it is known to work on\nNetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also\nneed gmake since the Makefiles are not compatible with BSD make).\nNote that the cross-powerpc package does not install include files;\nattempting to build U-Boot will fail because \u003cmachine/ansi.h\u003e is\nmissing.  This file has to be installed and patched manually:\n\n\t# cd /usr/pkg/cross/powerpc-netbsd/include\n\t# mkdir powerpc\n\t# ln -s powerpc machine\n\t# cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h\n\t# ${EDIT} powerpc/ansi.h\t## must remove __va_list, _BSD_VA_LIST\n\nNative builds *don't* work due to incompatibilities between native\nand U-Boot include files.\n\nBooting assumes that (the first part of) the image booted is a\nstage-2 loader which in turn loads and then invokes the kernel\nproper. Loader sources will eventually appear in the NetBSD source\ntree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the\nmeantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz\n\n\nImplementation Internals:\n=========================\n\nThe following is not intended to be a complete description of every\nimplementation detail. However, it should help to understand the\ninner workings of U-Boot and make it easier to port it to custom\nhardware.\n\n\nInitial Stack, Global Data:\n---------------------------\n\nThe implementation of U-Boot is complicated by the fact that U-Boot\nstarts running out of ROM (flash memory), usually without access to\nsystem RAM (because the memory controller is not initialized yet).\nThis means that we don't have writable Data or BSS segments, and BSS\nis not initialized as zero. To be able to get a C environment working\nat all, we have to allocate at least a minimal stack. Implementation\noptions for this are defined and restricted by the CPU used: Some CPU\nmodels provide on-chip memory (like the IMMR area on MPC8xx and\nMPC826x processors), on others (parts of) the data cache can be\nlocked as (mis-) used as memory, etc.\n\n\tChris Hallinan posted a good summary of these issues to the\n\tU-Boot mailing list:\n\n\tSubject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?\n\tFrom: \"Chris Hallinan\" \u003cclh@net1plus.com\u003e\n\tDate: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)\n\t...\n\n\tCorrect me if I'm wrong, folks, but the way I understand it\n\tis this: Using DCACHE as initial RAM for Stack, etc, does not\n\trequire any physical RAM backing up the cache. The cleverness\n\tis that the cache is being used as a temporary supply of\n\tnecessary storage before the SDRAM controller is setup. It's\n\tbeyond the scope of this list to explain the details, but you\n\tcan see how this works by studying the cache architecture and\n\toperation in the architecture and processor-specific manuals.\n\n\tOCM is On Chip Memory, which I believe the 405GP has 4K. It\n\tis another option for the system designer to use as an\n\tinitial stack/RAM area prior to SDRAM being available. Either\n\toption should work for you. Using CS 4 should be fine if your\n\tboard designers haven't used it for something that would\n\tcause you grief during the initial boot! It is frequently not\n\tused.\n\n\tCONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere\n\twith your processor/board/system design. The default value\n\tyou will find in any recent u-boot distribution in\n\twalnut.h should work for you. I'd set it to a value larger\n\tthan your SDRAM module. If you have a 64MB SDRAM module, set\n\tit above 400_0000. Just make sure your board has no resources\n\tthat are supposed to respond to that address! That code in\n\tstart.S has been around a while and should work as is when\n\tyou get the config right.\n\n\t-Chris Hallinan\n\tDS4.COM, Inc.\n\nIt is essential to remember this, since it has some impact on the C\ncode for the initialization procedures:\n\n* Initialized global data (data segment) is read-only. Do not attempt\n  to write it.\n\n* Do not use any uninitialized global data (or implicitely initialized\n  as zero data - BSS segment) at all - this is undefined, initiali-\n  zation is performed later (when relocating to RAM).\n\n* Stack space is very limited. Avoid big data buffers or things like\n  that.\n\nHaving only the stack as writable memory limits means we cannot use\nnormal global data to share information beween the code. But it\nturned out that the implementation of U-Boot can be greatly\nsimplified by making a global data structure (gd_t) available to all\nfunctions. We could pass a pointer to this data as argument to _all_\nfunctions, but this would bloat the code. Instead we use a feature of\nthe GCC compiler (Global Register Variables) to share the data: we\nplace a pointer (gd) to the global data into a register which we\nreserve for this purpose.\n\nWhen choosing a register for such a purpose we are restricted by the\nrelevant  (E)ABI  specifications for the current architecture, and by\nGCC's implementation.\n\nFor PowerPC, the following registers have specific use:\n\tR1:\tstack pointer\n\tR2:\treserved for system use\n\tR3-R4:\tparameter passing and return values\n\tR5-R10: parameter passing\n\tR13:\tsmall data area pointer\n\tR30:\tGOT pointer\n\tR31:\tframe pointer\n\n\t(U-Boot also uses R12 as internal GOT pointer. r12\n\tis a volatile register so r12 needs to be reset when\n\tgoing back and forth between asm and C)\n\n    ==\u003e U-Boot will use R2 to hold a pointer to the global data\n\n    Note: on PPC, we could use a static initializer (since the\n    address of the global data structure is known at compile time),\n    but it turned out that reserving a register results in somewhat\n    smaller code - although the code savings are not that big (on\n    average for all boards 752 bytes for the whole U-Boot image,\n    624 text + 127 data).\n\nOn Blackfin, the normal C ABI (except for P3) is followed as documented here:\n\thttp://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface\n\n    ==\u003e U-Boot will use P3 to hold a pointer to the global data\n\nOn ARM, the following registers are used:\n\n\tR0:\tfunction argument word/integer result\n\tR1-R3:\tfunction argument word\n\tR9:\tGOT pointer\n\tR10:\tstack limit (used only if stack checking if enabled)\n\tR11:\targument (frame) pointer\n\tR12:\ttemporary workspace\n\tR13:\tstack pointer\n\tR14:\tlink register\n\tR15:\tprogram counter\n\n    ==\u003e U-Boot will use R8 to hold a pointer to the global data\n\nOn Nios II, the ABI is documented here:\n\thttp://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf\n\n    ==\u003e U-Boot will use gp to hold a pointer to the global data\n\n    Note: on Nios II, we give \"-G0\" option to gcc and don't use gp\n    to access small data sections, so gp is free.\n\nOn NDS32, the following registers are used:\n\n\tR0-R1:\targument/return\n\tR2-R5:\targument\n\tR15:\ttemporary register for assembler\n\tR16:\ttrampoline register\n\tR28:\tframe pointer (FP)\n\tR29:\tglobal pointer (GP)\n\tR30:\tlink register (LP)\n\tR31:\tstack pointer (SP)\n\tPC:\tprogram counter (PC)\n\n    ==\u003e U-Boot will use R10 to hold a pointer to the global data\n\nNOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,\nor current versions of GCC may \"optimize\" the code too much.\n\nMemory Management:\n------------------\n\nU-Boot runs in system state and uses physical addresses, i.e. the\nMMU is not used either for address mapping nor for memory protection.\n\nThe available memory is mapped to fixed addresses using the memory\ncontroller. In this process, a contiguous block is formed for each\nmemory type (Flash, SDRAM, SRAM), even when it consists of several\nphysical memory banks.\n\nU-Boot is installed in the first 128 kB of the first Flash bank (on\nTQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After\nbooting and sizing and initializing DRAM, the code relocates itself\nto the upper end of DRAM. Immediately below the U-Boot code some\nmemory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN\nconfiguration setting]. Below that, a structure with global Board\nInfo data is placed, followed by the stack (growing downward).\n\nAdditionally, some exception handler code is copied to the low 8 kB\nof DRAM (0x00000000 ... 0x00001FFF).\n\nSo a typical memory configuration with 16 MB of DRAM could look like\nthis:\n\n\t0x0000 0000\tException Vector code\n\t      :\n\t0x0000 1FFF\n\t0x0000 2000\tFree for Application Use\n\t      :\n\t      :\n\n\t      :\n\t      :\n\t0x00FB FF20\tMonitor Stack (Growing downward)\n\t0x00FB FFAC\tBoard Info Data and permanent copy of global data\n\t0x00FC 0000\tMalloc Arena\n\t      :\n\t0x00FD FFFF\n\t0x00FE 0000\tRAM Copy of Monitor Code\n\t...\t\teventually: LCD or video framebuffer\n\t...\t\teventually: pRAM (Protected RAM - unchanged by reset)\n\t0x00FF FFFF\t[End of RAM]\n\n\nSystem Initialization:\n----------------------\n\nIn the reset configuration, U-Boot starts at the reset entry point\n(on most PowerPC systems at address 0x00000100). Because of the reset\nconfiguration for CS0# this is a mirror of the onboard Flash memory.\nTo be able to re-map memory U-Boot then jumps to its link address.\nTo be able to implement the initialization code in C, a (small!)\ninitial stack is set up in the internal Dual Ported RAM (in case CPUs\nwhich provide such a feature like MPC8xx or MPC8260), or in a locked\npart of the data cache. After that, U-Boot initializes the CPU core,\nthe caches and the SIU.\n\nNext, all (potentially) available memory banks are mapped using a\npreliminary mapping. For example, we put them on 512 MB boundaries\n(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash\non 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is\nprogrammed for SDRAM access. Using the temporary configuration, a\nsimple memory test is run that determines the size of the SDRAM\nbanks.\n\nWhen there is more than one SDRAM bank, and the banks are of\ndifferent size, the largest is mapped first. For equal size, the first\nbank (CS2#) is mapped first. The first mapping is always for address\n0x00000000, with any additional banks following immediately to create\ncontiguous memory starting from 0.\n\nThen, the monitor installs itself at the upper end of the SDRAM area\nand allocates memory for use by malloc() and for the global Board\nInfo data; also, the exception vector code is copied to the low RAM\npages, and the final stack is set up.\n\nOnly after this relocation will you have a \"normal\" C environment;\nuntil that you are restricted in several ways, mostly because you are\nrunning from ROM, and because the code will have to be relocated to a\nnew address in RAM.\n\n\nU-Boot Porting Guide:\n----------------------\n\n[Based on messages by Jerry Van Baren in the U-Boot-Users mailing\nlist, October 2002]\n\n\nint main(int argc, char *argv[])\n{\n\tsighandler_t no_more_time;\n\n\tsignal(SIGALRM, no_more_time);\n\talarm(PROJECT_DEADLINE - toSec (3 * WEEK));\n\n\tif (available_money \u003e available_manpower) {\n\t\tPay consultant to port U-Boot;\n\t\treturn 0;\n\t}\n\n\tDownload latest U-Boot source;\n\n\tSubscribe to u-boot mailing list;\n\n\tif (clueless)\n\t\temail(\"Hi, I am new to U-Boot, how do I get started?\");\n\n\twhile (learning) {\n\t\tRead the README file in the top level directory;\n\t\tRead http://www.denx.de/twiki/bin/view/DULG/Manual;\n\t\tRead applicable doc/*.README;\n\t\tRead the source, Luke;\n\t\t/* find . -name \"*.[chS]\" | xargs grep -i \u003ckeyword\u003e */\n\t}\n\n\tif (available_money \u003e toLocalCurrency ($2500))\n\t\tBuy a BDI3000;\n\telse\n\t\tAdd a lot of aggravation and time;\n\n\tif (a similar board exists) {\t/* hopefully... */\n\t\tcp -a board/\u003csimilar\u003e board/\u003cmyboard\u003e\n\t\tcp include/configs/\u003csimilar\u003e.h include/configs/\u003cmyboard\u003e.h\n\t} else {\n\t\tCreate your own board support subdirectory;\n\t\tCreate your own board include/configs/\u003cmyboard\u003e.h file;\n\t}\n\tEdit new board/\u003cmyboard\u003e files\n\tEdit new include/configs/\u003cmyboard\u003e.h\n\n\twhile (!accepted) {\n\t\twhile (!running) {\n\t\t\tdo {\n\t\t\t\tAdd / modify source code;\n\t\t\t} until (compiles);\n\t\t\tDebug;\n\t\t\tif (clueless)\n\t\t\t\temail(\"Hi, I am having problems...\");\n\t\t}\n\t\tSend patch file to the U-Boot email list;\n\t\tif (reasonable critiques)\n\t\t\tIncorporate improvements from email list code review;\n\t\telse\n\t\t\tDefend code as written;\n\t}\n\n\treturn 0;\n}\n\nvoid no_more_time (int sig)\n{\n      hire_a_guru();\n}\n\n\nCoding Standards:\n-----------------\n\nAll contributions to U-Boot should conform to the Linux kernel\ncoding style; see the file \"Documentation/CodingStyle\" and the script\n\"scripts/Lindent\" in your Linux kernel source directory.\n\nSource files originating from a different project (for example the\nMTD subsystem) are generally exempt from these guidelines and are not\nreformated to ease subsequent migration to newer versions of those\nsources.\n\nPlease note that U-Boot is implemented in C (and to some small parts in\nAssembler); no C++ is used, so please do not use C++ style comments (//)\nin your code.\n\nPlease also stick to the following formatting rules:\n- remove any trailing white space\n- use TAB characters for indentation and vertical alignment, not spaces\n- make sure NOT to use DOS '\\r\\n' line feeds\n- do not add more than 2 consecutive empty lines to source files\n- do not add trailing empty lines to source files\n\nSubmissions which do not conform to the standards may be returned\nwith a request to reformat the changes.\n\n\nSubmitting Patches:\n-------------------\n\nSince the number of patches for U-Boot is growing, we need to\nestablish some rules. Submissions which do not conform to these rules\nmay be rejected, even when they contain important and valuable stuff.\n\nPlease see http://www.denx.de/wiki/U-Boot/Patches for details.\n\nPatches shall be sent to the u-boot mailing list \u003cu-boot@lists.denx.de\u003e;\nsee http://lists.denx.de/mailman/listinfo/u-boot\n\nWhen you send a patch, please include the following information with\nit:\n\n* For bug fixes: a description of the bug and how your patch fixes\n  this bug. Please try to include a way of demonstrating that the\n  patch actually fixes something.\n\n* For new features: a description of the feature and your\n  implementation.\n\n* A CHANGELOG entry as plaintext (separate from the patch)\n\n* For major contributions, your entry to the CREDITS file\n\n* When you add support for a new board, don't forget to add this\n  board to the MAINTAINERS file, too.\n\n* If your patch adds new configuration options, don't forget to\n  document these in the README file.\n\n* The patch itself. If you are using git (which is *strongly*\n  recommended) you can easily generate the patch using the\n  \"git format-patch\". If you then use \"git send-email\" to send it to\n  the U-Boot mailing list, you will avoid most of the common problems\n  with some other mail clients.\n\n  If you cannot use git, use \"diff -purN OLD NEW\". If your version of\n  diff does not support these options, then get the latest version of\n  GNU diff.\n\n  The current directory when running this command shall be the parent\n  directory of the U-Boot source tree (i. e. please make sure that\n  your patch includes sufficient directory information for the\n  affected files).\n\n  We prefer patches as plain text. MIME attachments are discouraged,\n  and compressed attachments must not be used.\n\n* If one logical set of modifications affects or creates several\n  files, all these changes shall be submitted in a SINGLE patch file.\n\n* Changesets that contain different, unrelated modifications shall be\n  submitted as SEPARATE patches, one patch per changeset.\n\n\nNotes:\n\n* Before sending the patch, run the MAKEALL script on your patched\n  source tree and make sure that no errors or warnings are reported\n  for any of the boards.\n\n* Keep your modifications to the necessary minimum: A patch\n  containing several unrelated changes or arbitrary reformats will be\n  returned with a request to re-formatting / split it.\n\n* If you modify existing code, make sure that your new code does not\n  add to the memory footprint of the code ;-) Small is beautiful!\n  When adding new features, these should compile conditionally only\n  (using #ifdef), and the resulting code with the new feature\n  disabled must not need more memory than the old code without your\n  modification.\n\n* Remember that there is a size limit of 100 kB per message on the\n  u-boot mailing list. Bigger patches will be moderated. If they are\n  reasonable and not too big, they will be acknowledged. But patches\n  bigger than the size limit should be avoided.\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fopenipc%2Fu-boot-t20","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fopenipc%2Fu-boot-t20","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fopenipc%2Fu-boot-t20/lists"}