ARM: uniphier: add macro to generate SoC data look-up function

[people/ms/u-boot.git] / README

diff --git a/README b/README
index 39a3042ce402939184aa170f2d7bc61fff7b3ba8..a95348a876b4a53609ca5e384df5cc49abc61ac2 100644 (file)
--- a/README
+++ b/README
@@ -127,7 +127,7 @@ releases in "stable" maintenance trees.
 Examples:
        U-Boot v2009.11     - Release November 2009
        U-Boot v2009.11.1   - Release 1 in version November 2009 stable tree
-       U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release
+       U-Boot v2010.09-rc1 - Release candidate 1 for September 2010 release
 
 
 Directory Hierarchy:
@@ -376,15 +376,6 @@ The following options need to be configured:
                Defines the string to utilize when trying to match PCIe device
                tree nodes for the given platform.
 
-               CONFIG_SYS_PPC_E500_DEBUG_TLB
-
-               Enables a temporary TLB entry to be used during boot to work
-               around limitations in e500v1 and e500v2 external debugger
-               support. This reduces the portions of the boot code where
-               breakpoints and single stepping do not work.  The value of this
-               symbol should be set to the TLB1 entry to be used for this
-               purpose.
-
                CONFIG_SYS_FSL_ERRATUM_A004510
 
                Enables a workaround for erratum A004510.  If set,
@@ -1589,7 +1580,7 @@ The following options need to be configured:
                This will also enable the command "fatwrite" enabling the
                user to write files to FAT.
 
-CBFS (Coreboot Filesystem) support
+- CBFS (Coreboot Filesystem) support:
                CONFIG_CMD_CBFS
 
                Define this to enable support for reading from a Coreboot
@@ -2042,7 +2033,7 @@ CBFS (Coreboot Filesystem) support
 
                A byte containing the id of the VLAN.
 
-- Status LED:  CONFIG_STATUS_LED
+- Status LED:  CONFIG_LED_STATUS
 
                Several configurations allow to display the current
                status using a LED. For instance, the LED will blink
@@ -2050,15 +2041,15 @@ CBFS (Coreboot Filesystem) support
                soon as a reply to a BOOTP request was received, and
                start blinking slow once the Linux kernel is running
                (supported by a status LED driver in the Linux
-               kernel). Defining CONFIG_STATUS_LED enables this
+               kernel). Defining CONFIG_LED_STATUS enables this
                feature in U-Boot.
 
                Additional options:
 
-               CONFIG_GPIO_LED
+               CONFIG_LED_STATUS_GPIO
                The status LED can be connected to a GPIO pin.
                In such cases, the gpio_led driver can be used as a
-               status LED backend implementation. Define CONFIG_GPIO_LED
+               status LED backend implementation. Define CONFIG_LED_STATUS_GPIO
                to include the gpio_led driver in the U-Boot binary.
 
                CONFIG_GPIO_LED_INVERTED_TABLE
@@ -3338,11 +3329,6 @@ FIT uImage format:
                CONFIG_SPL_INIT_MINIMAL
                Arch init code should be built for a very small image
 
-               CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR,
-               CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS,
-               Address and partition on the MMC to load U-Boot from
-               when the MMC is being used in raw mode.
-
                CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
                Partition on the MMC to load U-Boot from when the MMC is being
                used in raw mode
@@ -4115,7 +4101,7 @@ but it can not erase, write this NOR flash by SRIO or PCIE interface.
 
          Define this to a string that is the name of the block device.
 
-       - FAT_ENV_DEV_AND_PART:
+       - FAT_ENV_DEVICE_AND_PART:
 
          Define this to a string to specify the partition of the device. It can
          be as following:
@@ -4598,12 +4584,6 @@ Low Level (hardware related) configuration options:
                addressable memory. This option causes some memory accesses
                to be mapped through map_sysmem() / unmap_sysmem().
 
-- CONFIG_USE_ARCH_MEMCPY
-  CONFIG_USE_ARCH_MEMSET
-               If these options are used a optimized version of memcpy/memset will
-               be used if available. These functions may be faster under some
-               conditions but may increase the binary size.
-
 - CONFIG_X86_RESET_VECTOR
                If defined, the x86 reset vector code is included. This is not
                needed when U-Boot is running from Coreboot.