nds32: add header files support for nds32

[u-boot] / README

diff --git a/README b/README
index e0a4d53ed9250f03e34f52b9360140c76bc85c73..eb9ade9ad4c987a553f1198786b5e8b051c5425d 100644 (file)
--- a/README
+++ b/README
@@ -181,6 +181,7 @@ Directory Hierarchy:
   /mips                        Files generic to MIPS architecture
     /cpu               CPU specific files
       /mips32          Files specific to MIPS32 CPUs
+      /xburst          Files specific to Ingenic XBurst CPUs
     /lib               Architecture specific library files
   /nios2               Files generic to Altera NIOS2 architecture
     /cpu               CPU specific files
@@ -627,7 +628,7 @@ The following options need to be configured:
                initialised to a buffer of size CONFIG_PRE_CON_BUF_SZ
                bytes located at CONFIG_PRE_CON_BUF_ADDR. The buffer is
                a circular buffer, so if more than CONFIG_PRE_CON_BUF_SZ
-               bytes are output before the console is  initialised, the
+               bytes are output before the console is initialised, the
                earlier bytes are discarded.
 
                'Sane' compilers will generate smaller code if
@@ -783,6 +784,7 @@ The following options need to be configured:
                CONFIG_CMD_SOURCE         "source" command Support
                CONFIG_CMD_SPI          * SPI serial bus support
                CONFIG_CMD_TFTPSRV      * TFTP transfer in server mode
+               CONFIG_CMD_TIME         * run command and report execution time
                CONFIG_CMD_USB          * USB support
                CONFIG_CMD_CDP          * Cisco Discover Protocol support
                CONFIG_CMD_FSL          * Microblaze FSL support
@@ -2264,9 +2266,9 @@ FIT uImage format:
 - Standalone program support:
                CONFIG_STANDALONE_LOAD_ADDR
 
-               This option allows to define board specific values
-               for the address where standalone program gets loaded,
-               thus overwriting the architecutre dependent default
+               This option defines a board specific value for the
+               address where standalone program gets loaded, thus
+               overwriting the architecture dependent default
                settings.
 
 - Frame Buffer Address:
@@ -2276,13 +2278,10 @@ FIT uImage format:
                address for frame buffer.
                Then system will reserve the frame buffer address to
                defined address instead of lcd_setmem (this function
-               grab the memory for frame buffer by panel's size).
+               grabs the memory for frame buffer by panel's size).
 
                Please see board_init_f function.
 
-               If you want this config option then,
-               please define it at your board config file
-
 - Automatic software updates via TFTP server
                CONFIG_UPDATE_TFTP
                CONFIG_UPDATE_TFTP_CNT_MAX
@@ -3101,6 +3100,9 @@ Low Level (hardware related) configuration options:
                parameters are extracted from datasheet and hard-coded into
                header files or board specific files.
 
+- CONFIG_FSL_DDR_INTERACTIVE
+               Enable interactive DDR debugging. See doc/README.fsl-ddr.
+
 - CONFIG_SYS_83XX_DDR_USES_CS0
                Only for 83xx systems. If specified, then DDR should
                be configured using CS0 and CS1 instead of CS2 and CS3.
@@ -3556,6 +3558,25 @@ List of environment variables (most likely not complete):
                  Ethernet is encapsulated/received over 802.1q
                  VLAN tagged frames.
 
+The following image location variables contain the location of images
+used in booting. The "Image" column gives the role of the image and is
+not an environment variable name. The other columns are environment
+variable names. "File Name" gives the name of the file on a TFTP
+server, "RAM Address" gives the location in RAM the image will be
+loaded to, and "Flash Location" gives the image's address in NOR
+flash or offset in NAND flash.
+
+*Note* - these variables don't have to be defined for all boards, some
+boards currenlty use other variables for these purposes, and some
+boards use these variables for other purposes.
+
+Image               File Name        RAM Address       Flash Location
+-----               ---------        -----------       --------------
+u-boot              u-boot           u-boot_addr_r     u-boot_addr
+Linux kernel        bootfile         kernel_addr_r     kernel_addr
+device tree blob    fdtfile          fdt_addr_r        fdt_addr
+ramdisk             ramdiskfile      ramdisk_addr_r    ramdisk_addr
+
 The following environment variables may be used and automatically
 updated by the network boot commands ("bootp" and "rarpboot"),
 depending the information provided by your boot server: