ppc: Remove xpedite boards

[platform/kernel/u-boot.git] / env / Kconfig

diff --git a/env/Kconfig b/env/Kconfig
index 4113628..c06b8ba 100644 (file)
--- a/env/Kconfig
+++ b/env/Kconfig
@@ -72,6 +72,7 @@ config ENV_IS_IN_FAT
 config ENV_IS_IN_EXT4
        bool "Environment is in a EXT4 filesystem"
        depends on !CHAIN_OF_TRUST
 config ENV_IS_IN_EXT4
        bool "Environment is in a EXT4 filesystem"
        depends on !CHAIN_OF_TRUST

+       select FS_EXT4

        select EXT4_WRITE
        help
          Define this if you want to use the EXT4 file system for the environment.
        select EXT4_WRITE
        help
          Define this if you want to use the EXT4 file system for the environment.


@@ -81,10 +82,10 @@ config ENV_IS_IN_FLASH
        depends on !CHAIN_OF_TRUST
        default y if ARCH_CINTEGRATOR
        default y if ARCH_INTEGRATOR_CP
        depends on !CHAIN_OF_TRUST
        default y if ARCH_CINTEGRATOR
        default y if ARCH_INTEGRATOR_CP

-       default y if M548x || M547x || M5282 || MCF547x_8x
+       default y if M548x || M547x || M5282

        default y if MCF532x || MCF52x2
        default y if MPC86xx || MPC83xx
        default y if MCF532x || MCF52x2
        default y if MPC86xx || MPC83xx

-       default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
+       default y if ARCH_MPC8548 || ARCH_MPC8641

        default y if SH && !CPU_SH4
        help
          Define this if you have a flash device which you want to use for the
        default y if SH && !CPU_SH4
        help
          Define this if you have a flash device which you want to use for the


@@ -323,6 +324,20 @@ config ENV_IS_IN_SPI_FLASH
          during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
          aligned to an erase sector boundary.
 
          during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
          aligned to an erase sector boundary.
 

+config ENV_SECT_SIZE_AUTO
+       bool "Use automatically detected sector size"
+       depends on ENV_IS_IN_SPI_FLASH
+       help
+         Some boards exist in multiple variants, with different
+         flashes having different sector sizes. In such cases, you
+         can select this option to make U-Boot use the actual sector
+         size when figuring out how much to erase, which can thus be
+         more efficient on the flashes with smaller erase size. Since
+         the environment must always be aligned on a sector boundary,
+         CONFIG_ENV_OFFSET must be aligned to the largest of the
+         different sector sizes, and CONFIG_ENV_SECT_SIZE should be
+         set to that value.
+

 config USE_ENV_SPI_BUS
        bool "SPI flash bus for environment"
        depends on ENV_IS_IN_SPI_FLASH
 config USE_ENV_SPI_BUS
        bool "SPI flash bus for environment"
        depends on ENV_IS_IN_SPI_FLASH


@@ -375,6 +390,14 @@ config ENV_SPI_MODE
          Value of the SPI work mode for environment.
          See include/spi.h for value.
 
          Value of the SPI work mode for environment.
          See include/spi.h for value.
 

+config ENV_SPI_EARLY
+       bool "Access Environment in SPI flashes before relocation"
+       depends on ENV_IS_IN_SPI_FLASH
+       help
+         Enable this if you want to use Environment in SPI flash
+         before relocation. Call env_init() and than you can use
+         env_get_f() for accessing Environment variables.
+

 config ENV_IS_IN_UBI
        bool "Environment in a UBI volume"
        depends on !CHAIN_OF_TRUST
 config ENV_IS_IN_UBI
        bool "Environment in a UBI volume"
        depends on !CHAIN_OF_TRUST


@@ -402,13 +425,14 @@ config ENV_IS_IN_UBI
 
 config SYS_REDUNDAND_ENVIRONMENT
        bool "Enable redundant environment support"
 
 config SYS_REDUNDAND_ENVIRONMENT
        bool "Enable redundant environment support"

-       depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
-               ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI

        help
          Normally, the environemt is stored in a single location.  By
          selecting this option, you can then define where to hold a redundant
          copy of the environment data, so that there is a valid backup copy in
          case there is a power failure during a "saveenv" operation.
        help
          Normally, the environemt is stored in a single location.  By
          selecting this option, you can then define where to hold a redundant
          copy of the environment data, so that there is a valid backup copy in
          case there is a power failure during a "saveenv" operation.

+         Also this config changes the binary environment structure handling
+         which is used by env import/export commands which are independent of
+         storing variables to redundant location on a non volatile device.

 
 config ENV_FAT_INTERFACE
        string "Name of the block device for the environment"
 
 config ENV_FAT_INTERFACE
        string "Name of the block device for the environment"


@@ -421,7 +445,7 @@ config ENV_FAT_DEVICE_AND_PART
        string "Device and partition for where to store the environemt in FAT"
        depends on ENV_IS_IN_FAT
        default "0:1" if TI_COMMON_CMD_OPTIONS
        string "Device and partition for where to store the environemt in FAT"
        depends on ENV_IS_IN_FAT
        default "0:1" if TI_COMMON_CMD_OPTIONS

-       default "0:auto" if ARCH_ZYNQMP
+       default "0:auto" if ARCH_ZYNQ || ARCH_ZYNQMP || ARCH_VERSAL

        default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
        default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
        default "0" if ARCH_AT91
        default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
        default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
        default "0" if ARCH_AT91


@@ -452,6 +476,14 @@ config ENV_FAT_FILE
          It's a string of the FAT file name. This file use to store the
          environment.
 
          It's a string of the FAT file name. This file use to store the
          environment.
 

+config ENV_FAT_FILE_REDUND
+       string "Name of the FAT file to use for the environment"
+       depends on ENV_IS_IN_FAT && SYS_REDUNDAND_ENVIRONMENT
+       default "uboot-redund.env"
+       help
+         It's a string of the FAT file name. This file use to store the
+         redundant environment.
+

 config ENV_EXT4_INTERFACE
        string "Name of the block device for the environment"
        depends on ENV_IS_IN_EXT4
 config ENV_EXT4_INTERFACE
        string "Name of the block device for the environment"
        depends on ENV_IS_IN_EXT4


@@ -476,10 +508,14 @@ config ENV_EXT4_DEVICE_AND_PART
                           If none, first valid partition in device D. If no
                           partition table then means device D.
 
                           If none, first valid partition in device D. If no
                           partition table then means device D.
 

+         If ENV_EXT4_INTERFACE is set to "mmc" then device 'D' can be omitted,
+         leaving the string starting with a colon, and the boot device will
+         be used.
+

 config ENV_EXT4_FILE
        string "Name of the EXT4 file to use for the environment"
        depends on ENV_IS_IN_EXT4
 config ENV_EXT4_FILE
        string "Name of the EXT4 file to use for the environment"
        depends on ENV_IS_IN_EXT4

-       default "uboot.env"
+       default "/uboot.env"

        help
          It's a string of the EXT4 file name. This file use to store the
          environment (explicit path to the file)
        help
          It's a string of the EXT4 file name. This file use to store the
          environment (explicit path to the file)


@@ -520,6 +556,7 @@ config ENV_OFFSET_REDUND
        hex "Redundant environment offset"
        depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
                    ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
        hex "Redundant environment offset"
        depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
                    ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT

+       default 0

        help
          Offset from the start of the device (or partition) of the redundant
          environment location.
        help
          Offset from the start of the device (or partition) of the redundant
          environment location.


@@ -577,6 +614,25 @@ config SYS_RELOC_GD_ENV_ADDR
          Relocate the early env_addr pointer so we know it is not inside
          the binary. Some systems need this and for the rest, it doesn't hurt.
 
          Relocate the early env_addr pointer so we know it is not inside
          the binary. Some systems need this and for the rest, it doesn't hurt.
 

+config SYS_MMC_ENV_DEV
+       int "mmc device number"
+       depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT || SYS_LS_PPA_FW_IN_MMC || \
+               CMD_MVEBU_BUBT || FMAN_ENET || QE
+       default 0
+       help
+         MMC device number on the platform where the environment is stored.
+
+config SYS_MMC_ENV_PART
+       int "mmc partition number"
+       depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT
+       default 0
+       help
+         MMC hardware partition device number on the platform where the
+         environment is stored.  Note that this is not related to any software
+         defined partition table but instead if we are in the user area, which is
+         partition 0 or the first boot partition, which is 1 or some other defined
+         partition.
+

 config USE_DEFAULT_ENV_FILE
        bool "Create default environment from file"
        help
 config USE_DEFAULT_ENV_FILE
        bool "Create default environment from file"
        help


@@ -614,6 +670,41 @@ config DELAY_ENVIRONMENT
          later by U-Boot code. With CONFIG_OF_CONTROL this is instead
          controlled by the value of /config/load-environment.
 
          later by U-Boot code. With CONFIG_OF_CONTROL this is instead
          controlled by the value of /config/load-environment.
 

+config ENV_IMPORT_FDT
+       bool "Amend environment by FDT properties"
+       depends on OF_CONTROL
+       help
+         If selected, after the environment has been loaded from its
+         persistent location, the "env_fdt_path" variable is looked
+         up and used as a path to a node in the control DTB. The
+         property/value pairs in that node is then used to update the
+         run-time environment. This can be useful to use the same
+         U-Boot binary with different board variants.
+
+config ENV_FDT_PATH
+       string "Default value for env_fdt_path variable"
+       depends on ENV_IMPORT_FDT
+       default "/config/environment"
+       help
+         The initial value of the env_fdt_path variable.
+
+config ENV_APPEND
+       bool "Always append the environment with new data"
+       default n
+       help
+         If defined, the environment hash table is only ever appended with new
+         data, but the existing hash table can never be dropped and reloaded
+         with newly imported data. This may be used in combination with static
+         flags to e.g. to protect variables which must not be modified.
+
+config ENV_WRITEABLE_LIST
+       bool "Permit write access only to listed variables"
+       default n
+       help
+         If defined, only environment variables which explicitly set the 'w'
+         writeable flag can be written and modified at runtime. No variables
+         can be otherwise created, written or imported into the environment.
+

 config ENV_ACCESS_IGNORE_FORCE
        bool "Block forced environment operations"
        default n
 config ENV_ACCESS_IGNORE_FORCE
        bool "Block forced environment operations"
        default n


@@ -736,4 +827,13 @@ config TPL_ENV_IS_IN_FLASH
 
 endif
 
 
 endif
 

+config VERSION_VARIABLE
+       bool "Add a 'ver' environment variable with the U-Boot version"
+       help
+         If this variable is defined, an environment variable
+         named "ver" is created by U-Boot showing the U-Boot
+         version as printed by the "version" command.
+         Any change to this variable will be reverted at the
+         next reset.
+

 endmenu
 endmenu