uboot/env/Kconfig
<<
>>
Prefs
   1menu "Environment"
   2
   3config ENV_OVERWRITE
   4        bool "Enable overwriting environment"
   5        help
   6          Use this to permit overriding of certain environmental variables
   7          like Ethernet and Serial
   8
   9config ENV_IS_NOWHERE
  10        bool "Environment is not stored"
  11        default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
  12                     !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
  13                     !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
  14                     !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
  15                     !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
  16                     !ENV_IS_IN_UBI
  17        help
  18          Define this if you don't want to or can't have an environment stored
  19          on a storage medium. In this case the environment will still exist
  20          while U-Boot is running, but once U-Boot exits it will not be
  21          stored. U-Boot will therefore always start up with a default
  22          environment.
  23
  24config ENV_IS_IN_EEPROM
  25        bool "Environment in EEPROM"
  26        depends on !CHAIN_OF_TRUST
  27        help
  28          Use this if you have an EEPROM or similar serial access
  29          device and a driver for it.
  30
  31          - CONFIG_ENV_OFFSET:
  32          - CONFIG_ENV_SIZE:
  33
  34          These two #defines specify the offset and size of the
  35          environment area within the total memory of your EEPROM.
  36
  37          Note that we consider the length of the address field to
  38          still be one byte because the extra address bits are hidden
  39          in the chip address.
  40
  41          - CONFIG_ENV_EEPROM_IS_ON_I2C
  42          define this, if you have I2C and SPI activated, and your
  43          EEPROM, which holds the environment, is on the I2C bus.
  44
  45          - CONFIG_I2C_ENV_EEPROM_BUS
  46          if you have an Environment on an EEPROM reached over
  47          I2C muxes, you can define here, how to reach this
  48          EEPROM. For example:
  49
  50          #define CONFIG_I2C_ENV_EEPROM_BUS       1
  51
  52          EEPROM which holds the environment, is reached over
  53          a pca9547 i2c mux with address 0x70, channel 3.
  54
  55config ENV_IS_IN_FAT
  56        bool "Environment is in a FAT filesystem"
  57        depends on !CHAIN_OF_TRUST
  58        default y if ARCH_BCM283X
  59        default y if ARCH_SUNXI && MMC
  60        default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
  61        select FS_FAT
  62        select FAT_WRITE
  63        help
  64          Define this if you want to use the FAT file system for the environment.
  65
  66config ENV_IS_IN_EXT4
  67        bool "Environment is in a EXT4 filesystem"
  68        depends on !CHAIN_OF_TRUST
  69        select EXT4_WRITE
  70        help
  71          Define this if you want to use the EXT4 file system for the environment.
  72
  73config ENV_IS_IN_FLASH
  74        bool "Environment in flash memory"
  75        depends on !CHAIN_OF_TRUST
  76        default y if ARCH_CINTEGRATOR
  77        default y if ARCH_INTEGRATOR_CP
  78        default y if M548x || M547x || M5282 || MCF547x_8x
  79        default y if MCF532x || MCF52x2
  80        default y if MPC86xx || MPC83xx
  81        default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
  82        default y if SH && !CPU_SH4
  83        help
  84          Define this if you have a flash device which you want to use for the
  85          environment.
  86
  87          a) The environment occupies one whole flash sector, which is
  88           "embedded" in the text segment with the U-Boot code. This
  89           happens usually with "bottom boot sector" or "top boot
  90           sector" type flash chips, which have several smaller
  91           sectors at the start or the end. For instance, such a
  92           layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  93           such a case you would place the environment in one of the
  94           4 kB sectors - with U-Boot code before and after it. With
  95           "top boot sector" type flash chips, you would put the
  96           environment in one of the last sectors, leaving a gap
  97           between U-Boot and the environment.
  98
  99          CONFIG_ENV_OFFSET:
 100
 101           Offset of environment data (variable area) to the
 102           beginning of flash memory; for instance, with bottom boot
 103           type flash chips the second sector can be used: the offset
 104           for this sector is given here.
 105
 106           CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
 107
 108          CONFIG_ENV_ADDR:
 109
 110           This is just another way to specify the start address of
 111           the flash sector containing the environment (instead of
 112           CONFIG_ENV_OFFSET).
 113
 114          CONFIG_ENV_SECT_SIZE:
 115
 116           Size of the sector containing the environment.
 117
 118
 119          b) Sometimes flash chips have few, equal sized, BIG sectors.
 120           In such a case you don't want to spend a whole sector for
 121           the environment.
 122
 123          CONFIG_ENV_SIZE:
 124
 125           If you use this in combination with CONFIG_ENV_IS_IN_FLASH
 126           and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
 127           of this flash sector for the environment. This saves
 128           memory for the RAM copy of the environment.
 129
 130           It may also save flash memory if you decide to use this
 131           when your environment is "embedded" within U-Boot code,
 132           since then the remainder of the flash sector could be used
 133           for U-Boot code. It should be pointed out that this is
 134           STRONGLY DISCOURAGED from a robustness point of view:
 135           updating the environment in flash makes it always
 136           necessary to erase the WHOLE sector. If something goes
 137           wrong before the contents has been restored from a copy in
 138           RAM, your target system will be dead.
 139
 140          CONFIG_ENV_ADDR_REDUND
 141
 142           These settings describe a second storage area used to hold
 143           a redundant copy of the environment data, so that there is
 144           a valid backup copy in case there is a power failure during
 145           a "saveenv" operation.
 146
 147          BE CAREFUL! Any changes to the flash layout, and some changes to the
 148          source code will make it necessary to adapt <board>/u-boot.lds*
 149          accordingly!
 150
 151config ENV_IS_IN_MMC
 152        bool "Environment in an MMC device"
 153        depends on !CHAIN_OF_TRUST
 154        depends on MMC
 155        default y if ARCH_EXYNOS4
 156        default y if MX6SX || MX7D
 157        default y if TEGRA30 || TEGRA124
 158        default y if TEGRA_ARMV8_COMMON
 159        help
 160          Define this if you have an MMC device which you want to use for the
 161          environment.
 162
 163          CONFIG_SYS_MMC_ENV_DEV:
 164
 165          Specifies which MMC device the environment is stored in.
 166
 167          CONFIG_SYS_MMC_ENV_PART (optional):
 168
 169          Specifies which MMC partition the environment is stored in. If not
 170          set, defaults to partition 0, the user area. Common values might be
 171          1 (first MMC boot partition), 2 (second MMC boot partition).
 172
 173          CONFIG_ENV_OFFSET:
 174          CONFIG_ENV_SIZE:
 175
 176          These two #defines specify the offset and size of the environment
 177          area within the specified MMC device.
 178
 179          If offset is positive (the usual case), it is treated as relative to
 180          the start of the MMC partition. If offset is negative, it is treated
 181          as relative to the end of the MMC partition. This can be useful if
 182          your board may be fitted with different MMC devices, which have
 183          different sizes for the MMC partitions, and you always want the
 184          environment placed at the very end of the partition, to leave the
 185          maximum possible space before it, to store other data.
 186
 187          These two values are in units of bytes, but must be aligned to an
 188          MMC sector boundary.
 189
 190          CONFIG_ENV_OFFSET_REDUND (optional):
 191
 192          Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
 193          hold a redundant copy of the environment data. This provides a
 194          valid backup copy in case the other copy is corrupted, e.g. due
 195          to a power failure during a "saveenv" operation.
 196
 197          This value may also be positive or negative; this is handled in the
 198          same way as CONFIG_ENV_OFFSET.
 199
 200          This value is also in units of bytes, but must also be aligned to
 201          an MMC sector boundary.
 202
 203config ENV_IS_IN_NAND
 204        bool "Environment in a NAND device"
 205        depends on !CHAIN_OF_TRUST
 206        help
 207          Define this if you have a NAND device which you want to use for the
 208          environment.
 209
 210          - CONFIG_ENV_OFFSET:
 211          - CONFIG_ENV_SIZE:
 212
 213          These two #defines specify the offset and size of the environment
 214          area within the first NAND device.  CONFIG_ENV_OFFSET must be
 215          aligned to an erase block boundary.
 216
 217          - CONFIG_ENV_OFFSET_REDUND (optional):
 218
 219          This setting describes a second storage area of CONFIG_ENV_SIZE
 220          size used to hold a redundant copy of the environment data, so
 221          that there is a valid backup copy in case there is a power failure
 222          during a "saveenv" operation.  CONFIG_ENV_OFFSET_REDUND must be
 223          aligned to an erase block boundary.
 224
 225          - CONFIG_ENV_RANGE (optional):
 226
 227          Specifies the length of the region in which the environment
 228          can be written.  This should be a multiple of the NAND device's
 229          block size.  Specifying a range with more erase blocks than
 230          are needed to hold CONFIG_ENV_SIZE allows bad blocks within
 231          the range to be avoided.
 232
 233          - CONFIG_ENV_OFFSET_OOB (optional):
 234
 235          Enables support for dynamically retrieving the offset of the
 236          environment from block zero's out-of-band data.  The
 237          "nand env.oob" command can be used to record this offset.
 238          Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
 239          using CONFIG_ENV_OFFSET_OOB.
 240
 241config ENV_IS_IN_NVRAM
 242        bool "Environment in a non-volatile RAM"
 243        depends on !CHAIN_OF_TRUST
 244        help
 245          Define this if you have some non-volatile memory device
 246          (NVRAM, battery buffered SRAM) which you want to use for the
 247          environment.
 248
 249          - CONFIG_ENV_ADDR:
 250          - CONFIG_ENV_SIZE:
 251
 252          These two #defines are used to determine the memory area you
 253          want to use for environment. It is assumed that this memory
 254          can just be read and written to, without any special
 255          provision.
 256
 257config ENV_IS_IN_ONENAND
 258        bool "Environment is in OneNAND"
 259        depends on !CHAIN_OF_TRUST
 260        help
 261          Define this if you want to put your local device's environment in
 262          OneNAND.
 263
 264          - CONFIG_ENV_ADDR:
 265          - CONFIG_ENV_SIZE:
 266
 267          These two #defines are used to determine the device range you
 268          want to use for environment. It is assumed that this memory
 269          can just be read and written to, without any special
 270          provision.
 271
 272config ENV_IS_IN_REMOTE
 273        bool "Environment is in remote memory space"
 274        depends on !CHAIN_OF_TRUST
 275        help
 276          Define this if you have a remote memory space which you
 277          want to use for the local device's environment.
 278
 279          - CONFIG_ENV_ADDR:
 280          - CONFIG_ENV_SIZE:
 281
 282          These two #defines specify the address and size of the
 283          environment area within the remote memory space. The
 284          local device can get the environment from remote memory
 285          space by SRIO or PCIE links.
 286
 287config ENV_IS_IN_SPI_FLASH
 288        bool "Environment is in SPI flash"
 289        depends on !CHAIN_OF_TRUST && SPI
 290        default y if ARMADA_XP
 291        default y if INTEL_BAYTRAIL
 292        default y if INTEL_BRASWELL
 293        default y if INTEL_BROADWELL
 294        default y if NORTHBRIDGE_INTEL_IVYBRIDGE
 295        default y if INTEL_QUARK
 296        default y if INTEL_QUEENSBAY
 297        help
 298          Define this if you have a SPI Flash memory device which you
 299          want to use for the environment.
 300
 301          - CONFIG_ENV_OFFSET:
 302          - CONFIG_ENV_SIZE:
 303
 304          These two #defines specify the offset and size of the
 305          environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
 306          aligned to an erase sector boundary.
 307
 308          - CONFIG_ENV_SECT_SIZE:
 309
 310          Define the SPI flash's sector size.
 311
 312          - CONFIG_ENV_OFFSET_REDUND (optional):
 313
 314          This setting describes a second storage area of CONFIG_ENV_SIZE
 315          size used to hold a redundant copy of the environment data, so
 316          that there is a valid backup copy in case there is a power failure
 317          during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
 318          aligned to an erase sector boundary.
 319
 320config USE_ENV_SPI_BUS
 321        bool "SPI flash bus for environment"
 322        depends on ENV_IS_IN_SPI_FLASH
 323        help
 324          Force the SPI bus for environment.
 325          If not defined, use CONFIG_SF_DEFAULT_BUS.
 326
 327config ENV_SPI_BUS
 328        int "Value of SPI flash bus for environment"
 329        depends on USE_ENV_SPI_BUS
 330        help
 331          Value the SPI bus and chip select for environment.
 332
 333config USE_ENV_SPI_CS
 334        bool "SPI flash chip select for environment"
 335        depends on ENV_IS_IN_SPI_FLASH
 336        help
 337          Force the SPI chip select for environment.
 338          If not defined, use CONFIG_SF_DEFAULT_CS.
 339
 340config ENV_SPI_CS
 341        int "Value of SPI flash chip select for environment"
 342        depends on USE_ENV_SPI_CS
 343        help
 344          Value of the SPI chip select for environment.
 345
 346config USE_ENV_SPI_MAX_HZ
 347        bool "SPI flash max frequency for environment"
 348        depends on ENV_IS_IN_SPI_FLASH
 349        help
 350          Force the SPI max work clock for environment.
 351          If not defined, use CONFIG_SF_DEFAULT_SPEED.
 352
 353config ENV_SPI_MAX_HZ
 354        int "Value of SPI flash max frequency for environment"
 355        depends on USE_ENV_SPI_MAX_HZ
 356        help
 357          Value of the SPI max work clock for environment.
 358
 359config USE_ENV_SPI_MODE
 360        bool "SPI flash mode for environment"
 361        depends on ENV_IS_IN_SPI_FLASH
 362        help
 363          Force the SPI work mode for environment.
 364
 365config ENV_SPI_MODE
 366        hex "Value of SPI flash work mode for environment"
 367        depends on USE_ENV_SPI_MODE
 368        help
 369          Value of the SPI work mode for environment.
 370          See include/spi.h for value.
 371
 372config ENV_IS_IN_UBI
 373        bool "Environment in a UBI volume"
 374        depends on !CHAIN_OF_TRUST
 375        depends on MTD_UBI
 376        depends on CMD_UBI
 377        help
 378          Define this if you have an UBI volume that you want to use for the
 379          environment.  This has the benefit of wear-leveling the environment
 380          accesses, which is important on NAND.
 381
 382          - CONFIG_ENV_UBI_PART:
 383
 384          Define this to a string that is the mtd partition containing the UBI.
 385
 386          - CONFIG_ENV_UBI_VOLUME:
 387
 388          Define this to the name of the volume that you want to store the
 389          environment in.
 390
 391          - CONFIG_ENV_UBI_VOLUME_REDUND:
 392
 393          Define this to the name of another volume to store a second copy of
 394          the environment in.  This will enable redundant environments in UBI.
 395          It is assumed that both volumes are in the same MTD partition.
 396
 397config SYS_REDUNDAND_ENVIRONMENT
 398        bool "Enable redundant environment support"
 399        depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
 400                ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI
 401        help
 402          Normally, the environemt is stored in a single location.  By
 403          selecting this option, you can then define where to hold a redundant
 404          copy of the environment data, so that there is a valid backup copy in
 405          case there is a power failure during a "saveenv" operation.
 406
 407config ENV_FAT_INTERFACE
 408        string "Name of the block device for the environment"
 409        depends on ENV_IS_IN_FAT
 410        default "mmc" if ARCH_SUNXI
 411        default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91
 412        help
 413          Define this to a string that is the name of the block device.
 414
 415config ENV_FAT_DEVICE_AND_PART
 416        string "Device and partition for where to store the environemt in FAT"
 417        depends on ENV_IS_IN_FAT
 418        default "0:1" if TI_COMMON_CMD_OPTIONS
 419        default "0:auto" if ARCH_ZYNQMP
 420        default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
 421        default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
 422        default "0" if ARCH_AT91
 423        help
 424          Define this to a string to specify the partition of the device. It can
 425          be as following:
 426
 427            "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
 428               - "D:P": device D partition P. Error occurs if device D has no
 429                        partition table.
 430               - "D:0": device D.
 431               - "D" or "D:": device D partition 1 if device D has partition
 432                              table, or the whole device D if has no partition
 433                              table.
 434               - "D:auto": first partition in device D with bootable flag set.
 435                           If none, first valid partition in device D. If no
 436                           partition table then means device D.
 437
 438config ENV_FAT_FILE
 439        string "Name of the FAT file to use for the environment"
 440        depends on ENV_IS_IN_FAT
 441        default "uboot.env"
 442        help
 443          It's a string of the FAT file name. This file use to store the
 444          environment.
 445
 446config ENV_EXT4_INTERFACE
 447        string "Name of the block device for the environment"
 448        depends on ENV_IS_IN_EXT4
 449        help
 450          Define this to a string that is the name of the block device.
 451
 452config ENV_EXT4_DEVICE_AND_PART
 453        string "Device and partition for where to store the environemt in EXT4"
 454        depends on ENV_IS_IN_EXT4
 455        help
 456          Define this to a string to specify the partition of the device. It can
 457          be as following:
 458
 459            "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
 460               - "D:P": device D partition P. Error occurs if device D has no
 461                        partition table.
 462               - "D:0": device D.
 463               - "D" or "D:": device D partition 1 if device D has partition
 464                              table, or the whole device D if has no partition
 465                              table.
 466               - "D:auto": first partition in device D with bootable flag set.
 467                           If none, first valid partition in device D. If no
 468                           partition table then means device D.
 469
 470config ENV_EXT4_FILE
 471        string "Name of the EXT4 file to use for the environment"
 472        depends on ENV_IS_IN_EXT4
 473        default "uboot.env"
 474        help
 475          It's a string of the EXT4 file name. This file use to store the
 476          environment (explicit path to the file)
 477
 478config ENV_ADDR
 479        hex "Environment address"
 480        depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
 481                     ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
 482        default 0x0 if ENV_IS_IN_SPI_FLASH
 483        help
 484          Offset from the start of the device (or partition)
 485
 486config ENV_ADDR_REDUND
 487        hex "Redundant environment address"
 488        depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
 489        help
 490          Offset from the start of the device (or partition) of the redundant
 491          environment location.
 492
 493config ENV_OFFSET
 494        hex "Environment offset"
 495        depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
 496                    ENV_IS_IN_SPI_FLASH
 497        default 0x3f8000 if ARCH_ROCKCHIP
 498        default 0x88000 if ARCH_SUNXI
 499        default 0xE0000 if ARCH_ZYNQ
 500        default 0x1E00000 if ARCH_ZYNQMP
 501        default 0x7F40000 if ARCH_VERSAL
 502        default 0 if ARC
 503        default 0x140000 if ARCH_AT91
 504        default 0x260000 if ARCH_OMAP2PLUS
 505        default 0x1080000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
 506        help
 507          Offset from the start of the device (or partition)
 508
 509config ENV_OFFSET_REDUND
 510        hex "Redundant environment offset"
 511        depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
 512                    ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
 513        help
 514          Offset from the start of the device (or partition) of the redundant
 515          environment location.
 516
 517config ENV_SIZE
 518        hex "Environment Size"
 519        default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
 520        default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
 521        default 0x8000 if ARCH_ROCKCHIP || ARCH_ZYNQMP || ARCH_VERSAL
 522        default 0x4000 if ARC
 523        default 0x1f000
 524        help
 525          Size of the environment storage area
 526
 527config ENV_SECT_SIZE
 528        hex "Environment Sector-Size"
 529        depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
 530        default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL
 531        default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
 532        default 0x20000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
 533        help
 534          Size of the sector containing the environment.
 535
 536config ENV_UBI_PART
 537        string "UBI partition name"
 538        depends on ENV_IS_IN_UBI
 539        help
 540          MTD partition containing the UBI device
 541
 542config ENV_UBI_VOLUME
 543        string "UBI volume name"
 544        depends on ENV_IS_IN_UBI
 545        help
 546          Name of the volume that you want to store the environment in.
 547
 548config ENV_UBI_VOLUME_REDUND
 549        string "UBI redundant volume name"
 550        depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
 551        help
 552          Name of the redundant volume that you want to store the environment in.
 553
 554config ENV_UBI_VID_OFFSET
 555        int "ubi environment VID offset"
 556        depends on ENV_IS_IN_UBI
 557        default 0
 558        help
 559          UBI VID offset for environment. If 0, no custom VID offset is used.
 560
 561config SYS_RELOC_GD_ENV_ADDR
 562        bool "Relocate gd->en_addr"
 563        help
 564          Relocate the early env_addr pointer so we know it is not inside
 565          the binary. Some systems need this and for the rest, it doesn't hurt.
 566
 567config USE_DEFAULT_ENV_FILE
 568        bool "Create default environment from file"
 569        help
 570          Normally, the default environment is automatically generated
 571          based on the settings of various CONFIG_* options, as well
 572          as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
 573          you can instead define the entire default environment in an
 574          external file.
 575
 576config DEFAULT_ENV_FILE
 577        string "Path to default environment file"
 578        depends on USE_DEFAULT_ENV_FILE
 579        help
 580          The path containing the default environment. The format is
 581          the same as accepted by the mkenvimage tool: lines
 582          containing key=value pairs, blank lines and lines beginning
 583          with # are ignored.
 584
 585config ENV_VARS_UBOOT_RUNTIME_CONFIG
 586        bool "Add run-time information to the environment"
 587        help
 588          Enable this in order to add variables describing certain
 589          run-time determined information about the hardware to the
 590          environment.  These will be named board_name, board_rev.
 591
 592if SPL_ENV_SUPPORT
 593config SPL_ENV_IS_NOWHERE
 594        bool "SPL Environment is not stored"
 595        default y if ENV_IS_NOWHERE
 596        help
 597          Similar to ENV_IS_NOWHERE, used for SPL environment.
 598
 599config SPL_ENV_IS_IN_MMC
 600        bool "SPL Environment in an MMC device"
 601        depends on !SPL_ENV_IS_NOWHERE
 602        depends on ENV_IS_IN_MMC
 603        default y
 604        help
 605          Similar to ENV_IS_IN_MMC, used for SPL environment.
 606
 607config SPL_ENV_IS_IN_FAT
 608        bool "SPL Environment is in a FAT filesystem"
 609        depends on !SPL_ENV_IS_NOWHERE
 610        depends on ENV_IS_IN_FAT
 611        default y
 612        help
 613          Similar to ENV_IS_IN_FAT, used for SPL environment.
 614
 615config SPL_ENV_IS_IN_EXT4
 616        bool "SPL Environment is in a EXT4 filesystem"
 617        depends on !SPL_ENV_IS_NOWHERE
 618        depends on ENV_IS_IN_EXT4
 619        default y
 620        help
 621          Similar to ENV_IS_IN_EXT4, used for SPL environment.
 622
 623config SPL_ENV_IS_IN_NAND
 624        bool "SPL Environment in a NAND device"
 625        depends on !SPL_ENV_IS_NOWHERE
 626        depends on ENV_IS_IN_NAND
 627        default y
 628        help
 629          Similar to ENV_IS_IN_NAND, used for SPL environment.
 630
 631config SPL_ENV_IS_IN_SPI_FLASH
 632        bool "SPL Environment is in SPI flash"
 633        depends on !SPL_ENV_IS_NOWHERE
 634        depends on ENV_IS_IN_SPI_FLASH
 635        default y
 636        help
 637          Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
 638
 639config SPL_ENV_IS_IN_FLASH
 640        bool "SPL Environment in flash memory"
 641        depends on !SPL_ENV_IS_NOWHERE
 642        depends on ENV_IS_IN_FLASH
 643        default y
 644        help
 645          Similar to ENV_IS_IN_FLASH, used for SPL environment.
 646
 647endif
 648
 649if TPL_ENV_SUPPORT
 650
 651config TPL_ENV_IS_NOWHERE
 652        bool "TPL Environment is not stored"
 653        default y if ENV_IS_NOWHERE
 654        help
 655          Similar to ENV_IS_NOWHERE, used for TPL environment.
 656
 657config TPL_ENV_IS_IN_MMC
 658        bool "TPL Environment in an MMC device"
 659        depends on !TPL_ENV_IS_NOWHERE
 660        depends on ENV_IS_IN_MMC
 661        default y
 662        help
 663          Similar to ENV_IS_IN_MMC, used for TPL environment.
 664
 665config TPL_ENV_IS_IN_FAT
 666        bool "TPL Environment is in a FAT filesystem"
 667        depends on !TPL_ENV_IS_NOWHERE
 668        depends on ENV_IS_IN_FAT
 669        default y
 670        help
 671          Similar to ENV_IS_IN_FAT, used for TPL environment.
 672
 673config TPL_ENV_IS_IN_EXT4
 674        bool "TPL Environment is in a EXT4 filesystem"
 675        depends on !TPL_ENV_IS_NOWHERE
 676        depends on ENV_IS_IN_EXT4
 677        default y
 678        help
 679          Similar to ENV_IS_IN_EXT4, used for TPL environment.
 680
 681config TPL_ENV_IS_IN_NAND
 682        bool "TPL Environment in a NAND device"
 683        depends on !TPL_ENV_IS_NOWHERE
 684        depends on ENV_IS_IN_NAND
 685        default y
 686        help
 687          Similar to ENV_IS_IN_NAND, used for TPL environment.
 688
 689config TPL_ENV_IS_IN_SPI_FLASH
 690        bool "TPL Environment is in SPI flash"
 691        depends on !TPL_ENV_IS_NOWHERE
 692        depends on ENV_IS_IN_SPI_FLASH
 693        default y
 694        help
 695          Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
 696
 697config TPL_ENV_IS_IN_FLASH
 698        bool "TPL Environment in flash memory"
 699        depends on !TPL_ENV_IS_NOWHERE
 700        depends on ENV_IS_IN_FLASH
 701        default y
 702        help
 703          Similar to ENV_IS_IN_FLASH, used for TPL environment.
 704
 705endif
 706
 707endmenu
 708