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 OVERWRITE_ETHADDR_ONCE
34 bool "Enable overwriting ethaddr environment variables once"
35 depends on !ENV_OVERWRITE
37 Enable this to allow for the ethaddr environment variables to be
38 overwritten one time per boot, only. This allows for a default
39 to be installed in the environment, which can be changed exactly ONCE
42 config ENV_MIN_ENTRIES
43 int "Minimum number of entries in the environment hashtable"
46 Minimum number of entries in the hash table that is used internally
47 to store the environment settings.
49 config ENV_MAX_ENTRIES
50 int "Maximumm number of entries in the environment hashtable"
53 Maximum number of entries in the hash table that is used internally
54 to store the environment settings. The default setting is supposed to
55 be generous and should work in most cases. This setting can be used
56 to tune behaviour; see lib/hashtable.c for details.
59 bool "Environment is not stored"
60 default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
61 !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
62 !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
63 !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
64 !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
67 Define this if you don't want to or can't have an environment stored
68 on a storage medium. In this case the environment will still exist
69 while U-Boot is running, but once U-Boot exits it will not be
70 stored. U-Boot will therefore always start up with a default
73 config ENV_IS_IN_EEPROM
74 bool "Environment in EEPROM"
75 depends on !CHAIN_OF_TRUST
77 Use this if you have an EEPROM or similar serial access
78 device and a driver for it.
83 These two #defines specify the offset and size of the
84 environment area within the total memory of your EEPROM.
86 Note that we consider the length of the address field to
87 still be one byte because the extra address bits are hidden
90 EEPROM which holds the environment, is reached over
91 a pca9547 i2c mux with address 0x70, channel 3.
94 bool "Environment is in a FAT filesystem"
95 depends on !CHAIN_OF_TRUST
96 default y if ARCH_BCM283X
97 default y if ARCH_SUNXI && MMC
98 default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
102 Define this if you want to use the FAT file system for the environment.
104 config ENV_IS_IN_EXT4
105 bool "Environment is in a EXT4 filesystem"
106 depends on !CHAIN_OF_TRUST
110 Define this if you want to use the EXT4 file system for the environment.
112 config ENV_IS_IN_FLASH
113 bool "Environment in flash memory"
114 depends on !CHAIN_OF_TRUST
115 default y if ARCH_CINTEGRATOR
116 default y if ARCH_INTEGRATOR_CP
117 default y if M548x || M547x || M5282
118 default y if MCF532x || MCF52x2
119 default y if MPC86xx || MPC83xx
120 default y if ARCH_MPC8548
121 default y if SH && !CPU_SH4
123 Define this if you have a flash device which you want to use for the
126 a) The environment occupies one whole flash sector, which is
127 "embedded" in the text segment with the U-Boot code. This
128 happens usually with "bottom boot sector" or "top boot
129 sector" type flash chips, which have several smaller
130 sectors at the start or the end. For instance, such a
131 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
132 such a case you would place the environment in one of the
133 4 kB sectors - with U-Boot code before and after it. With
134 "top boot sector" type flash chips, you would put the
135 environment in one of the last sectors, leaving a gap
136 between U-Boot and the environment.
140 Offset of environment data (variable area) to the
141 beginning of flash memory; for instance, with bottom boot
142 type flash chips the second sector can be used: the offset
143 for this sector is given here.
145 CONFIG_ENV_OFFSET is used relative to CFG_SYS_FLASH_BASE.
149 This is just another way to specify the start address of
150 the flash sector containing the environment (instead of
153 CONFIG_ENV_SECT_SIZE:
155 Size of the sector containing the environment.
158 b) Sometimes flash chips have few, equal sized, BIG sectors.
159 In such a case you don't want to spend a whole sector for
164 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
165 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
166 of this flash sector for the environment. This saves
167 memory for the RAM copy of the environment.
169 It may also save flash memory if you decide to use this
170 when your environment is "embedded" within U-Boot code,
171 since then the remainder of the flash sector could be used
172 for U-Boot code. It should be pointed out that this is
173 STRONGLY DISCOURAGED from a robustness point of view:
174 updating the environment in flash makes it always
175 necessary to erase the WHOLE sector. If something goes
176 wrong before the contents has been restored from a copy in
177 RAM, your target system will be dead.
179 CONFIG_ENV_ADDR_REDUND
181 These settings describe a second storage area used to hold
182 a redundant copy of the environment data, so that there is
183 a valid backup copy in case there is a power failure during
184 a "saveenv" operation.
186 BE CAREFUL! Any changes to the flash layout, and some changes to the
187 source code will make it necessary to adapt <board>/u-boot.lds*
191 bool "Environment in an MMC device"
192 depends on !CHAIN_OF_TRUST
194 default y if ARCH_EXYNOS4
195 default y if MX6SX || MX7D
196 default y if TEGRA30 || TEGRA124
197 default y if TEGRA_ARMV8_COMMON
199 Define this if you have an MMC device which you want to use for the
202 CONFIG_SYS_MMC_ENV_DEV:
204 Specifies which MMC device the environment is stored in.
206 CONFIG_SYS_MMC_ENV_PART (optional):
208 Specifies which MMC partition the environment is stored in. If not
209 set, defaults to partition 0, the user area. Common values might be
210 1 (first MMC boot partition), 2 (second MMC boot partition).
215 These two #defines specify the offset and size of the environment
216 area within the specified MMC device.
218 If offset is positive (the usual case), it is treated as relative to
219 the start of the MMC partition. If offset is negative, it is treated
220 as relative to the end of the MMC partition. This can be useful if
221 your board may be fitted with different MMC devices, which have
222 different sizes for the MMC partitions, and you always want the
223 environment placed at the very end of the partition, to leave the
224 maximum possible space before it, to store other data.
226 These two values are in units of bytes, but must be aligned to an
229 CONFIG_ENV_OFFSET_REDUND (optional):
231 Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
232 hold a redundant copy of the environment data. This provides a
233 valid backup copy in case the other copy is corrupted, e.g. due
234 to a power failure during a "saveenv" operation.
236 This value may also be positive or negative; this is handled in the
237 same way as CONFIG_ENV_OFFSET.
239 In case CONFIG_SYS_MMC_ENV_PART is 1 (i.e. environment in eMMC boot
240 partition) then setting CONFIG_ENV_OFFSET_REDUND to the same value
241 as CONFIG_ENV_OFFSET makes use of the second eMMC boot partition for
242 the redundant environment copy.
244 This value is also in units of bytes, but must also be aligned to
245 an MMC sector boundary.
247 config ENV_IS_IN_NAND
248 bool "Environment in a NAND device"
249 depends on !CHAIN_OF_TRUST
251 Define this if you have a NAND device which you want to use for the
257 These two #defines specify the offset and size of the environment
258 area within the first NAND device. CONFIG_ENV_OFFSET must be
259 aligned to an erase block boundary.
261 - CONFIG_ENV_OFFSET_REDUND (optional):
263 This setting describes a second storage area of CONFIG_ENV_SIZE
264 size used to hold a redundant copy of the environment data, so
265 that there is a valid backup copy in case there is a power failure
266 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
267 aligned to an erase block boundary.
269 - CONFIG_ENV_OFFSET_OOB (optional):
271 Enables support for dynamically retrieving the offset of the
272 environment from block zero's out-of-band data. The
273 "nand env.oob" command can be used to record this offset.
274 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
275 using CONFIG_ENV_OFFSET_OOB.
278 hex "Length of the region in which the environment can be written"
279 depends on ENV_IS_IN_NAND
280 range ENV_SIZE 0x7fffffff
283 This should be a multiple of the NAND device's block size.
284 Specifying a range with more erase blocks than are needed to hold
285 CONFIG_ENV_SIZE allows bad blocks within the range to be avoided.
287 config ENV_IS_IN_NVRAM
288 bool "Environment in a non-volatile RAM"
289 depends on !CHAIN_OF_TRUST
291 Define this if you have some non-volatile memory device
292 (NVRAM, battery buffered SRAM) which you want to use for the
298 These two #defines are used to determine the memory area you
299 want to use for environment. It is assumed that this memory
300 can just be read and written to, without any special
303 config ENV_IS_IN_ONENAND
304 bool "Environment is in OneNAND"
305 depends on !CHAIN_OF_TRUST
307 Define this if you want to put your local device's environment in
313 These two #defines are used to determine the device range you
314 want to use for environment. It is assumed that this memory
315 can just be read and written to, without any special
318 config ENV_IS_IN_REMOTE
319 bool "Environment is in remote memory space"
320 depends on !CHAIN_OF_TRUST
322 Define this if you have a remote memory space which you
323 want to use for the local device's environment.
328 These two #defines specify the address and size of the
329 environment area within the remote memory space. The
330 local device can get the environment from remote memory
331 space by SRIO or PCIE links.
333 config ENV_IS_IN_SPI_FLASH
334 bool "Environment is in SPI flash"
335 depends on !CHAIN_OF_TRUST && SPI
336 default y if ARMADA_XP
337 default y if INTEL_BAYTRAIL
338 default y if INTEL_BRASWELL
339 default y if INTEL_BROADWELL
340 default y if NORTHBRIDGE_INTEL_IVYBRIDGE
341 default y if INTEL_QUARK
342 default y if INTEL_QUEENSBAY
343 default y if ARCH_SUNXI
345 Define this if you have a SPI Flash memory device which you
346 want to use for the environment.
351 These two #defines specify the offset and size of the
352 environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
353 aligned to an erase sector boundary.
355 - CONFIG_ENV_SECT_SIZE:
357 Define the SPI flash's sector size.
359 - CONFIG_ENV_OFFSET_REDUND (optional):
361 This setting describes a second storage area of CONFIG_ENV_SIZE
362 size used to hold a redundant copy of the environment data, so
363 that there is a valid backup copy in case there is a power failure
364 during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
365 aligned to an erase sector boundary.
367 config ENV_SECT_SIZE_AUTO
368 bool "Use automatically detected sector size"
369 depends on ENV_IS_IN_SPI_FLASH
371 Some boards exist in multiple variants, with different
372 flashes having different sector sizes. In such cases, you
373 can select this option to make U-Boot use the actual sector
374 size when figuring out how much to erase, which can thus be
375 more efficient on the flashes with smaller erase size. Since
376 the environment must always be aligned on a sector boundary,
377 CONFIG_ENV_OFFSET must be aligned to the largest of the
378 different sector sizes, and CONFIG_ENV_SECT_SIZE should be
382 int "Value of SPI flash bus for environment"
383 depends on ENV_IS_IN_SPI_FLASH
384 default SF_DEFAULT_BUS
386 Value the SPI bus and chip select for environment.
389 int "Value of SPI flash chip select for environment"
390 depends on ENV_IS_IN_SPI_FLASH
391 default SF_DEFAULT_CS
393 Value of the SPI chip select for environment.
395 config ENV_SPI_MAX_HZ
396 int "Value of SPI flash max frequency for environment"
397 depends on ENV_IS_IN_SPI_FLASH
398 default SF_DEFAULT_SPEED
400 Value of the SPI max work clock for environment.
403 hex "Value of SPI flash work mode for environment"
404 depends on ENV_IS_IN_SPI_FLASH
405 default SF_DEFAULT_MODE
407 Value of the SPI work mode for environment.
408 See include/spi.h for value.
411 bool "Access Environment in SPI flashes before relocation"
412 depends on ENV_IS_IN_SPI_FLASH
414 Enable this if you want to use Environment in SPI flash
415 before relocation. Call env_init() and than you can use
416 env_get_f() for accessing Environment variables.
419 bool "Environment in a UBI volume"
420 depends on !CHAIN_OF_TRUST
424 Define this if you have an UBI volume that you want to use for the
425 environment. This has the benefit of wear-leveling the environment
426 accesses, which is important on NAND.
428 - CONFIG_ENV_UBI_PART:
430 Define this to a string that is the mtd partition containing the UBI.
432 - CONFIG_ENV_UBI_VOLUME:
434 Define this to the name of the volume that you want to store the
437 - CONFIG_ENV_UBI_VOLUME_REDUND:
439 Define this to the name of another volume to store a second copy of
440 the environment in. This will enable redundant environments in UBI.
441 It is assumed that both volumes are in the same MTD partition.
443 config SYS_REDUNDAND_ENVIRONMENT
444 bool "Enable redundant environment support"
446 Normally, the environemt is stored in a single location. By
447 selecting this option, you can then define where to hold a redundant
448 copy of the environment data, so that there is a valid backup copy in
449 case there is a power failure during a "saveenv" operation.
450 Also this config changes the binary environment structure handling
451 which is used by env import/export commands which are independent of
452 storing variables to redundant location on a non volatile device.
454 config ENV_FAT_INTERFACE
455 string "Name of the block device for the environment"
456 depends on ENV_IS_IN_FAT
459 Define this to a string that is the name of the block device.
461 config ENV_FAT_DEVICE_AND_PART
462 string "Device and partition for where to store the environemt in FAT"
463 depends on ENV_IS_IN_FAT
464 default "0:1" if TI_COMMON_CMD_OPTIONS
465 default "0:auto" if ARCH_ZYNQ || ARCH_ZYNQMP || ARCH_VERSAL
466 default ":auto" if ARCH_SUNXI
467 default "0" if ARCH_AT91
469 Define this to a string to specify the partition of the device. It can
472 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
473 - "D:P": device D partition P. Error occurs if device D has no
476 - "D" or "D:": device D partition 1 if device D has partition
477 table, or the whole device D if has no partition
479 - "D:auto": first partition in device D with bootable flag set.
480 If none, first valid partition in device D. If no
481 partition table then means device D.
483 If ENV_FAT_INTERFACE is set to "mmc" then device 'D' can be omitted,
484 leaving the string starting with a colon, and the boot device will
488 string "Name of the FAT file to use for the environment"
489 depends on ENV_IS_IN_FAT
492 It's a string of the FAT file name. This file use to store the
495 config ENV_FAT_FILE_REDUND
496 string "Name of the FAT file to use for the environment"
497 depends on ENV_IS_IN_FAT && SYS_REDUNDAND_ENVIRONMENT
498 default "uboot-redund.env"
500 It's a string of the FAT file name. This file use to store the
501 redundant environment.
503 config ENV_EXT4_INTERFACE
504 string "Name of the block device for the environment"
505 depends on ENV_IS_IN_EXT4
507 Define this to a string that is the name of the block device.
509 config ENV_EXT4_DEVICE_AND_PART
510 string "Device and partition for where to store the environemt in EXT4"
511 depends on ENV_IS_IN_EXT4
513 Define this to a string to specify the partition of the device. It can
516 "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
517 - "D:P": device D partition P. Error occurs if device D has no
520 - "D" or "D:": device D partition 1 if device D has partition
521 table, or the whole device D if has no partition
523 - "D:auto": first partition in device D with bootable flag set.
524 If none, first valid partition in device D. If no
525 partition table then means device D.
527 If ENV_EXT4_INTERFACE is set to "mmc" then device 'D' can be omitted,
528 leaving the string starting with a colon, and the boot device will
532 string "Name of the EXT4 file to use for the environment"
533 depends on ENV_IS_IN_EXT4
536 It's a string of the EXT4 file name. This file use to store the
537 environment (explicit path to the file)
540 hex "Environment address"
541 depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
542 ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
543 default 0x0 if ENV_IS_IN_SPI_FLASH
545 Offset from the start of the device (or partition)
547 config ENV_ADDR_REDUND
548 hex "Redundant environment address"
549 depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
551 Offset from the start of the device (or partition) of the redundant
552 environment location.
555 hex "Environment offset"
556 depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
558 default 0x3f8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
559 default 0x140000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
560 default 0xF0000 if ARCH_SUNXI
561 default 0xE0000 if ARCH_ZYNQ
562 default 0x1E00000 if ARCH_ZYNQMP
563 default 0x7F40000 if ARCH_VERSAL || ARCH_VERSAL_NET
565 default 0x140000 if ARCH_AT91
566 default 0x260000 if ARCH_OMAP2PLUS
567 default 0x1080000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
569 Offset from the start of the device (or partition)
571 config ENV_OFFSET_REDUND
572 hex "Redundant environment offset"
573 depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
574 ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
575 default 0x10C0000 if MICROBLAZE
578 Offset from the start of the device (or partition) of the redundant
579 environment location.
582 hex "Environment Size"
583 default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
584 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
585 default 0x10000 if ARCH_SUNXI
586 default 0x8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
587 default 0x2000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
588 default 0x8000 if ARCH_ZYNQMP || ARCH_VERSAL || ARCH_VERSAL_NET
589 default 0x4000 if ARC
592 Size of the environment storage area
595 hex "Environment Sector-Size"
596 depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
597 default 0x2000 if ARCH_ROCKCHIP
598 default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL || ARCH_VERSAL_NET
599 default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
600 default 0x20000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
601 default 0x10000 if ARCH_SUNXI && ENV_IS_IN_SPI_FLASH
603 Size of the sector containing the environment.
606 string "UBI partition name"
607 depends on ENV_IS_IN_UBI
609 MTD partition containing the UBI device
611 config ENV_UBI_VOLUME
612 string "UBI volume name"
613 depends on ENV_IS_IN_UBI
615 Name of the volume that you want to store the environment in.
617 config ENV_UBI_VOLUME_REDUND
618 string "UBI redundant volume name"
619 depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
621 Name of the redundant volume that you want to store the environment in.
623 config ENV_UBI_VID_OFFSET
624 int "ubi environment VID offset"
625 depends on ENV_IS_IN_UBI
628 UBI VID offset for environment. If 0, no custom VID offset is used.
630 config SYS_RELOC_GD_ENV_ADDR
631 bool "Relocate gd->env_addr"
633 Relocate the early env_addr pointer so we know it is not inside
634 the binary. Some systems need this and for the rest, it doesn't hurt.
636 config SYS_MMC_ENV_DEV
637 int "mmc device number"
638 depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT || SYS_LS_PPA_FW_IN_MMC || \
639 CMD_MVEBU_BUBT || FMAN_ENET || QE || PHY_CORTINA
642 MMC device number on the platform where the environment is stored.
644 config SYS_MMC_ENV_PART
645 int "mmc partition number"
646 depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT
649 MMC hardware partition device number on the platform where the
650 environment is stored. Note that this is not related to any software
651 defined partition table but instead if we are in the user area, which is
652 partition 0 or the first boot partition, which is 1 or some other defined
655 config USE_DEFAULT_ENV_FILE
656 bool "Create default environment from file"
658 Normally, the default environment is automatically generated
659 based on the settings of various CONFIG_* options, as well
660 as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
661 you can instead define the entire default environment in an
664 config DEFAULT_ENV_FILE
665 string "Path to default environment file"
666 depends on USE_DEFAULT_ENV_FILE
668 The path containing the default environment. The format is
669 the same as accepted by the mkenvimage tool: lines
670 containing key=value pairs, blank lines and lines beginning
673 config ENV_VARS_UBOOT_RUNTIME_CONFIG
674 bool "Add run-time information to the environment"
676 Enable this in order to add variables describing certain
677 run-time determined information about the hardware to the
678 environment. These will be named board_name, board_rev.
680 config DELAY_ENVIRONMENT
681 bool "Delay environment loading"
682 depends on !OF_CONTROL
684 Enable this to inhibit loading the environment during board
685 initialization. This can address the security risk of untrusted data
686 being used during boot. Normally the environment is loaded when the
687 board is initialised so that it is available to U-Boot. This inhibits
688 that so that the environment is not available until explicitly loaded
689 later by U-Boot code. With CONFIG_OF_CONTROL this is instead
690 controlled by the value of /config/load-environment.
692 config ENV_IMPORT_FDT
693 bool "Amend environment by FDT properties"
694 depends on OF_CONTROL
696 If selected, after the environment has been loaded from its
697 persistent location, the "env_fdt_path" variable is looked
698 up and used as a path to a node in the control DTB. The
699 property/value pairs in that node is then used to update the
700 run-time environment. This can be useful to use the same
701 U-Boot binary with different board variants.
704 string "Default value for env_fdt_path variable"
705 depends on ENV_IMPORT_FDT
706 default "/config/environment"
708 The initial value of the env_fdt_path variable.
711 bool "Always append the environment with new data"
713 If defined, the environment hash table is only ever appended with new
714 data, but the existing hash table can never be dropped and reloaded
715 with newly imported data. This may be used in combination with static
716 flags to e.g. to protect variables which must not be modified.
718 config ENV_WRITEABLE_LIST
719 bool "Permit write access only to listed variables"
721 If defined, only environment variables which explicitly set the 'w'
722 writeable flag can be written and modified at runtime. No variables
723 can be otherwise created, written or imported into the environment.
725 config ENV_ACCESS_IGNORE_FORCE
726 bool "Block forced environment operations"
728 If defined, don't allow the -f switch to env set override variable
732 config SPL_ENV_IS_NOWHERE
733 bool "SPL Environment is not stored"
734 default y if ENV_IS_NOWHERE
736 Similar to ENV_IS_NOWHERE, used for SPL environment.
738 config SPL_ENV_IS_IN_MMC
739 bool "SPL Environment in an MMC device"
740 depends on !SPL_ENV_IS_NOWHERE
741 depends on ENV_IS_IN_MMC
744 Similar to ENV_IS_IN_MMC, used for SPL environment.
746 config SPL_ENV_IS_IN_FAT
747 bool "SPL Environment is in a FAT filesystem"
748 depends on !SPL_ENV_IS_NOWHERE
749 depends on ENV_IS_IN_FAT
752 Similar to ENV_IS_IN_FAT, used for SPL environment.
754 config SPL_ENV_IS_IN_EXT4
755 bool "SPL Environment is in a EXT4 filesystem"
756 depends on !SPL_ENV_IS_NOWHERE
757 depends on ENV_IS_IN_EXT4
760 Similar to ENV_IS_IN_EXT4, used for SPL environment.
762 config SPL_ENV_IS_IN_NAND
763 bool "SPL Environment in a NAND device"
764 depends on !SPL_ENV_IS_NOWHERE
765 depends on ENV_IS_IN_NAND
768 Similar to ENV_IS_IN_NAND, used for SPL environment.
770 config SPL_ENV_IS_IN_SPI_FLASH
771 bool "SPL Environment is in SPI flash"
772 depends on !SPL_ENV_IS_NOWHERE
773 depends on ENV_IS_IN_SPI_FLASH
776 Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
778 config SPL_ENV_IS_IN_FLASH
779 bool "SPL Environment in flash memory"
780 depends on !SPL_ENV_IS_NOWHERE
781 depends on ENV_IS_IN_FLASH
784 Similar to ENV_IS_IN_FLASH, used for SPL environment.
790 config TPL_ENV_IS_NOWHERE
791 bool "TPL Environment is not stored"
792 default y if ENV_IS_NOWHERE
794 Similar to ENV_IS_NOWHERE, used for TPL environment.
796 config TPL_ENV_IS_IN_MMC
797 bool "TPL Environment in an MMC device"
798 depends on !TPL_ENV_IS_NOWHERE
799 depends on ENV_IS_IN_MMC
802 Similar to ENV_IS_IN_MMC, used for TPL environment.
804 config TPL_ENV_IS_IN_FAT
805 bool "TPL Environment is in a FAT filesystem"
806 depends on !TPL_ENV_IS_NOWHERE
807 depends on ENV_IS_IN_FAT
810 Similar to ENV_IS_IN_FAT, used for TPL environment.
812 config TPL_ENV_IS_IN_EXT4
813 bool "TPL Environment is in a EXT4 filesystem"
814 depends on !TPL_ENV_IS_NOWHERE
815 depends on ENV_IS_IN_EXT4
818 Similar to ENV_IS_IN_EXT4, used for TPL environment.
820 config TPL_ENV_IS_IN_NAND
821 bool "TPL Environment in a NAND device"
822 depends on !TPL_ENV_IS_NOWHERE
823 depends on ENV_IS_IN_NAND
826 Similar to ENV_IS_IN_NAND, used for TPL environment.
828 config TPL_ENV_IS_IN_SPI_FLASH
829 bool "TPL Environment is in SPI flash"
830 depends on !TPL_ENV_IS_NOWHERE
831 depends on ENV_IS_IN_SPI_FLASH
834 Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
836 config TPL_ENV_IS_IN_FLASH
837 bool "TPL Environment in flash memory"
838 depends on !TPL_ENV_IS_NOWHERE
839 depends on ENV_IS_IN_FLASH
842 Similar to ENV_IS_IN_FLASH, used for TPL environment.
847 bool "Add a 'bootfile' environment variable"
849 The "bootfile" variable is used in some cases to allow for
850 controlling what file U-Boot will attempt to load and boot. To set
851 this, enable this option and set the value in the next question.
854 string "'bootfile' environment variable value"
855 depends on USE_BOOTFILE
857 The value to set the "bootfile" variable to.
860 bool "Add an 'ethprime' environment variable"
862 The "ethprime" variable is used in some cases to control which
863 network interface is used first.
866 string "'ethprime' environment variable value"
867 depends on USE_ETHPRIME
869 The value to set the "ethprime" variable to.
872 bool "Set a default 'hostname' value in the environment"
876 string "Value of the default 'hostname' value in the environment"
877 depends on USE_HOSTNAME
881 config VERSION_VARIABLE
882 bool "Add a 'ver' environment variable with the U-Boot version"
884 If this variable is defined, an environment variable
885 named "ver" is created by U-Boot showing the U-Boot
886 version as printed by the "version" command.
887 Any change to this variable will be reverted at the