1menu "Environment" 2 3config ENV_IS_NOWHERE 4 bool "Environment is not stored" 5 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \ 6 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \ 7 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \ 8 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \ 9 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \ 10 !ENV_IS_IN_UBI && !ENV_IS_IN_UFS 11 help 12 Define this if you don't want to or can't have an environment stored 13 on a storage medium. In this case the environment will still exist 14 while U-Boot is running, but once U-Boot exits it will not be 15 stored. U-Boot will therefore always start up with a default 16 environment. 17 18config ENV_IS_IN_EEPROM 19 bool "Environment in EEPROM" 20 depends on !CHAIN_OF_TRUST 21 help 22 Use this if you have an EEPROM or similar serial access 23 device and a driver for it. 24 25 - CONFIG_ENV_OFFSET: 26 - CONFIG_ENV_SIZE: 27 28 These two #defines specify the offset and size of the 29 environment area within the total memory of your EEPROM. 30 31 Note that we consider the length of the address field to 32 still be one byte because the extra address bits are hidden 33 in the chip address. 34 35 - CONFIG_ENV_EEPROM_IS_ON_I2C 36 define this, if you have I2C and SPI activated, and your 37 EEPROM, which holds the environment, is on the I2C bus. 38 39 - CONFIG_I2C_ENV_EEPROM_BUS 40 if you have an Environment on an EEPROM reached over 41 I2C muxes, you can define here, how to reach this 42 EEPROM. For example: 43 44 #define CONFIG_I2C_ENV_EEPROM_BUS 1 45 46 EEPROM which holds the environment, is reached over 47 a pca9547 i2c mux with address 0x70, channel 3. 48 49config ENV_IS_IN_FAT 50 bool "Environment is in a FAT filesystem" 51 depends on !CHAIN_OF_TRUST 52 default y if ARCH_BCM283X 53 default y if ARCH_SUNXI && MMC 54 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS 55 select FS_FAT 56 select FAT_WRITE 57 help 58 Define this if you want to use the FAT file system for the environment. 59 60config ENV_IS_IN_EXT4 61 bool "Environment is in a EXT4 filesystem" 62 depends on !CHAIN_OF_TRUST 63 select EXT4_WRITE 64 help 65 Define this if you want to use the EXT4 file system for the environment. 66 67config ENV_IS_IN_FLASH 68 bool "Environment in flash memory" 69 depends on !CHAIN_OF_TRUST 70 default y if ARCH_CINTEGRATOR 71 default y if ARCH_INTEGRATOR_CP 72 default y if M548x || M547x || M5282 || MCF547x_8x 73 default y if MCF532x || MCF52x2 74 default y if MPC86xx || MPC83xx 75 default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641 76 default y if SH && !CPU_SH4 77 help 78 Define this if you have a flash device which you want to use for the 79 environment. 80 81 a) The environment occupies one whole flash sector, which is 82 "embedded" in the text segment with the U-Boot code. This 83 happens usually with "bottom boot sector" or "top boot 84 sector" type flash chips, which have several smaller 85 sectors at the start or the end. For instance, such a 86 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In 87 such a case you would place the environment in one of the 88 4 kB sectors - with U-Boot code before and after it. With 89 "top boot sector" type flash chips, you would put the 90 environment in one of the last sectors, leaving a gap 91 between U-Boot and the environment. 92 93 CONFIG_ENV_OFFSET: 94 95 Offset of environment data (variable area) to the 96 beginning of flash memory; for instance, with bottom boot 97 type flash chips the second sector can be used: the offset 98 for this sector is given here. 99 100 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE. 101 102 CONFIG_ENV_ADDR: 103 104 This is just another way to specify the start address of 105 the flash sector containing the environment (instead of 106 CONFIG_ENV_OFFSET). 107 108 CONFIG_ENV_SECT_SIZE: 109 110 Size of the sector containing the environment. 111 112 113 b) Sometimes flash chips have few, equal sized, BIG sectors. 114 In such a case you don't want to spend a whole sector for 115 the environment. 116 117 CONFIG_ENV_SIZE: 118 119 If you use this in combination with CONFIG_ENV_IS_IN_FLASH 120 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part 121 of this flash sector for the environment. This saves 122 memory for the RAM copy of the environment. 123 124 It may also save flash memory if you decide to use this 125 when your environment is "embedded" within U-Boot code, 126 since then the remainder of the flash sector could be used 127 for U-Boot code. It should be pointed out that this is 128 STRONGLY DISCOURAGED from a robustness point of view: 129 updating the environment in flash makes it always 130 necessary to erase the WHOLE sector. If something goes 131 wrong before the contents has been restored from a copy in 132 RAM, your target system will be dead. 133 134 CONFIG_ENV_ADDR_REDUND 135 136 These settings describe a second storage area used to hold 137 a redundant copy of the environment data, so that there is 138 a valid backup copy in case there is a power failure during 139 a "saveenv" operation. 140 141 BE CAREFUL! Any changes to the flash layout, and some changes to the 142 source code will make it necessary to adapt <board>/u-boot.lds* 143 accordingly! 144 145config ENV_IS_IN_MMC 146 bool "Environment in an MMC device" 147 depends on !CHAIN_OF_TRUST 148 depends on MMC 149 default y if ARCH_EXYNOS4 150 default y if MX6SX || MX7D 151 default y if TEGRA30 || TEGRA124 152 default y if TEGRA_ARMV8_COMMON 153 help 154 Define this if you have an MMC device which you want to use for the 155 environment. 156 157 CONFIG_SYS_MMC_ENV_DEV: 158 159 Specifies which MMC device the environment is stored in. 160 161 CONFIG_SYS_MMC_ENV_PART (optional): 162 163 Specifies which MMC partition the environment is stored in. If not 164 set, defaults to partition 0, the user area. Common values might be 165 1 (first MMC boot partition), 2 (second MMC boot partition). 166 167 CONFIG_ENV_OFFSET: 168 CONFIG_ENV_SIZE: 169 170 These two #defines specify the offset and size of the environment 171 area within the specified MMC device. 172 173 If offset is positive (the usual case), it is treated as relative to 174 the start of the MMC partition. If offset is negative, it is treated 175 as relative to the end of the MMC partition. This can be useful if 176 your board may be fitted with different MMC devices, which have 177 different sizes for the MMC partitions, and you always want the 178 environment placed at the very end of the partition, to leave the 179 maximum possible space before it, to store other data. 180 181 These two values are in units of bytes, but must be aligned to an 182 MMC sector boundary. 183 184 CONFIG_ENV_OFFSET_REDUND (optional): 185 186 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to 187 hold a redundant copy of the environment data. This provides a 188 valid backup copy in case the other copy is corrupted, e.g. due 189 to a power failure during a "saveenv" operation. 190 191 This value may also be positive or negative; this is handled in the 192 same way as CONFIG_ENV_OFFSET. 193 194 This value is also in units of bytes, but must also be aligned to 195 an MMC sector boundary. 196 197config ENV_IS_IN_UFS 198 bool "Environment in an UFS device" 199 depends on !CHAIN_OF_TRUST 200 depends on UFS 201 help 202 Define this if you have an UFS device which you want to use for the 203 environment. 204 205config ENV_IS_IN_NAND 206 bool "Environment in a NAND device" 207 depends on !CHAIN_OF_TRUST 208 help 209 Define this if you have a NAND device which you want to use for the 210 environment. 211 212 - CONFIG_ENV_OFFSET: 213 - CONFIG_ENV_SIZE: 214 215 These two #defines specify the offset and size of the environment 216 area within the first NAND device. CONFIG_ENV_OFFSET must be 217 aligned to an erase block boundary. 218 219 - CONFIG_ENV_OFFSET_REDUND (optional): 220 221 This setting describes a second storage area of CONFIG_ENV_SIZE 222 size used to hold a redundant copy of the environment data, so 223 that there is a valid backup copy in case there is a power failure 224 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be 225 aligned to an erase block boundary. 226 227 - CONFIG_ENV_RANGE (optional): 228 229 Specifies the length of the region in which the environment 230 can be written. This should be a multiple of the NAND device's 231 block size. Specifying a range with more erase blocks than 232 are needed to hold CONFIG_ENV_SIZE allows bad blocks within 233 the range to be avoided. 234 235 - CONFIG_ENV_OFFSET_OOB (optional): 236 237 Enables support for dynamically retrieving the offset of the 238 environment from block zero's out-of-band data. The 239 "nand env.oob" command can be used to record this offset. 240 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when 241 using CONFIG_ENV_OFFSET_OOB. 242 243config ENV_IS_IN_NVRAM 244 bool "Environment in a non-volatile RAM" 245 depends on !CHAIN_OF_TRUST 246 help 247 Define this if you have some non-volatile memory device 248 (NVRAM, battery buffered SRAM) which you want to use for the 249 environment. 250 251 - CONFIG_ENV_ADDR: 252 - CONFIG_ENV_SIZE: 253 254 These two #defines are used to determine the memory area you 255 want to use for environment. It is assumed that this memory 256 can just be read and written to, without any special 257 provision. 258 259config ENV_IS_IN_ONENAND 260 bool "Environment is in OneNAND" 261 depends on !CHAIN_OF_TRUST 262 help 263 Define this if you want to put your local device's environment in 264 OneNAND. 265 266 - CONFIG_ENV_ADDR: 267 - CONFIG_ENV_SIZE: 268 269 These two #defines are used to determine the device range you 270 want to use for environment. It is assumed that this memory 271 can just be read and written to, without any special 272 provision. 273 274config ENV_IS_IN_REMOTE 275 bool "Environment is in remote memory space" 276 depends on !CHAIN_OF_TRUST 277 help 278 Define this if you have a remote memory space which you 279 want to use for the local device's environment. 280 281 - CONFIG_ENV_ADDR: 282 - CONFIG_ENV_SIZE: 283 284 These two #defines specify the address and size of the 285 environment area within the remote memory space. The 286 local device can get the environment from remote memory 287 space by SRIO or PCIE links. 288 289config ENV_IS_IN_SPI_FLASH 290 bool "Environment is in SPI flash" 291 depends on !CHAIN_OF_TRUST && SPI || HIFMC 292 default y if ARMADA_XP 293 default y if INTEL_BAYTRAIL 294 default y if INTEL_BRASWELL 295 default y if INTEL_BROADWELL 296 default y if NORTHBRIDGE_INTEL_IVYBRIDGE 297 default y if INTEL_QUARK 298 default y if INTEL_QUEENSBAY 299 help 300 Define this if you have a SPI Flash memory device which you 301 want to use for the environment. 302 303 - CONFIG_ENV_OFFSET: 304 - CONFIG_ENV_SIZE: 305 306 These two #defines specify the offset and size of the 307 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be 308 aligned to an erase sector boundary. 309 310 - CONFIG_ENV_SECT_SIZE: 311 312 Define the SPI flash's sector size. 313 314 - CONFIG_ENV_OFFSET_REDUND (optional): 315 316 This setting describes a second storage area of CONFIG_ENV_SIZE 317 size used to hold a redundant copy of the environment data, so 318 that there is a valid backup copy in case there is a power failure 319 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be 320 aligned to an erase sector boundary. 321 322config USE_ENV_SPI_BUS 323 bool "SPI flash bus for environment" 324 depends on ENV_IS_IN_SPI_FLASH 325 help 326 Force the SPI bus for environment. 327 If not defined, use CONFIG_SF_DEFAULT_BUS. 328 329config ENV_SPI_BUS 330 int "Value of SPI flash bus for environment" 331 depends on USE_ENV_SPI_BUS 332 help 333 Value the SPI bus and chip select for environment. 334 335config USE_ENV_SPI_CS 336 bool "SPI flash chip select for environment" 337 depends on ENV_IS_IN_SPI_FLASH 338 help 339 Force the SPI chip select for environment. 340 If not defined, use CONFIG_SF_DEFAULT_CS. 341 342config ENV_SPI_CS 343 int "Value of SPI flash chip select for environment" 344 depends on USE_ENV_SPI_CS 345 help 346 Value of the SPI chip select for environment. 347 348config USE_ENV_SPI_MAX_HZ 349 bool "SPI flash max frequency for environment" 350 depends on ENV_IS_IN_SPI_FLASH 351 help 352 Force the SPI max work clock for environment. 353 If not defined, use CONFIG_SF_DEFAULT_SPEED. 354 355config ENV_SPI_MAX_HZ 356 int "Value of SPI flash max frequency for environment" 357 depends on USE_ENV_SPI_MAX_HZ 358 help 359 Value of the SPI max work clock for environment. 360 361config USE_ENV_SPI_MODE 362 bool "SPI flash mode for environment" 363 depends on ENV_IS_IN_SPI_FLASH 364 help 365 Force the SPI work mode for environment. 366 367config ENV_SPI_MODE 368 hex "Value of SPI flash work mode for environment" 369 depends on USE_ENV_SPI_MODE 370 help 371 Value of the SPI work mode for environment. 372 See include/spi.h for value. 373 374config ENV_IS_IN_UBI 375 bool "Environment in a UBI volume" 376 depends on !CHAIN_OF_TRUST 377 depends on MTD_UBI 378 depends on CMD_UBI 379 help 380 Define this if you have an UBI volume that you want to use for the 381 environment. This has the benefit of wear-leveling the environment 382 accesses, which is important on NAND. 383 384 - CONFIG_ENV_UBI_PART: 385 386 Define this to a string that is the mtd partition containing the UBI. 387 388 - CONFIG_ENV_UBI_VOLUME: 389 390 Define this to the name of the volume that you want to store the 391 environment in. 392 393 - CONFIG_ENV_UBI_VOLUME_REDUND: 394 395 Define this to the name of another volume to store a second copy of 396 the environment in. This will enable redundant environments in UBI. 397 It is assumed that both volumes are in the same MTD partition. 398 399config SYS_REDUNDAND_ENVIRONMENT 400 bool "Enable redundant environment support" 401 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \ 402 ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI 403 help 404 Normally, the environemt is stored in a single location. By 405 selecting this option, you can then define where to hold a redundant 406 copy of the environment data, so that there is a valid backup copy in 407 case there is a power failure during a "saveenv" operation. 408 409config ENV_FAT_INTERFACE 410 string "Name of the block device for the environment" 411 depends on ENV_IS_IN_FAT 412 default "mmc" if ARCH_SUNXI 413 default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91 414 help 415 Define this to a string that is the name of the block device. 416 417config ENV_FAT_DEVICE_AND_PART 418 string "Device and partition for where to store the environemt in FAT" 419 depends on ENV_IS_IN_FAT 420 default "0:1" if TI_COMMON_CMD_OPTIONS 421 default "0:auto" if ARCH_ZYNQMP 422 default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1 423 default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1 424 default "0" if ARCH_AT91 425 help 426 Define this to a string to specify the partition of the device. It can 427 be as following: 428 429 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1) 430 - "D:P": device D partition P. Error occurs if device D has no 431 partition table. 432 - "D:0": device D. 433 - "D" or "D:": device D partition 1 if device D has partition 434 table, or the whole device D if has no partition 435 table. 436 - "D:auto": first partition in device D with bootable flag set. 437 If none, first valid partition in device D. If no 438 partition table then means device D. 439 440config ENV_FAT_FILE 441 string "Name of the FAT file to use for the environment" 442 depends on ENV_IS_IN_FAT 443 default "uboot.env" 444 help 445 It's a string of the FAT file name. This file use to store the 446 environment. 447 448config ENV_EXT4_INTERFACE 449 string "Name of the block device for the environment" 450 depends on ENV_IS_IN_EXT4 451 help 452 Define this to a string that is the name of the block device. 453 454config ENV_EXT4_DEVICE_AND_PART 455 string "Device and partition for where to store the environemt in EXT4" 456 depends on ENV_IS_IN_EXT4 457 help 458 Define this to a string to specify the partition of the device. It can 459 be as following: 460 461 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1) 462 - "D:P": device D partition P. Error occurs if device D has no 463 partition table. 464 - "D:0": device D. 465 - "D" or "D:": device D partition 1 if device D has partition 466 table, or the whole device D if has no partition 467 table. 468 - "D:auto": first partition in device D with bootable flag set. 469 If none, first valid partition in device D. If no 470 partition table then means device D. 471 472config ENV_EXT4_FILE 473 string "Name of the EXT4 file to use for the environment" 474 depends on ENV_IS_IN_EXT4 475 default "uboot.env" 476 help 477 It's a string of the EXT4 file name. This file use to store the 478 environment (explicit path to the file) 479 480config ENV_ADDR 481 hex "Environment address" 482 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \ 483 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH 484 default 0x0 if ENV_IS_IN_SPI_FLASH 485 help 486 Offset from the start of the device (or partition) 487 488config ENV_ADDR_REDUND 489 hex "Redundant environment address" 490 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT 491 help 492 Offset from the start of the device (or partition) of the redundant 493 environment location. 494 495config ENV_OFFSET 496 hex "Environment offset" 497 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \ 498 ENV_IS_IN_SPI_FLASH 499 default 0x3f8000 if ARCH_ROCKCHIP 500 default 0x88000 if ARCH_SUNXI 501 default 0xE0000 if ARCH_ZYNQ 502 default 0x1E00000 if ARCH_ZYNQMP 503 default 0x7F40000 if ARCH_VERSAL 504 default 0 if ARC 505 default 0x140000 if ARCH_AT91 506 default 0x260000 if ARCH_OMAP2PLUS 507 help 508 Offset from the start of the device (or partition) 509 510config ENV_OFFSET_REDUND 511 hex "Redundant environment offset" 512 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \ 513 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT 514 help 515 Offset from the start of the device (or partition) of the redundant 516 environment location. 517 518config ENV_SIZE 519 hex "Environment Size" 520 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP 521 default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91 522 default 0x8000 if ARCH_ROCKCHIP || ARCH_ZYNQMP || ARCH_VERSAL 523 default 0x4000 if ARC 524 default 0x1f000 525 help 526 Size of the environment storage area 527 528config ENV_SECT_SIZE 529 hex "Environment Sector-Size" 530 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH 531 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL 532 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91 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