Kconfig: Remove CONFIG_CLOCKS_IN_MHZ

[platform/kernel/u-boot.git] / README

diff --git a/README b/README
index 2e8ad3b..020918a 100644 (file)
--- a/README
+++ b/README
@@ -559,19 +559,6 @@ The following options need to be configured:
                such as ARM architectural timer initialization.
 
 - Linux Kernel Interface:
                such as ARM architectural timer initialization.
 
 - Linux Kernel Interface:

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

                CONFIG_MEMSIZE_IN_BYTES         [relevant for MIPS only]
 
                When transferring memsize parameter to Linux, some versions
                CONFIG_MEMSIZE_IN_BYTES         [relevant for MIPS only]
 
                When transferring memsize parameter to Linux, some versions


@@ -670,11 +657,6 @@ The following options need to be configured:
                Define this variable to enable hw flow control in serial driver.
                Current user of this option is drivers/serial/nsl16550.c driver
 
                Define this variable to enable hw flow control in serial driver.
                Current user of this option is drivers/serial/nsl16550.c driver
 

-- Console Baudrate:
-               CONFIG_BAUDRATE - in bps
-               Select one of the baudrates listed in
-               CONFIG_SYS_BAUDRATE_TABLE, see below.
-

 - Autoboot Command:
                CONFIG_BOOTCOMMAND
                Only needed when CONFIG_BOOTDELAY is enabled;
 - Autoboot Command:
                CONFIG_BOOTCOMMAND
                Only needed when CONFIG_BOOTDELAY is enabled;


@@ -889,11 +871,6 @@ The following options need to be configured:
                Allow generic access to the SPI bus on the Intel 8257x, for
                example with the "sspi" command.
 
                Allow generic access to the SPI bus on the Intel 8257x, for
                example with the "sspi" command.
 

-               CONFIG_EEPRO100
-               Support for Intel 82557/82559/82559ER chips.
-               Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
-               write routine for first time initialisation.
-

                CONFIG_TULIP
                Support for Digital 2114x chips.
 
                CONFIG_TULIP
                Support for Digital 2114x chips.
 


@@ -1330,21 +1307,6 @@ The following options need to be configured:
                can be displayed via the splashscreen support or the
                bmp command.
 
                can be displayed via the splashscreen support or the
                bmp command.
 

-- Compression support:
-               CONFIG_GZIP
-
-               Enabled by default to support gzip compressed images.
-
-               CONFIG_BZIP2
-
-               If this option is set, support for bzip2 compressed
-               images is included. If not, only uncompressed and gzip
-               compressed images are supported.
-
-               NOTE: the bzip2 algorithm requires a lot of RAM, so
-               the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
-               be at least 4MB.
-

 - MII/PHY support:
                CONFIG_PHY_CLOCK_FREQ (ppc4xx)
 
 - MII/PHY support:
                CONFIG_PHY_CLOCK_FREQ (ppc4xx)
 


@@ -1567,14 +1529,6 @@ The following options need to be configured:
 
                This enable the NEW i2c subsystem, and will allow you to use
                i2c commands at the u-boot command line (as long as you set
 
                This enable the NEW i2c subsystem, and will allow you to use
                i2c commands at the u-boot command line (as long as you set

-               CONFIG_CMD_I2C in CONFIG_COMMANDS) and communicate with i2c
-               based realtime clock chips or other i2c devices. See
-               common/cmd_i2c.c for a description of the command line
-               interface.
-
-               ported i2c driver to the new framework:
-               - drivers/i2c/soft_i2c.c:
-                 - activate first bus with CONFIG_SYS_I2C_SOFT define

                    CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE
                    for defining speed and slave address
                  - activate second bus with I2C_SOFT_DECLARATIONS2 define
                    CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE
                    for defining speed and slave address
                  - activate second bus with I2C_SOFT_DECLARATIONS2 define


@@ -2473,14 +2427,6 @@ Configuration Settings:
 - CONFIG_SYS_BAUDRATE_TABLE:
                List of legal baudrate settings for this board.
 
 - CONFIG_SYS_BAUDRATE_TABLE:
                List of legal baudrate settings for this board.
 

-- CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END:
-               Begin and End addresses of the area used by the
-               simple memory test.
-
-- CONFIG_SYS_MEMTEST_SCRATCH:
-               Scratch address used by the alternate memory test
-               You only need to set this if address zero isn't writeable
-

 - CONFIG_SYS_MEM_RESERVE_SECURE
                Only implemented for ARMv8 for now.
                If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory
 - CONFIG_SYS_MEM_RESERVE_SECURE
                Only implemented for ARMv8 for now.
                If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory


@@ -2737,10 +2683,6 @@ Configuration Settings:
        regular expression. This allows multiple variables to define the same
        flags without explicitly listing them for each variable.
 
        regular expression. This allows multiple variables to define the same
        flags without explicitly listing them for each variable.
 

-- CONFIG_ENV_ACCESS_IGNORE_FORCE
-       If defined, don't allow the -f switch to env set override variable
-       access flags.
-

 The following definitions that deal with the placement and management
 of environment data (variable area); in general, we support the
 following configurations:
 The following definitions that deal with the placement and management
 of environment data (variable area); in general, we support the
 following configurations: