7 def_bool y if CMD_SAVEENV
10 bool "Enable overwriting environment"
12 Use this to permit overriding of certain environmental variables
13 like Ethernet and Serial
16 bool "Environment is not stored"
17 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
18 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
19 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
20 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
21 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
24 Define this if you don't want to or can't have an environment stored
25 on a storage medium. In this case the environment will still exist
26 while U-Boot is running, but once U-Boot exits it will not be
27 stored. U-Boot will therefore always start up with a default
30 config ENV_IS_IN_EEPROM
31 bool "Environment in EEPROM"
32 depends on !CHAIN_OF_TRUST
34 Use this if you have an EEPROM or similar serial access
35 device and a driver for it.
40 These two #defines specify the offset and size of the
41 environment area within the total memory of your EEPROM.
43 Note that we consider the length of the address field to
44 still be one byte because the extra address bits are hidden
47 - CONFIG_ENV_EEPROM_IS_ON_I2C
48 define this, if you have I2C and SPI activated, and your
49 EEPROM, which holds the environment, is on the I2C bus.
51 - CONFIG_I2C_ENV_EEPROM_BUS
52 if you have an Environment on an EEPROM reached over
53 I2C muxes, you can define here, how to reach this
56 #define CONFIG_I2C_ENV_EEPROM_BUS 1
58 EEPROM which holds the environment, is reached over
59 a pca9547 i2c mux with address 0x70, channel 3.
62 bool "Environment is in a FAT filesystem"
63 depends on !CHAIN_OF_TRUST
64 default y if ARCH_BCM283X
65 default y if ARCH_SUNXI && MMC
66 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
70 Define this if you want to use the FAT file system for the environment.
73 bool "Environment is in a EXT4 filesystem"
74 depends on !CHAIN_OF_TRUST
78 Define this if you want to use the EXT4 file system for the environment.
80 config ENV_IS_IN_FLASH
81 bool "Environment in flash memory"
82 depends on !CHAIN_OF_TRUST
83 default y if ARCH_CINTEGRATOR
84 default y if ARCH_INTEGRATOR_CP
85 default y if M548x || M547x || M5282 || MCF547x_8x
86 default y if MCF532x || MCF52x2
87 default y if MPC86xx || MPC83xx
88 default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
89 default y if SH && !CPU_SH4
91 Define this if you have a flash device which you want to use for the
94 a) The environment occupies one whole flash sector, which is
95 "embedded" in the text segment with the U-Boot code. This
96 happens usually with "bottom boot sector" or "top boot
97 sector" type flash chips, which have several smaller
98 sectors at the start or the end. For instance, such a
99 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
100 such a case you would place the environment in one of the
101 4 kB sectors - with U-Boot code before and after it. With
102 "top boot sector" type flash chips, you would put the
103 environment in one of the last sectors, leaving a gap
104 between U-Boot and the environment.
108 Offset of environment data (variable area) to the
109 beginning of flash memory; for instance, with bottom boot
110 type flash chips the second sector can be used: the offset
111 for this sector is given here.
113 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
117 This is just another way to specify the start address of
118 the flash sector containing the environment (instead of
121 CONFIG_ENV_SECT_SIZE:
123 Size of the sector containing the environment.
126 b) Sometimes flash chips have few, equal sized, BIG sectors.
127 In such a case you don't want to spend a whole sector for
132 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
133 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
134 of this flash sector for the environment. This saves
135 memory for the RAM copy of the environment.
137 It may also save flash memory if you decide to use this
138 when your environment is "embedded" within U-Boot code,
139 since then the remainder of the flash sector could be used
140 for U-Boot code. It should be pointed out that this is
141 STRONGLY DISCOURAGED from a robustness point of view:
142 updating the environment in flash makes it always
143 necessary to erase the WHOLE sector. If something goes
144 wrong before the contents has been restored from a copy in
145 RAM, your target system will be dead.
147 CONFIG_ENV_ADDR_REDUND
149 These settings describe a second storage area used to hold
150 a redundant copy of the environment data, so that there is
151 a valid backup copy in case there is a power failure during
152 a "saveenv" operation.
154 BE CAREFUL! Any changes to the flash layout, and some changes to the
155 source code will make it necessary to adapt <board>/u-boot.lds*
159 bool "Environment in an MMC device"
160 depends on !CHAIN_OF_TRUST
162 default y if ARCH_EXYNOS4
163 default y if MX6SX || MX7D
164 default y if TEGRA30 || TEGRA124
165 default y if TEGRA_ARMV8_COMMON
167 Define this if you have an MMC device which you want to use for the
170 CONFIG_SYS_MMC_ENV_DEV:
172 Specifies which MMC device the environment is stored in.
174 CONFIG_SYS_MMC_ENV_PART (optional):
176 Specifies which MMC partition the environment is stored in. If not
177 set, defaults to partition 0, the user area. Common values might be
178 1 (first MMC boot partition), 2 (second MMC boot partition).
183 These two #defines specify the offset and size of the environment
184 area within the specified MMC device.
186 If offset is positive (the usual case), it is treated as relative to
187 the start of the MMC partition. If offset is negative, it is treated
188 as relative to the end of the MMC partition. This can be useful if
189 your board may be fitted with different MMC devices, which have
190 different sizes for the MMC partitions, and you always want the
191 environment placed at the very end of the partition, to leave the
192 maximum possible space before it, to store other data.
194 These two values are in units of bytes, but must be aligned to an
197 CONFIG_ENV_OFFSET_REDUND (optional):
199 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
200 hold a redundant copy of the environment data. This provides a
201 valid backup copy in case the other copy is corrupted, e.g. due
202 to a power failure during a "saveenv" operation.
204 This value may also be positive or negative; this is handled in the
205 same way as CONFIG_ENV_OFFSET.
207 This value is also in units of bytes, but must also be aligned to
208 an MMC sector boundary.
210 config ENV_IS_IN_NAND
211 bool "Environment in a NAND device"
212 depends on !CHAIN_OF_TRUST
214 Define this if you have a NAND device which you want to use for the
220 These two #defines specify the offset and size of the environment
221 area within the first NAND device. CONFIG_ENV_OFFSET must be
222 aligned to an erase block boundary.
224 - CONFIG_ENV_OFFSET_REDUND (optional):
226 This setting describes a second storage area of CONFIG_ENV_SIZE
227 size used to hold a redundant copy of the environment data, so
228 that there is a valid backup copy in case there is a power failure
229 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
230 aligned to an erase block boundary.
232 - CONFIG_ENV_RANGE (optional):
234 Specifies the length of the region in which the environment
235 can be written. This should be a multiple of the NAND device's
236 block size. Specifying a range with more erase blocks than
237 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
238 the range to be avoided.
240 - CONFIG_ENV_OFFSET_OOB (optional):
242 Enables support for dynamically retrieving the offset of the
243 environment from block zero's out-of-band data. The
244 "nand env.oob" command can be used to record this offset.
245 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
246 using CONFIG_ENV_OFFSET_OOB.
248 config ENV_IS_IN_NVRAM
249 bool "Environment in a non-volatile RAM"
250 depends on !CHAIN_OF_TRUST
252 Define this if you have some non-volatile memory device
253 (NVRAM, battery buffered SRAM) which you want to use for the
259 These two #defines are used to determine the memory area you
260 want to use for environment. It is assumed that this memory
261 can just be read and written to, without any special
264 config ENV_IS_IN_ONENAND
265 bool "Environment is in OneNAND"
266 depends on !CHAIN_OF_TRUST
268 Define this if you want to put your local device's environment in
274 These two #defines are used to determine the device range you
275 want to use for environment. It is assumed that this memory
276 can just be read and written to, without any special
279 config ENV_IS_IN_REMOTE
280 bool "Environment is in remote memory space"
281 depends on !CHAIN_OF_TRUST
283 Define this if you have a remote memory space which you
284 want to use for the local device's environment.
289 These two #defines specify the address and size of the
290 environment area within the remote memory space. The
291 local device can get the environment from remote memory
292 space by SRIO or PCIE links.
294 config ENV_IS_IN_SPI_FLASH
295 bool "Environment is in SPI flash"
296 depends on !CHAIN_OF_TRUST && SPI
297 default y if ARMADA_XP
298 default y if INTEL_BAYTRAIL
299 default y if INTEL_BRASWELL
300 default y if INTEL_BROADWELL
301 default y if NORTHBRIDGE_INTEL_IVYBRIDGE
302 default y if INTEL_QUARK
303 default y if INTEL_QUEENSBAY
305 Define this if you have a SPI Flash memory device which you
306 want to use for the environment.
311 These two #defines specify the offset and size of the
312 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
313 aligned to an erase sector boundary.
315 - CONFIG_ENV_SECT_SIZE:
317 Define the SPI flash's sector size.
319 - CONFIG_ENV_OFFSET_REDUND (optional):
321 This setting describes a second storage area of CONFIG_ENV_SIZE
322 size used to hold a redundant copy of the environment data, so
323 that there is a valid backup copy in case there is a power failure
324 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
325 aligned to an erase sector boundary.
327 config USE_ENV_SPI_BUS
328 bool "SPI flash bus for environment"
329 depends on ENV_IS_IN_SPI_FLASH
331 Force the SPI bus for environment.
332 If not defined, use CONFIG_SF_DEFAULT_BUS.
335 int "Value of SPI flash bus for environment"
336 depends on USE_ENV_SPI_BUS
338 Value the SPI bus and chip select for environment.
340 config USE_ENV_SPI_CS
341 bool "SPI flash chip select for environment"
342 depends on ENV_IS_IN_SPI_FLASH
344 Force the SPI chip select for environment.
345 If not defined, use CONFIG_SF_DEFAULT_CS.
348 int "Value of SPI flash chip select for environment"
349 depends on USE_ENV_SPI_CS
351 Value of the SPI chip select for environment.
353 config USE_ENV_SPI_MAX_HZ
354 bool "SPI flash max frequency for environment"
355 depends on ENV_IS_IN_SPI_FLASH
357 Force the SPI max work clock for environment.
358 If not defined, use CONFIG_SF_DEFAULT_SPEED.
360 config ENV_SPI_MAX_HZ
361 int "Value of SPI flash max frequency for environment"
362 depends on USE_ENV_SPI_MAX_HZ
364 Value of the SPI max work clock for environment.
366 config USE_ENV_SPI_MODE
367 bool "SPI flash mode for environment"
368 depends on ENV_IS_IN_SPI_FLASH
370 Force the SPI work mode for environment.
373 hex "Value of SPI flash work mode for environment"
374 depends on USE_ENV_SPI_MODE
376 Value of the SPI work mode for environment.
377 See include/spi.h for value.
380 bool "Environment in a UBI volume"
381 depends on !CHAIN_OF_TRUST
385 Define this if you have an UBI volume that you want to use for the
386 environment. This has the benefit of wear-leveling the environment
387 accesses, which is important on NAND.
389 - CONFIG_ENV_UBI_PART:
391 Define this to a string that is the mtd partition containing the UBI.
393 - CONFIG_ENV_UBI_VOLUME:
395 Define this to the name of the volume that you want to store the
398 - CONFIG_ENV_UBI_VOLUME_REDUND:
400 Define this to the name of another volume to store a second copy of
401 the environment in. This will enable redundant environments in UBI.
402 It is assumed that both volumes are in the same MTD partition.
404 config SYS_REDUNDAND_ENVIRONMENT
405 bool "Enable redundant environment support"
406 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
407 ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI
409 Normally, the environemt is stored in a single location. By
410 selecting this option, you can then define where to hold a redundant
411 copy of the environment data, so that there is a valid backup copy in
412 case there is a power failure during a "saveenv" operation.
414 config ENV_FAT_INTERFACE
415 string "Name of the block device for the environment"
416 depends on ENV_IS_IN_FAT
419 Define this to a string that is the name of the block device.
421 config ENV_FAT_DEVICE_AND_PART
422 string "Device and partition for where to store the environemt in FAT"
423 depends on ENV_IS_IN_FAT
424 default "0:1" if TI_COMMON_CMD_OPTIONS
425 default "0:auto" if ARCH_ZYNQ || ARCH_ZYNQMP
426 default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
427 default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
428 default "0" if ARCH_AT91
430 Define this to a string to specify the partition of the device. It can
433 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
434 - "D:P": device D partition P. Error occurs if device D has no
437 - "D" or "D:": device D partition 1 if device D has partition
438 table, or the whole device D if has no partition
440 - "D:auto": first partition in device D with bootable flag set.
441 If none, first valid partition in device D. If no
442 partition table then means device D.
444 If ENV_FAT_INTERFACE is set to "mmc" then device 'D' can be omitted,
445 leaving the string starting with a colon, and the boot device will
449 string "Name of the FAT file to use for the environment"
450 depends on ENV_IS_IN_FAT
453 It's a string of the FAT file name. This file use to store the
456 config ENV_EXT4_INTERFACE
457 string "Name of the block device for the environment"
458 depends on ENV_IS_IN_EXT4
460 Define this to a string that is the name of the block device.
462 config ENV_EXT4_DEVICE_AND_PART
463 string "Device and partition for where to store the environemt in EXT4"
464 depends on ENV_IS_IN_EXT4
466 Define this to a string to specify the partition of the device. It can
469 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
470 - "D:P": device D partition P. Error occurs if device D has no
473 - "D" or "D:": device D partition 1 if device D has partition
474 table, or the whole device D if has no partition
476 - "D:auto": first partition in device D with bootable flag set.
477 If none, first valid partition in device D. If no
478 partition table then means device D.
480 If ENV_EXT4_INTERFACE is set to "mmc" then device 'D' can be omitted,
481 leaving the string starting with a colon, and the boot device will
485 string "Name of the EXT4 file to use for the environment"
486 depends on ENV_IS_IN_EXT4
489 It's a string of the EXT4 file name. This file use to store the
490 environment (explicit path to the file)
493 hex "Environment address"
494 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
495 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
496 default 0x0 if ENV_IS_IN_SPI_FLASH
498 Offset from the start of the device (or partition)
500 config ENV_ADDR_REDUND
501 hex "Redundant environment address"
502 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
504 Offset from the start of the device (or partition) of the redundant
505 environment location.
508 hex "Environment offset"
509 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
511 default 0x3f8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
512 default 0x140000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
513 default 0x88000 if ARCH_SUNXI
514 default 0xE0000 if ARCH_ZYNQ
515 default 0x1E00000 if ARCH_ZYNQMP
516 default 0x7F40000 if ARCH_VERSAL
518 default 0x140000 if ARCH_AT91
519 default 0x260000 if ARCH_OMAP2PLUS
520 default 0x1080000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
522 Offset from the start of the device (or partition)
524 config ENV_OFFSET_REDUND
525 hex "Redundant environment offset"
526 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
527 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
529 Offset from the start of the device (or partition) of the redundant
530 environment location.
533 hex "Environment Size"
534 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
535 default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
536 default 0x8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
537 default 0x2000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
538 default 0x8000 if ARCH_ZYNQMP || ARCH_VERSAL
539 default 0x4000 if ARC
542 Size of the environment storage area
545 hex "Environment Sector-Size"
546 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
547 default 0x2000 if ARCH_ROCKCHIP
548 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL
549 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
550 default 0x20000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
552 Size of the sector containing the environment.
555 string "UBI partition name"
556 depends on ENV_IS_IN_UBI
558 MTD partition containing the UBI device
560 config ENV_UBI_VOLUME
561 string "UBI volume name"
562 depends on ENV_IS_IN_UBI
564 Name of the volume that you want to store the environment in.
566 config ENV_UBI_VOLUME_REDUND
567 string "UBI redundant volume name"
568 depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
570 Name of the redundant volume that you want to store the environment in.
572 config ENV_UBI_VID_OFFSET
573 int "ubi environment VID offset"
574 depends on ENV_IS_IN_UBI
577 UBI VID offset for environment. If 0, no custom VID offset is used.
579 config SYS_RELOC_GD_ENV_ADDR
580 bool "Relocate gd->env_addr"
582 Relocate the early env_addr pointer so we know it is not inside
583 the binary. Some systems need this and for the rest, it doesn't hurt.
585 config SYS_MMC_ENV_DEV
586 int "mmc device number"
587 depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT || SYS_LS_PPA_FW_IN_MMC || \
588 CMD_MVEBU_BUBT || FMAN_ENET || QE
591 MMC device number on the platform where the environment is stored.
593 config SYS_MMC_ENV_PART
594 int "mmc partition number"
595 depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT
598 MMC hardware partition device number on the platform where the
599 environment is stored. Note that this is not related to any software
600 defined partition table but instead if we are in the user area, which is
601 partition 0 or the first boot partition, which is 1 or some other defined
604 config USE_DEFAULT_ENV_FILE
605 bool "Create default environment from file"
607 Normally, the default environment is automatically generated
608 based on the settings of various CONFIG_* options, as well
609 as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
610 you can instead define the entire default environment in an
613 config DEFAULT_ENV_FILE
614 string "Path to default environment file"
615 depends on USE_DEFAULT_ENV_FILE
617 The path containing the default environment. The format is
618 the same as accepted by the mkenvimage tool: lines
619 containing key=value pairs, blank lines and lines beginning
622 config ENV_VARS_UBOOT_RUNTIME_CONFIG
623 bool "Add run-time information to the environment"
625 Enable this in order to add variables describing certain
626 run-time determined information about the hardware to the
627 environment. These will be named board_name, board_rev.
629 config DELAY_ENVIRONMENT
630 bool "Delay environment loading"
631 depends on !OF_CONTROL
633 Enable this to inhibit loading the environment during board
634 initialization. This can address the security risk of untrusted data
635 being used during boot. Normally the environment is loaded when the
636 board is initialised so that it is available to U-Boot. This inhibits
637 that so that the environment is not available until explicitly loaded
638 later by U-Boot code. With CONFIG_OF_CONTROL this is instead
639 controlled by the value of /config/load-environment.
642 bool "Always append the environment with new data"
645 If defined, the environment hash table is only ever appended with new
646 data, but the existing hash table can never be dropped and reloaded
647 with newly imported data. This may be used in combination with static
648 flags to e.g. to protect variables which must not be modified.
650 config ENV_WRITEABLE_LIST
651 bool "Permit write access only to listed variables"
654 If defined, only environment variables which explicitly set the 'w'
655 writeable flag can be written and modified at runtime. No variables
656 can be otherwise created, written or imported into the environment.
658 config ENV_ACCESS_IGNORE_FORCE
659 bool "Block forced environment operations"
662 If defined, don't allow the -f switch to env set override variable
666 config SPL_ENV_IS_NOWHERE
667 bool "SPL Environment is not stored"
668 default y if ENV_IS_NOWHERE
670 Similar to ENV_IS_NOWHERE, used for SPL environment.
672 config SPL_ENV_IS_IN_MMC
673 bool "SPL Environment in an MMC device"
674 depends on !SPL_ENV_IS_NOWHERE
675 depends on ENV_IS_IN_MMC
678 Similar to ENV_IS_IN_MMC, used for SPL environment.
680 config SPL_ENV_IS_IN_FAT
681 bool "SPL Environment is in a FAT filesystem"
682 depends on !SPL_ENV_IS_NOWHERE
683 depends on ENV_IS_IN_FAT
686 Similar to ENV_IS_IN_FAT, used for SPL environment.
688 config SPL_ENV_IS_IN_EXT4
689 bool "SPL Environment is in a EXT4 filesystem"
690 depends on !SPL_ENV_IS_NOWHERE
691 depends on ENV_IS_IN_EXT4
694 Similar to ENV_IS_IN_EXT4, used for SPL environment.
696 config SPL_ENV_IS_IN_NAND
697 bool "SPL Environment in a NAND device"
698 depends on !SPL_ENV_IS_NOWHERE
699 depends on ENV_IS_IN_NAND
702 Similar to ENV_IS_IN_NAND, used for SPL environment.
704 config SPL_ENV_IS_IN_SPI_FLASH
705 bool "SPL Environment is in SPI flash"
706 depends on !SPL_ENV_IS_NOWHERE
707 depends on ENV_IS_IN_SPI_FLASH
710 Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
712 config SPL_ENV_IS_IN_FLASH
713 bool "SPL Environment in flash memory"
714 depends on !SPL_ENV_IS_NOWHERE
715 depends on ENV_IS_IN_FLASH
718 Similar to ENV_IS_IN_FLASH, used for SPL environment.
724 config TPL_ENV_IS_NOWHERE
725 bool "TPL Environment is not stored"
726 default y if ENV_IS_NOWHERE
728 Similar to ENV_IS_NOWHERE, used for TPL environment.
730 config TPL_ENV_IS_IN_MMC
731 bool "TPL Environment in an MMC device"
732 depends on !TPL_ENV_IS_NOWHERE
733 depends on ENV_IS_IN_MMC
736 Similar to ENV_IS_IN_MMC, used for TPL environment.
738 config TPL_ENV_IS_IN_FAT
739 bool "TPL Environment is in a FAT filesystem"
740 depends on !TPL_ENV_IS_NOWHERE
741 depends on ENV_IS_IN_FAT
744 Similar to ENV_IS_IN_FAT, used for TPL environment.
746 config TPL_ENV_IS_IN_EXT4
747 bool "TPL Environment is in a EXT4 filesystem"
748 depends on !TPL_ENV_IS_NOWHERE
749 depends on ENV_IS_IN_EXT4
752 Similar to ENV_IS_IN_EXT4, used for TPL environment.
754 config TPL_ENV_IS_IN_NAND
755 bool "TPL Environment in a NAND device"
756 depends on !TPL_ENV_IS_NOWHERE
757 depends on ENV_IS_IN_NAND
760 Similar to ENV_IS_IN_NAND, used for TPL environment.
762 config TPL_ENV_IS_IN_SPI_FLASH
763 bool "TPL Environment is in SPI flash"
764 depends on !TPL_ENV_IS_NOWHERE
765 depends on ENV_IS_IN_SPI_FLASH
768 Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
770 config TPL_ENV_IS_IN_FLASH
771 bool "TPL Environment in flash memory"
772 depends on !TPL_ENV_IS_NOWHERE
773 depends on ENV_IS_IN_FLASH
776 Similar to ENV_IS_IN_FLASH, used for TPL environment.
780 config VERSION_VARIABLE
781 bool "Add a 'ver' environment variable with the U-Boot version"
783 If this variable is defined, an environment variable
784 named "ver" is created by U-Boot showing the U-Boot
785 version as printed by the "version" command.
786 Any change to this variable will be reverted at the