Kconfig - OpenGrok cross reference for /OK3568_Linux_fs/u-boot/env/Kconfig

29 	  option to select the location. This is either a device (where the
30 	  environemnt information is simply written to a fixed location or
32 	  information is written to a file).
35 	bool "Environment is not stored"
38 	  on a storage medium. In this case the environemnt will still exist
39 	  while U-Boot is running, but once U-Boot exits it will not be
40 	  stored. U-Boot will therefore always start up with a default
44 	bool "Environment fragment is store in envf partition"
51 	bool "Environment fragment is store in envf partition in SPL"
73 	  - CONFIG_ENV_OFFSET:
74 	  - CONFIG_ENV_SIZE:
83 	  - CONFIG_ENV_EEPROM_IS_ON_I2C
85 	  EEPROM, which holds the environment, is on the I2C bus.
87 	  - CONFIG_I2C_ENV_EEPROM_BUS
94 	  EEPROM which holds the environment, is reached over
98 	bool "Environment is in a FAT filesystem"
104 	  - CONFIG_FAT_WRITE:
114 	  a) The environment occupies one whole flash sector, which is
115 	   "embedded" in the text segment with the U-Boot code. This
116 	   happens usually with "bottom boot sector" or "top boot
121 	   4 kB sectors - with U-Boot code before and after it. With
122 	   "top boot sector" type flash chips, you would put the
124 	   between U-Boot and the environment.
129 	   beginning of flash memory; for instance, with bottom boot
131 	   for this sector is given here.
133 	   CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
137 	   This is just another way to specify the start address of
158 	   when your environment is "embedded" within U-Boot code,
160 	   for U-Boot code. It should be pointed out that this is
171 	   a redundant copy of the environment data, so that there is
172 	   a valid backup copy in case there is a power failure during
176 	  source code will make it necessary to adapt <board>/u-boot.lds*
188 	  Specifies which MMC device the environment is stored in.
192 	  Specifies which MMC partition the environment is stored in. If not
194 	  1 (first MMC boot partition), 2 (second MMC boot partition).
202 	  If offset is positive (the usual case), it is treated as relative to
203 	  the start of the MMC partition. If offset is negative, it is treated
217 	  valid backup copy in case the other copy is corrupted, e.g. due
220 	  This value may also be positive or negative; this is handled in the
223 	  This value is also in units of bytes, but must also be aligned to
228 	  This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
229 	  set. If this value is set, it must be set to the same value as
233 	bool "Environment in a NAND device"
236 	  Define this if you have a NAND device which you want to use for the
239 	  - CONFIG_ENV_OFFSET:
240 	  - CONFIG_ENV_SIZE:
243 	  area within the first NAND device.  CONFIG_ENV_OFFSET must be
246 	  - CONFIG_ENV_OFFSET_REDUND (optional):
250 	  that there is a valid backup copy in case there is a power failure
254 	  - CONFIG_ENV_RANGE (optional):
257 	  can be written.  This should be a multiple of the NAND device's
262 	  - CONFIG_ENV_OFFSET_OOB (optional):
265 	  environment from block zero's out-of-band data.  The
266 	  "nand env.oob" command can be used to record this offset.
267 	  Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
271 	bool "Environment in a non-volatile RAM"
274 	  Define this if you have some non-volatile memory device
278 	  - CONFIG_ENV_ADDR:
279 	  - CONFIG_ENV_SIZE:
282 	  want to use for environment. It is assumed that this memory
287 	bool "Environment is in OneNAND"
293 	  - CONFIG_ENV_ADDR:
294 	  - CONFIG_ENV_SIZE:
297 	  want to use for environment. It is assumed that this memory
302 	bool "Environment is in remove memory space"
308 	  - CONFIG_ENV_ADDR:
309 	  - CONFIG_ENV_SIZE:
317 	bool "Environment is in SPI flash"
323 	  - CONFIG_ENV_OFFSET:
324 	  - CONFIG_ENV_SIZE:
330 	  - CONFIG_ENV_SECT_SIZE:
334 	  - CONFIG_ENV_OFFSET_REDUND (optional):
338 	  that there is a valid backup copy in case there is a power failure
342 	  - CONFIG_ENV_SPI_BUS (optional):
343 	  - CONFIG_ENV_SPI_CS (optional):
347 	  - CONFIG_ENV_SPI_MAX_HZ (optional):
351 	  - CONFIG_ENV_SPI_MODE (optional):
360 	  environment.  This has the benefit of wear-leveling the environment
361 	  accesses, which is important on NAND.
363 	  - CONFIG_ENV_UBI_PART:
365 	  Define this to a string that is the mtd partition containing the UBI.
367 	  - CONFIG_ENV_UBI_VOLUME:
372 	  - CONFIG_ENV_UBI_VOLUME_REDUND:
376 	  It is assumed that both volumes are in the same MTD partition.
378 	  - CONFIG_UBI_SILENCE_MSG
379 	  - CONFIG_UBIFS_SILENCE_MSG
391 	  - CONFIG_ENV_OFFSET:
392 	  - CONFIG_ENV_SIZE:
398 	  - CONFIG_ENV_OFFSET_REDUND (optional):
402 	  valid backup copy in case the other copy is corrupted, e.g. due
403 	  to a power failure during a "saveenv" operation. This is handled
406 	  - CONFIG_ENV_SIZE_REDUND (optional):
408 	  This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
409 	  set. If this value is set, it must be set to the same value as
412 	  - CONFIG_SYS_MMC_ENV_PART (optional):
414 	  Specifies which MMC partition the environment is stored in. If not
416 	  1 (first MMC boot partition), 2 (second MMC boot partition).
421 	bool "AES-128 encryption for stored environment (DEPRECATED)"
423 	  Enable this to have the on-device stored environment be encrypted
424 	  with AES-128.  The implementation here however has security
425 	  complications and is not recommended for use.  Please see
426 	  CVE-2017-3225 and CVE-2017-3226 for more details.
433 	  Define this to a string that is the name of the block device.
446 	       - "D:P": device D partition P. Error occurs if device D has no
448 	       - "D:0": device D.
449 	       - "D" or "D:": device D partition 1 if device D has partition
452 	       - "D:auto": first partition in device D with bootable flag set.
522 	hex "Environment offset in Nand"
526 	hex "Environment redundant(backup) offset in Nand"
530 	hex "Environment size in Nand"