7 string "Environment file to use"
10 This sets the basename to use to generate the default environment.
11 This a text file as described in doc/usage/environment.rst
13 The file must be in the board directory and have a .env extension, so
14 the resulting filename is typically
15 board/<vendor>/<board>/<CONFIG_ENV_SOURCE_FILE>.env
17 If the file is not present, an error is produced.
19 If this CONFIG is empty, U-Boot uses CONFIG SYS_BOARD as a default, if
20 the file board/<vendor>/<board>/<SYS_BOARD>.env exists. Otherwise the
21 environment is assumed to come from the ad-hoc
22 CONFIG_EXTRA_ENV_SETTINGS #define
25 def_bool y if CMD_SAVEENV
28 bool "Enable overwriting environment"
30 Use this to permit overriding of certain environmental variables
31 like Ethernet and Serial
33 config ENV_MIN_ENTRIES
34 int "Minimum number of entries in the environment hashtable"
37 Minimum number of entries in the hash table that is used internally
38 to store the environment settings.
40 config ENV_MAX_ENTRIES
41 int "Maximumm number of entries in the environment hashtable"
44 Maximum number of entries in the hash table that is used internally
45 to store the environment settings. The default setting is supposed to
46 be generous and should work in most cases. This setting can be used
47 to tune behaviour; see lib/hashtable.c for details.
50 bool "Environment is not stored"
51 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
52 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
53 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
54 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
55 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
58 Define this if you don't want to or can't have an environment stored
59 on a storage medium. In this case the environment will still exist
60 while U-Boot is running, but once U-Boot exits it will not be
61 stored. U-Boot will therefore always start up with a default
64 config ENV_IS_IN_EEPROM
65 bool "Environment in EEPROM"
66 depends on !CHAIN_OF_TRUST
68 Use this if you have an EEPROM or similar serial access
69 device and a driver for it.
74 These two #defines specify the offset and size of the
75 environment area within the total memory of your EEPROM.
77 Note that we consider the length of the address field to
78 still be one byte because the extra address bits are hidden
81 EEPROM which holds the environment, is reached over
82 a pca9547 i2c mux with address 0x70, channel 3.
85 bool "Environment is in a FAT filesystem"
86 depends on !CHAIN_OF_TRUST
87 default y if ARCH_BCM283X
88 default y if ARCH_SUNXI && MMC
89 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
93 Define this if you want to use the FAT file system for the environment.
96 bool "Environment is in a EXT4 filesystem"
97 depends on !CHAIN_OF_TRUST
101 Define this if you want to use the EXT4 file system for the environment.
103 config ENV_IS_IN_FLASH
104 bool "Environment in flash memory"
105 depends on !CHAIN_OF_TRUST
106 default y if ARCH_CINTEGRATOR
107 default y if ARCH_INTEGRATOR_CP
108 default y if M548x || M547x || M5282
109 default y if MCF532x || MCF52x2
110 default y if MPC86xx || MPC83xx
111 default y if ARCH_MPC8548
112 default y if SH && !CPU_SH4
114 Define this if you have a flash device which you want to use for the
117 a) The environment occupies one whole flash sector, which is
118 "embedded" in the text segment with the U-Boot code. This
119 happens usually with "bottom boot sector" or "top boot
120 sector" type flash chips, which have several smaller
121 sectors at the start or the end. For instance, such a
122 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
123 such a case you would place the environment in one of the
124 4 kB sectors - with U-Boot code before and after it. With
125 "top boot sector" type flash chips, you would put the
126 environment in one of the last sectors, leaving a gap
127 between U-Boot and the environment.
131 Offset of environment data (variable area) to the
132 beginning of flash memory; for instance, with bottom boot
133 type flash chips the second sector can be used: the offset
134 for this sector is given here.
136 CONFIG_ENV_OFFSET is used relative to CFG_SYS_FLASH_BASE.
140 This is just another way to specify the start address of
141 the flash sector containing the environment (instead of
144 CONFIG_ENV_SECT_SIZE:
146 Size of the sector containing the environment.
149 b) Sometimes flash chips have few, equal sized, BIG sectors.
150 In such a case you don't want to spend a whole sector for
155 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
156 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
157 of this flash sector for the environment. This saves
158 memory for the RAM copy of the environment.
160 It may also save flash memory if you decide to use this
161 when your environment is "embedded" within U-Boot code,
162 since then the remainder of the flash sector could be used
163 for U-Boot code. It should be pointed out that this is
164 STRONGLY DISCOURAGED from a robustness point of view:
165 updating the environment in flash makes it always
166 necessary to erase the WHOLE sector. If something goes
167 wrong before the contents has been restored from a copy in
168 RAM, your target system will be dead.
170 CONFIG_ENV_ADDR_REDUND
172 These settings describe a second storage area used to hold
173 a redundant copy of the environment data, so that there is
174 a valid backup copy in case there is a power failure during
175 a "saveenv" operation.
177 BE CAREFUL! Any changes to the flash layout, and some changes to the
178 source code will make it necessary to adapt <board>/u-boot.lds*
182 bool "Environment in an MMC device"
183 depends on !CHAIN_OF_TRUST
185 default y if ARCH_EXYNOS4
186 default y if MX6SX || MX7D
187 default y if TEGRA30 || TEGRA124
188 default y if TEGRA_ARMV8_COMMON
190 Define this if you have an MMC device which you want to use for the
193 CONFIG_SYS_MMC_ENV_DEV:
195 Specifies which MMC device the environment is stored in.
197 CONFIG_SYS_MMC_ENV_PART (optional):
199 Specifies which MMC partition the environment is stored in. If not
200 set, defaults to partition 0, the user area. Common values might be
201 1 (first MMC boot partition), 2 (second MMC boot partition).
206 These two #defines specify the offset and size of the environment
207 area within the specified MMC device.
209 If offset is positive (the usual case), it is treated as relative to
210 the start of the MMC partition. If offset is negative, it is treated
211 as relative to the end of the MMC partition. This can be useful if
212 your board may be fitted with different MMC devices, which have
213 different sizes for the MMC partitions, and you always want the
214 environment placed at the very end of the partition, to leave the
215 maximum possible space before it, to store other data.
217 These two values are in units of bytes, but must be aligned to an
220 CONFIG_ENV_OFFSET_REDUND (optional):
222 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
223 hold a redundant copy of the environment data. This provides a
224 valid backup copy in case the other copy is corrupted, e.g. due
225 to a power failure during a "saveenv" operation.
227 This value may also be positive or negative; this is handled in the
228 same way as CONFIG_ENV_OFFSET.
230 In case CONFIG_SYS_MMC_ENV_PART is 1 (i.e. environment in eMMC boot
231 partition) then setting CONFIG_ENV_OFFSET_REDUND to the same value
232 as CONFIG_ENV_OFFSET makes use of the second eMMC boot partition for
233 the redundant environment copy.
235 This value is also in units of bytes, but must also be aligned to
236 an MMC sector boundary.
238 config ENV_IS_IN_NAND
239 bool "Environment in a NAND device"
240 depends on !CHAIN_OF_TRUST
242 Define this if you have a NAND device which you want to use for the
248 These two #defines specify the offset and size of the environment
249 area within the first NAND device. CONFIG_ENV_OFFSET must be
250 aligned to an erase block boundary.
252 - CONFIG_ENV_OFFSET_REDUND (optional):
254 This setting describes a second storage area of CONFIG_ENV_SIZE
255 size used to hold a redundant copy of the environment data, so
256 that there is a valid backup copy in case there is a power failure
257 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
258 aligned to an erase block boundary.
260 - CONFIG_ENV_OFFSET_OOB (optional):
262 Enables support for dynamically retrieving the offset of the
263 environment from block zero's out-of-band data. The
264 "nand env.oob" command can be used to record this offset.
265 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
266 using CONFIG_ENV_OFFSET_OOB.
269 hex "Length of the region in which the environment can be written"
270 depends on ENV_IS_IN_NAND
271 range ENV_SIZE 0x7fffffff
274 This should be a multiple of the NAND device's block size.
275 Specifying a range with more erase blocks than are needed to hold
276 CONFIG_ENV_SIZE allows bad blocks within the range to be avoided.
278 config ENV_IS_IN_NVRAM
279 bool "Environment in a non-volatile RAM"
280 depends on !CHAIN_OF_TRUST
282 Define this if you have some non-volatile memory device
283 (NVRAM, battery buffered SRAM) which you want to use for the
289 These two #defines are used to determine the memory area you
290 want to use for environment. It is assumed that this memory
291 can just be read and written to, without any special
294 config ENV_IS_IN_ONENAND
295 bool "Environment is in OneNAND"
296 depends on !CHAIN_OF_TRUST
298 Define this if you want to put your local device's environment in
304 These two #defines are used to determine the device range you
305 want to use for environment. It is assumed that this memory
306 can just be read and written to, without any special
309 config ENV_IS_IN_REMOTE
310 bool "Environment is in remote memory space"
311 depends on !CHAIN_OF_TRUST
313 Define this if you have a remote memory space which you
314 want to use for the local device's environment.
319 These two #defines specify the address and size of the
320 environment area within the remote memory space. The
321 local device can get the environment from remote memory
322 space by SRIO or PCIE links.
324 config ENV_IS_IN_SPI_FLASH
325 bool "Environment is in SPI flash"
326 depends on !CHAIN_OF_TRUST && SPI
327 default y if ARMADA_XP
328 default y if INTEL_BAYTRAIL
329 default y if INTEL_BRASWELL
330 default y if INTEL_BROADWELL
331 default y if NORTHBRIDGE_INTEL_IVYBRIDGE
332 default y if INTEL_QUARK
333 default y if INTEL_QUEENSBAY
334 default y if ARCH_SUNXI
336 Define this if you have a SPI Flash memory device which you
337 want to use for the environment.
342 These two #defines specify the offset and size of the
343 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
344 aligned to an erase sector boundary.
346 - CONFIG_ENV_SECT_SIZE:
348 Define the SPI flash's sector size.
350 - CONFIG_ENV_OFFSET_REDUND (optional):
352 This setting describes a second storage area of CONFIG_ENV_SIZE
353 size used to hold a redundant copy of the environment data, so
354 that there is a valid backup copy in case there is a power failure
355 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
356 aligned to an erase sector boundary.
358 config ENV_SECT_SIZE_AUTO
359 bool "Use automatically detected sector size"
360 depends on ENV_IS_IN_SPI_FLASH
362 Some boards exist in multiple variants, with different
363 flashes having different sector sizes. In such cases, you
364 can select this option to make U-Boot use the actual sector
365 size when figuring out how much to erase, which can thus be
366 more efficient on the flashes with smaller erase size. Since
367 the environment must always be aligned on a sector boundary,
368 CONFIG_ENV_OFFSET must be aligned to the largest of the
369 different sector sizes, and CONFIG_ENV_SECT_SIZE should be
373 int "Value of SPI flash bus for environment"
374 depends on ENV_IS_IN_SPI_FLASH
375 default SF_DEFAULT_BUS
377 Value the SPI bus and chip select for environment.
380 int "Value of SPI flash chip select for environment"
381 depends on ENV_IS_IN_SPI_FLASH
382 default SF_DEFAULT_CS
384 Value of the SPI chip select for environment.
386 config ENV_SPI_MAX_HZ
387 int "Value of SPI flash max frequency for environment"
388 depends on ENV_IS_IN_SPI_FLASH
389 default SF_DEFAULT_SPEED
391 Value of the SPI max work clock for environment.
394 hex "Value of SPI flash work mode for environment"
395 depends on ENV_IS_IN_SPI_FLASH
396 default SF_DEFAULT_MODE
398 Value of the SPI work mode for environment.
399 See include/spi.h for value.
402 bool "Access Environment in SPI flashes before relocation"
403 depends on ENV_IS_IN_SPI_FLASH
405 Enable this if you want to use Environment in SPI flash
406 before relocation. Call env_init() and than you can use
407 env_get_f() for accessing Environment variables.
410 bool "Environment in a UBI volume"
411 depends on !CHAIN_OF_TRUST
415 Define this if you have an UBI volume that you want to use for the
416 environment. This has the benefit of wear-leveling the environment
417 accesses, which is important on NAND.
419 - CONFIG_ENV_UBI_PART:
421 Define this to a string that is the mtd partition containing the UBI.
423 - CONFIG_ENV_UBI_VOLUME:
425 Define this to the name of the volume that you want to store the
428 - CONFIG_ENV_UBI_VOLUME_REDUND:
430 Define this to the name of another volume to store a second copy of
431 the environment in. This will enable redundant environments in UBI.
432 It is assumed that both volumes are in the same MTD partition.
434 config SYS_REDUNDAND_ENVIRONMENT
435 bool "Enable redundant environment support"
437 Normally, the environemt is stored in a single location. By
438 selecting this option, you can then define where to hold a redundant
439 copy of the environment data, so that there is a valid backup copy in
440 case there is a power failure during a "saveenv" operation.
441 Also this config changes the binary environment structure handling
442 which is used by env import/export commands which are independent of
443 storing variables to redundant location on a non volatile device.
445 config ENV_FAT_INTERFACE
446 string "Name of the block device for the environment"
447 depends on ENV_IS_IN_FAT
450 Define this to a string that is the name of the block device.
452 config ENV_FAT_DEVICE_AND_PART
453 string "Device and partition for where to store the environemt in FAT"
454 depends on ENV_IS_IN_FAT
455 default "0:1" if TI_COMMON_CMD_OPTIONS
456 default "0:auto" if ARCH_ZYNQ || ARCH_ZYNQMP || ARCH_VERSAL
457 default ":auto" if ARCH_SUNXI
458 default "0" if ARCH_AT91
460 Define this to a string to specify the partition of the device. It can
463 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
464 - "D:P": device D partition P. Error occurs if device D has no
467 - "D" or "D:": device D partition 1 if device D has partition
468 table, or the whole device D if has no partition
470 - "D:auto": first partition in device D with bootable flag set.
471 If none, first valid partition in device D. If no
472 partition table then means device D.
474 If ENV_FAT_INTERFACE is set to "mmc" then device 'D' can be omitted,
475 leaving the string starting with a colon, and the boot device will
479 string "Name of the FAT file to use for the environment"
480 depends on ENV_IS_IN_FAT
483 It's a string of the FAT file name. This file use to store the
486 config ENV_FAT_FILE_REDUND
487 string "Name of the FAT file to use for the environment"
488 depends on ENV_IS_IN_FAT && SYS_REDUNDAND_ENVIRONMENT
489 default "uboot-redund.env"
491 It's a string of the FAT file name. This file use to store the
492 redundant environment.
494 config ENV_EXT4_INTERFACE
495 string "Name of the block device for the environment"
496 depends on ENV_IS_IN_EXT4
498 Define this to a string that is the name of the block device.
500 config ENV_EXT4_DEVICE_AND_PART
501 string "Device and partition for where to store the environemt in EXT4"
502 depends on ENV_IS_IN_EXT4
504 Define this to a string to specify the partition of the device. It can
507 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
508 - "D:P": device D partition P. Error occurs if device D has no
511 - "D" or "D:": device D partition 1 if device D has partition
512 table, or the whole device D if has no partition
514 - "D:auto": first partition in device D with bootable flag set.
515 If none, first valid partition in device D. If no
516 partition table then means device D.
518 If ENV_EXT4_INTERFACE is set to "mmc" then device 'D' can be omitted,
519 leaving the string starting with a colon, and the boot device will
523 string "Name of the EXT4 file to use for the environment"
524 depends on ENV_IS_IN_EXT4
527 It's a string of the EXT4 file name. This file use to store the
528 environment (explicit path to the file)
531 hex "Environment address"
532 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
533 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
534 default 0x0 if ENV_IS_IN_SPI_FLASH
536 Offset from the start of the device (or partition)
538 config ENV_ADDR_REDUND
539 hex "Redundant environment address"
540 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
542 Offset from the start of the device (or partition) of the redundant
543 environment location.
546 hex "Environment offset"
547 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
549 default 0x3f8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
550 default 0x140000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
551 default 0xF0000 if ARCH_SUNXI
552 default 0xE0000 if ARCH_ZYNQ
553 default 0x1E00000 if ARCH_ZYNQMP
554 default 0x7F40000 if ARCH_VERSAL || ARCH_VERSAL_NET
556 default 0x140000 if ARCH_AT91
557 default 0x260000 if ARCH_OMAP2PLUS
558 default 0x1080000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
560 Offset from the start of the device (or partition)
562 config ENV_OFFSET_REDUND
563 hex "Redundant environment offset"
564 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
565 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
566 default 0x10C0000 if MICROBLAZE
569 Offset from the start of the device (or partition) of the redundant
570 environment location.
573 hex "Environment Size"
574 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
575 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
576 default 0x10000 if ARCH_SUNXI
577 default 0x8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
578 default 0x2000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
579 default 0x8000 if ARCH_ZYNQMP || ARCH_VERSAL || ARCH_VERSAL_NET
580 default 0x4000 if ARC
583 Size of the environment storage area
586 hex "Environment Sector-Size"
587 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
588 default 0x2000 if ARCH_ROCKCHIP
589 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL || ARCH_VERSAL_NET
590 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
591 default 0x20000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
592 default 0x10000 if ARCH_SUNXI && ENV_IS_IN_SPI_FLASH
594 Size of the sector containing the environment.
597 string "UBI partition name"
598 depends on ENV_IS_IN_UBI
600 MTD partition containing the UBI device
602 config ENV_UBI_VOLUME
603 string "UBI volume name"
604 depends on ENV_IS_IN_UBI
606 Name of the volume that you want to store the environment in.
608 config ENV_UBI_VOLUME_REDUND
609 string "UBI redundant volume name"
610 depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
612 Name of the redundant volume that you want to store the environment in.
614 config ENV_UBI_VID_OFFSET
615 int "ubi environment VID offset"
616 depends on ENV_IS_IN_UBI
619 UBI VID offset for environment. If 0, no custom VID offset is used.
621 config SYS_RELOC_GD_ENV_ADDR
622 bool "Relocate gd->env_addr"
624 Relocate the early env_addr pointer so we know it is not inside
625 the binary. Some systems need this and for the rest, it doesn't hurt.
627 config SYS_MMC_ENV_DEV
628 int "mmc device number"
629 depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT || SYS_LS_PPA_FW_IN_MMC || \
630 CMD_MVEBU_BUBT || FMAN_ENET || QE || PHY_CORTINA
633 MMC device number on the platform where the environment is stored.
635 config SYS_MMC_ENV_PART
636 int "mmc partition number"
637 depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT
640 MMC hardware partition device number on the platform where the
641 environment is stored. Note that this is not related to any software
642 defined partition table but instead if we are in the user area, which is
643 partition 0 or the first boot partition, which is 1 or some other defined
646 config USE_DEFAULT_ENV_FILE
647 bool "Create default environment from file"
649 Normally, the default environment is automatically generated
650 based on the settings of various CONFIG_* options, as well
651 as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
652 you can instead define the entire default environment in an
655 config DEFAULT_ENV_FILE
656 string "Path to default environment file"
657 depends on USE_DEFAULT_ENV_FILE
659 The path containing the default environment. The format is
660 the same as accepted by the mkenvimage tool: lines
661 containing key=value pairs, blank lines and lines beginning
664 config ENV_VARS_UBOOT_RUNTIME_CONFIG
665 bool "Add run-time information to the environment"
667 Enable this in order to add variables describing certain
668 run-time determined information about the hardware to the
669 environment. These will be named board_name, board_rev.
671 config DELAY_ENVIRONMENT
672 bool "Delay environment loading"
673 depends on !OF_CONTROL
675 Enable this to inhibit loading the environment during board
676 initialization. This can address the security risk of untrusted data
677 being used during boot. Normally the environment is loaded when the
678 board is initialised so that it is available to U-Boot. This inhibits
679 that so that the environment is not available until explicitly loaded
680 later by U-Boot code. With CONFIG_OF_CONTROL this is instead
681 controlled by the value of /config/load-environment.
683 config ENV_IMPORT_FDT
684 bool "Amend environment by FDT properties"
685 depends on OF_CONTROL
687 If selected, after the environment has been loaded from its
688 persistent location, the "env_fdt_path" variable is looked
689 up and used as a path to a node in the control DTB. The
690 property/value pairs in that node is then used to update the
691 run-time environment. This can be useful to use the same
692 U-Boot binary with different board variants.
695 string "Default value for env_fdt_path variable"
696 depends on ENV_IMPORT_FDT
697 default "/config/environment"
699 The initial value of the env_fdt_path variable.
702 bool "Always append the environment with new data"
704 If defined, the environment hash table is only ever appended with new
705 data, but the existing hash table can never be dropped and reloaded
706 with newly imported data. This may be used in combination with static
707 flags to e.g. to protect variables which must not be modified.
709 config ENV_WRITEABLE_LIST
710 bool "Permit write access only to listed variables"
712 If defined, only environment variables which explicitly set the 'w'
713 writeable flag can be written and modified at runtime. No variables
714 can be otherwise created, written or imported into the environment.
716 config ENV_ACCESS_IGNORE_FORCE
717 bool "Block forced environment operations"
719 If defined, don't allow the -f switch to env set override variable
723 config SPL_ENV_IS_NOWHERE
724 bool "SPL Environment is not stored"
725 default y if ENV_IS_NOWHERE
727 Similar to ENV_IS_NOWHERE, used for SPL environment.
729 config SPL_ENV_IS_IN_MMC
730 bool "SPL Environment in an MMC device"
731 depends on !SPL_ENV_IS_NOWHERE
732 depends on ENV_IS_IN_MMC
735 Similar to ENV_IS_IN_MMC, used for SPL environment.
737 config SPL_ENV_IS_IN_FAT
738 bool "SPL Environment is in a FAT filesystem"
739 depends on !SPL_ENV_IS_NOWHERE
740 depends on ENV_IS_IN_FAT
743 Similar to ENV_IS_IN_FAT, used for SPL environment.
745 config SPL_ENV_IS_IN_EXT4
746 bool "SPL Environment is in a EXT4 filesystem"
747 depends on !SPL_ENV_IS_NOWHERE
748 depends on ENV_IS_IN_EXT4
751 Similar to ENV_IS_IN_EXT4, used for SPL environment.
753 config SPL_ENV_IS_IN_NAND
754 bool "SPL Environment in a NAND device"
755 depends on !SPL_ENV_IS_NOWHERE
756 depends on ENV_IS_IN_NAND
759 Similar to ENV_IS_IN_NAND, used for SPL environment.
761 config SPL_ENV_IS_IN_SPI_FLASH
762 bool "SPL Environment is in SPI flash"
763 depends on !SPL_ENV_IS_NOWHERE
764 depends on ENV_IS_IN_SPI_FLASH
767 Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
769 config SPL_ENV_IS_IN_FLASH
770 bool "SPL Environment in flash memory"
771 depends on !SPL_ENV_IS_NOWHERE
772 depends on ENV_IS_IN_FLASH
775 Similar to ENV_IS_IN_FLASH, used for SPL environment.
781 config TPL_ENV_IS_NOWHERE
782 bool "TPL Environment is not stored"
783 default y if ENV_IS_NOWHERE
785 Similar to ENV_IS_NOWHERE, used for TPL environment.
787 config TPL_ENV_IS_IN_MMC
788 bool "TPL Environment in an MMC device"
789 depends on !TPL_ENV_IS_NOWHERE
790 depends on ENV_IS_IN_MMC
793 Similar to ENV_IS_IN_MMC, used for TPL environment.
795 config TPL_ENV_IS_IN_FAT
796 bool "TPL Environment is in a FAT filesystem"
797 depends on !TPL_ENV_IS_NOWHERE
798 depends on ENV_IS_IN_FAT
801 Similar to ENV_IS_IN_FAT, used for TPL environment.
803 config TPL_ENV_IS_IN_EXT4
804 bool "TPL Environment is in a EXT4 filesystem"
805 depends on !TPL_ENV_IS_NOWHERE
806 depends on ENV_IS_IN_EXT4
809 Similar to ENV_IS_IN_EXT4, used for TPL environment.
811 config TPL_ENV_IS_IN_NAND
812 bool "TPL Environment in a NAND device"
813 depends on !TPL_ENV_IS_NOWHERE
814 depends on ENV_IS_IN_NAND
817 Similar to ENV_IS_IN_NAND, used for TPL environment.
819 config TPL_ENV_IS_IN_SPI_FLASH
820 bool "TPL Environment is in SPI flash"
821 depends on !TPL_ENV_IS_NOWHERE
822 depends on ENV_IS_IN_SPI_FLASH
825 Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
827 config TPL_ENV_IS_IN_FLASH
828 bool "TPL Environment in flash memory"
829 depends on !TPL_ENV_IS_NOWHERE
830 depends on ENV_IS_IN_FLASH
833 Similar to ENV_IS_IN_FLASH, used for TPL environment.
838 bool "Add a 'bootfile' environment variable"
840 The "bootfile" variable is used in some cases to allow for
841 controlling what file U-Boot will attempt to load and boot. To set
842 this, enable this option and set the value in the next question.
845 string "'bootfile' environment variable value"
846 depends on USE_BOOTFILE
848 The value to set the "bootfile" variable to.
851 bool "Add an 'ethprime' environment variable"
853 The "ethprime" variable is used in some cases to control which
854 network interface is used first.
857 string "'ethprime' environment variable value"
858 depends on USE_ETHPRIME
860 The value to set the "ethprime" variable to.
863 bool "Set a default 'hostname' value in the environment"
867 string "Value of the default 'hostname' value in the environment"
868 depends on USE_HOSTNAME
872 config VERSION_VARIABLE
873 bool "Add a 'ver' environment variable with the U-Boot version"
875 If this variable is defined, an environment variable
876 named "ver" is created by U-Boot showing the U-Boot
877 version as printed by the "version" command.
878 Any change to this variable will be reverted at the