Kconfig 25 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775
  1. menu "Environment"
  2. config ENV_SUPPORT
  3. def_bool y
  4. config SAVEENV
  5. def_bool y if CMD_SAVEENV
  6. config ENV_OVERWRITE
  7. bool "Enable overwriting environment"
  8. help
  9. Use this to permit overriding of certain environmental variables
  10. like Ethernet and Serial
  11. config ENV_IS_NOWHERE
  12. bool "Environment is not stored"
  13. default y if !ENV_IS_IN_EEPROM && !ENV_IS_IN_EXT4 && \
  14. !ENV_IS_IN_FAT && !ENV_IS_IN_FLASH && \
  15. !ENV_IS_IN_MMC && !ENV_IS_IN_NAND && \
  16. !ENV_IS_IN_NVRAM && !ENV_IS_IN_ONENAND && \
  17. !ENV_IS_IN_REMOTE && !ENV_IS_IN_SPI_FLASH && \
  18. !ENV_IS_IN_UBI
  19. help
  20. Define this if you don't want to or can't have an environment stored
  21. on a storage medium. In this case the environment will still exist
  22. while U-Boot is running, but once U-Boot exits it will not be
  23. stored. U-Boot will therefore always start up with a default
  24. environment.
  25. config ENV_IS_IN_EEPROM
  26. bool "Environment in EEPROM"
  27. depends on !CHAIN_OF_TRUST
  28. help
  29. Use this if you have an EEPROM or similar serial access
  30. device and a driver for it.
  31. - CONFIG_ENV_OFFSET:
  32. - CONFIG_ENV_SIZE:
  33. These two #defines specify the offset and size of the
  34. environment area within the total memory of your EEPROM.
  35. Note that we consider the length of the address field to
  36. still be one byte because the extra address bits are hidden
  37. in the chip address.
  38. - CONFIG_ENV_EEPROM_IS_ON_I2C
  39. define this, if you have I2C and SPI activated, and your
  40. EEPROM, which holds the environment, is on the I2C bus.
  41. - CONFIG_I2C_ENV_EEPROM_BUS
  42. if you have an Environment on an EEPROM reached over
  43. I2C muxes, you can define here, how to reach this
  44. EEPROM. For example:
  45. #define CONFIG_I2C_ENV_EEPROM_BUS 1
  46. EEPROM which holds the environment, is reached over
  47. a pca9547 i2c mux with address 0x70, channel 3.
  48. config ENV_IS_IN_FAT
  49. bool "Environment is in a FAT filesystem"
  50. depends on !CHAIN_OF_TRUST
  51. default y if ARCH_BCM283X
  52. default y if ARCH_SUNXI && MMC
  53. default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
  54. select FS_FAT
  55. select FAT_WRITE
  56. help
  57. Define this if you want to use the FAT file system for the environment.
  58. config ENV_IS_IN_EXT4
  59. bool "Environment is in a EXT4 filesystem"
  60. depends on !CHAIN_OF_TRUST
  61. select EXT4_WRITE
  62. help
  63. Define this if you want to use the EXT4 file system for the environment.
  64. config ENV_IS_IN_FLASH
  65. bool "Environment in flash memory"
  66. depends on !CHAIN_OF_TRUST
  67. default y if ARCH_CINTEGRATOR
  68. default y if ARCH_INTEGRATOR_CP
  69. default y if M548x || M547x || M5282 || MCF547x_8x
  70. default y if MCF532x || MCF52x2
  71. default y if MPC86xx || MPC83xx
  72. default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
  73. default y if SH && !CPU_SH4
  74. help
  75. Define this if you have a flash device which you want to use for the
  76. environment.
  77. a) The environment occupies one whole flash sector, which is
  78. "embedded" in the text segment with the U-Boot code. This
  79. happens usually with "bottom boot sector" or "top boot
  80. sector" type flash chips, which have several smaller
  81. sectors at the start or the end. For instance, such a
  82. layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  83. such a case you would place the environment in one of the
  84. 4 kB sectors - with U-Boot code before and after it. With
  85. "top boot sector" type flash chips, you would put the
  86. environment in one of the last sectors, leaving a gap
  87. between U-Boot and the environment.
  88. CONFIG_ENV_OFFSET:
  89. Offset of environment data (variable area) to the
  90. beginning of flash memory; for instance, with bottom boot
  91. type flash chips the second sector can be used: the offset
  92. for this sector is given here.
  93. CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
  94. CONFIG_ENV_ADDR:
  95. This is just another way to specify the start address of
  96. the flash sector containing the environment (instead of
  97. CONFIG_ENV_OFFSET).
  98. CONFIG_ENV_SECT_SIZE:
  99. Size of the sector containing the environment.
  100. b) Sometimes flash chips have few, equal sized, BIG sectors.
  101. In such a case you don't want to spend a whole sector for
  102. the environment.
  103. CONFIG_ENV_SIZE:
  104. If you use this in combination with CONFIG_ENV_IS_IN_FLASH
  105. and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
  106. of this flash sector for the environment. This saves
  107. memory for the RAM copy of the environment.
  108. It may also save flash memory if you decide to use this
  109. when your environment is "embedded" within U-Boot code,
  110. since then the remainder of the flash sector could be used
  111. for U-Boot code. It should be pointed out that this is
  112. STRONGLY DISCOURAGED from a robustness point of view:
  113. updating the environment in flash makes it always
  114. necessary to erase the WHOLE sector. If something goes
  115. wrong before the contents has been restored from a copy in
  116. RAM, your target system will be dead.
  117. CONFIG_ENV_ADDR_REDUND
  118. These settings describe a second storage area used to hold
  119. a redundant copy of the environment data, so that there is
  120. a valid backup copy in case there is a power failure during
  121. a "saveenv" operation.
  122. BE CAREFUL! Any changes to the flash layout, and some changes to the
  123. source code will make it necessary to adapt <board>/u-boot.lds*
  124. accordingly!
  125. config ENV_IS_IN_MMC
  126. bool "Environment in an MMC device"
  127. depends on !CHAIN_OF_TRUST
  128. depends on MMC
  129. default y if ARCH_EXYNOS4
  130. default y if MX6SX || MX7D
  131. default y if TEGRA30 || TEGRA124
  132. default y if TEGRA_ARMV8_COMMON
  133. help
  134. Define this if you have an MMC device which you want to use for the
  135. environment.
  136. CONFIG_SYS_MMC_ENV_DEV:
  137. Specifies which MMC device the environment is stored in.
  138. CONFIG_SYS_MMC_ENV_PART (optional):
  139. Specifies which MMC partition the environment is stored in. If not
  140. set, defaults to partition 0, the user area. Common values might be
  141. 1 (first MMC boot partition), 2 (second MMC boot partition).
  142. CONFIG_ENV_OFFSET:
  143. CONFIG_ENV_SIZE:
  144. These two #defines specify the offset and size of the environment
  145. area within the specified MMC device.
  146. If offset is positive (the usual case), it is treated as relative to
  147. the start of the MMC partition. If offset is negative, it is treated
  148. as relative to the end of the MMC partition. This can be useful if
  149. your board may be fitted with different MMC devices, which have
  150. different sizes for the MMC partitions, and you always want the
  151. environment placed at the very end of the partition, to leave the
  152. maximum possible space before it, to store other data.
  153. These two values are in units of bytes, but must be aligned to an
  154. MMC sector boundary.
  155. CONFIG_ENV_OFFSET_REDUND (optional):
  156. Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
  157. hold a redundant copy of the environment data. This provides a
  158. valid backup copy in case the other copy is corrupted, e.g. due
  159. to a power failure during a "saveenv" operation.
  160. This value may also be positive or negative; this is handled in the
  161. same way as CONFIG_ENV_OFFSET.
  162. This value is also in units of bytes, but must also be aligned to
  163. an MMC sector boundary.
  164. config ENV_IS_IN_NAND
  165. bool "Environment in a NAND device"
  166. depends on !CHAIN_OF_TRUST
  167. help
  168. Define this if you have a NAND device which you want to use for the
  169. environment.
  170. - CONFIG_ENV_OFFSET:
  171. - CONFIG_ENV_SIZE:
  172. These two #defines specify the offset and size of the environment
  173. area within the first NAND device. CONFIG_ENV_OFFSET must be
  174. aligned to an erase block boundary.
  175. - CONFIG_ENV_OFFSET_REDUND (optional):
  176. This setting describes a second storage area of CONFIG_ENV_SIZE
  177. size used to hold a redundant copy of the environment data, so
  178. that there is a valid backup copy in case there is a power failure
  179. during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
  180. aligned to an erase block boundary.
  181. - CONFIG_ENV_RANGE (optional):
  182. Specifies the length of the region in which the environment
  183. can be written. This should be a multiple of the NAND device's
  184. block size. Specifying a range with more erase blocks than
  185. are needed to hold CONFIG_ENV_SIZE allows bad blocks within
  186. the range to be avoided.
  187. - CONFIG_ENV_OFFSET_OOB (optional):
  188. Enables support for dynamically retrieving the offset of the
  189. environment from block zero's out-of-band data. The
  190. "nand env.oob" command can be used to record this offset.
  191. Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
  192. using CONFIG_ENV_OFFSET_OOB.
  193. config ENV_IS_IN_NVRAM
  194. bool "Environment in a non-volatile RAM"
  195. depends on !CHAIN_OF_TRUST
  196. help
  197. Define this if you have some non-volatile memory device
  198. (NVRAM, battery buffered SRAM) which you want to use for the
  199. environment.
  200. - CONFIG_ENV_ADDR:
  201. - CONFIG_ENV_SIZE:
  202. These two #defines are used to determine the memory area you
  203. want to use for environment. It is assumed that this memory
  204. can just be read and written to, without any special
  205. provision.
  206. config ENV_IS_IN_ONENAND
  207. bool "Environment is in OneNAND"
  208. depends on !CHAIN_OF_TRUST
  209. help
  210. Define this if you want to put your local device's environment in
  211. OneNAND.
  212. - CONFIG_ENV_ADDR:
  213. - CONFIG_ENV_SIZE:
  214. These two #defines are used to determine the device range you
  215. want to use for environment. It is assumed that this memory
  216. can just be read and written to, without any special
  217. provision.
  218. config ENV_IS_IN_REMOTE
  219. bool "Environment is in remote memory space"
  220. depends on !CHAIN_OF_TRUST
  221. help
  222. Define this if you have a remote memory space which you
  223. want to use for the local device's environment.
  224. - CONFIG_ENV_ADDR:
  225. - CONFIG_ENV_SIZE:
  226. These two #defines specify the address and size of the
  227. environment area within the remote memory space. The
  228. local device can get the environment from remote memory
  229. space by SRIO or PCIE links.
  230. config ENV_IS_IN_SPI_FLASH
  231. bool "Environment is in SPI flash"
  232. depends on !CHAIN_OF_TRUST && SPI
  233. default y if ARMADA_XP
  234. default y if INTEL_BAYTRAIL
  235. default y if INTEL_BRASWELL
  236. default y if INTEL_BROADWELL
  237. default y if NORTHBRIDGE_INTEL_IVYBRIDGE
  238. default y if INTEL_QUARK
  239. default y if INTEL_QUEENSBAY
  240. help
  241. Define this if you have a SPI Flash memory device which you
  242. want to use for the environment.
  243. - CONFIG_ENV_OFFSET:
  244. - CONFIG_ENV_SIZE:
  245. These two #defines specify the offset and size of the
  246. environment area within the SPI Flash. CONFIG_ENV_OFFSET must be
  247. aligned to an erase sector boundary.
  248. - CONFIG_ENV_SECT_SIZE:
  249. Define the SPI flash's sector size.
  250. - CONFIG_ENV_OFFSET_REDUND (optional):
  251. This setting describes a second storage area of CONFIG_ENV_SIZE
  252. size used to hold a redundant copy of the environment data, so
  253. that there is a valid backup copy in case there is a power failure
  254. during a "saveenv" operation. CONFIG_ENV_OFFSET_REDUND must be
  255. aligned to an erase sector boundary.
  256. config USE_ENV_SPI_BUS
  257. bool "SPI flash bus for environment"
  258. depends on ENV_IS_IN_SPI_FLASH
  259. help
  260. Force the SPI bus for environment.
  261. If not defined, use CONFIG_SF_DEFAULT_BUS.
  262. config ENV_SPI_BUS
  263. int "Value of SPI flash bus for environment"
  264. depends on USE_ENV_SPI_BUS
  265. help
  266. Value the SPI bus and chip select for environment.
  267. config USE_ENV_SPI_CS
  268. bool "SPI flash chip select for environment"
  269. depends on ENV_IS_IN_SPI_FLASH
  270. help
  271. Force the SPI chip select for environment.
  272. If not defined, use CONFIG_SF_DEFAULT_CS.
  273. config ENV_SPI_CS
  274. int "Value of SPI flash chip select for environment"
  275. depends on USE_ENV_SPI_CS
  276. help
  277. Value of the SPI chip select for environment.
  278. config USE_ENV_SPI_MAX_HZ
  279. bool "SPI flash max frequency for environment"
  280. depends on ENV_IS_IN_SPI_FLASH
  281. help
  282. Force the SPI max work clock for environment.
  283. If not defined, use CONFIG_SF_DEFAULT_SPEED.
  284. config ENV_SPI_MAX_HZ
  285. int "Value of SPI flash max frequency for environment"
  286. depends on USE_ENV_SPI_MAX_HZ
  287. help
  288. Value of the SPI max work clock for environment.
  289. config USE_ENV_SPI_MODE
  290. bool "SPI flash mode for environment"
  291. depends on ENV_IS_IN_SPI_FLASH
  292. help
  293. Force the SPI work mode for environment.
  294. config ENV_SPI_MODE
  295. hex "Value of SPI flash work mode for environment"
  296. depends on USE_ENV_SPI_MODE
  297. help
  298. Value of the SPI work mode for environment.
  299. See include/spi.h for value.
  300. config ENV_IS_IN_UBI
  301. bool "Environment in a UBI volume"
  302. depends on !CHAIN_OF_TRUST
  303. depends on MTD_UBI
  304. depends on CMD_UBI
  305. help
  306. Define this if you have an UBI volume that you want to use for the
  307. environment. This has the benefit of wear-leveling the environment
  308. accesses, which is important on NAND.
  309. - CONFIG_ENV_UBI_PART:
  310. Define this to a string that is the mtd partition containing the UBI.
  311. - CONFIG_ENV_UBI_VOLUME:
  312. Define this to the name of the volume that you want to store the
  313. environment in.
  314. - CONFIG_ENV_UBI_VOLUME_REDUND:
  315. Define this to the name of another volume to store a second copy of
  316. the environment in. This will enable redundant environments in UBI.
  317. It is assumed that both volumes are in the same MTD partition.
  318. config SYS_REDUNDAND_ENVIRONMENT
  319. bool "Enable redundant environment support"
  320. depends on ENV_IS_IN_EEPROM || ENV_IS_IN_FLASH || ENV_IS_IN_MMC || \
  321. ENV_IS_IN_NAND || ENV_IS_IN_SPI_FLASH || ENV_IS_IN_UBI
  322. help
  323. Normally, the environemt is stored in a single location. By
  324. selecting this option, you can then define where to hold a redundant
  325. copy of the environment data, so that there is a valid backup copy in
  326. case there is a power failure during a "saveenv" operation.
  327. config ENV_FAT_INTERFACE
  328. string "Name of the block device for the environment"
  329. depends on ENV_IS_IN_FAT
  330. default "mmc"
  331. help
  332. Define this to a string that is the name of the block device.
  333. config ENV_FAT_DEVICE_AND_PART
  334. string "Device and partition for where to store the environemt in FAT"
  335. depends on ENV_IS_IN_FAT
  336. default "0:1" if TI_COMMON_CMD_OPTIONS
  337. default "0:auto" if ARCH_ZYNQMP
  338. default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
  339. default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
  340. default "0" if ARCH_AT91
  341. help
  342. Define this to a string to specify the partition of the device. It can
  343. be as following:
  344. "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
  345. - "D:P": device D partition P. Error occurs if device D has no
  346. partition table.
  347. - "D:0": device D.
  348. - "D" or "D:": device D partition 1 if device D has partition
  349. table, or the whole device D if has no partition
  350. table.
  351. - "D:auto": first partition in device D with bootable flag set.
  352. If none, first valid partition in device D. If no
  353. partition table then means device D.
  354. If ENV_FAT_INTERFACE is set to "mmc" then device 'D' can be omitted,
  355. leaving the string starting with a colon, and the boot device will
  356. be used.
  357. config ENV_FAT_FILE
  358. string "Name of the FAT file to use for the environment"
  359. depends on ENV_IS_IN_FAT
  360. default "uboot.env"
  361. help
  362. It's a string of the FAT file name. This file use to store the
  363. environment.
  364. config ENV_EXT4_INTERFACE
  365. string "Name of the block device for the environment"
  366. depends on ENV_IS_IN_EXT4
  367. help
  368. Define this to a string that is the name of the block device.
  369. config ENV_EXT4_DEVICE_AND_PART
  370. string "Device and partition for where to store the environemt in EXT4"
  371. depends on ENV_IS_IN_EXT4
  372. help
  373. Define this to a string to specify the partition of the device. It can
  374. be as following:
  375. "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
  376. - "D:P": device D partition P. Error occurs if device D has no
  377. partition table.
  378. - "D:0": device D.
  379. - "D" or "D:": device D partition 1 if device D has partition
  380. table, or the whole device D if has no partition
  381. table.
  382. - "D:auto": first partition in device D with bootable flag set.
  383. If none, first valid partition in device D. If no
  384. partition table then means device D.
  385. config ENV_EXT4_FILE
  386. string "Name of the EXT4 file to use for the environment"
  387. depends on ENV_IS_IN_EXT4
  388. default "/uboot.env"
  389. help
  390. It's a string of the EXT4 file name. This file use to store the
  391. environment (explicit path to the file)
  392. config ENV_ADDR
  393. hex "Environment address"
  394. depends on ENV_IS_IN_FLASH || ENV_IS_IN_NVRAM || ENV_IS_IN_ONENAND || \
  395. ENV_IS_IN_REMOTE || ENV_IS_IN_SPI_FLASH
  396. default 0x0 if ENV_IS_IN_SPI_FLASH
  397. help
  398. Offset from the start of the device (or partition)
  399. config ENV_ADDR_REDUND
  400. hex "Redundant environment address"
  401. depends on ENV_IS_IN_FLASH && SYS_REDUNDAND_ENVIRONMENT
  402. help
  403. Offset from the start of the device (or partition) of the redundant
  404. environment location.
  405. config ENV_OFFSET
  406. hex "Environment offset"
  407. depends on ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
  408. ENV_IS_IN_SPI_FLASH
  409. default 0x3f8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
  410. default 0x140000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
  411. default 0x88000 if ARCH_SUNXI
  412. default 0xE0000 if ARCH_ZYNQ
  413. default 0x1E00000 if ARCH_ZYNQMP
  414. default 0x7F40000 if ARCH_VERSAL
  415. default 0 if ARC
  416. default 0x140000 if ARCH_AT91
  417. default 0x260000 if ARCH_OMAP2PLUS
  418. default 0x1080000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
  419. help
  420. Offset from the start of the device (or partition)
  421. config ENV_OFFSET_REDUND
  422. hex "Redundant environment offset"
  423. depends on (ENV_IS_IN_EEPROM || ENV_IS_IN_MMC || ENV_IS_IN_NAND || \
  424. ENV_IS_IN_SPI_FLASH) && SYS_REDUNDAND_ENVIRONMENT
  425. help
  426. Offset from the start of the device (or partition) of the redundant
  427. environment location.
  428. config ENV_SIZE
  429. hex "Environment Size"
  430. default 0x40000 if ENV_IS_IN_SPI_FLASH && ARCH_ZYNQMP
  431. default 0x20000 if ARCH_SUNXI || ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
  432. default 0x8000 if ARCH_ROCKCHIP && ENV_IS_IN_MMC
  433. default 0x2000 if ARCH_ROCKCHIP && ENV_IS_IN_SPI_FLASH
  434. default 0x8000 if ARCH_ZYNQMP || ARCH_VERSAL
  435. default 0x4000 if ARC
  436. default 0x1f000
  437. help
  438. Size of the environment storage area
  439. config ENV_SECT_SIZE
  440. hex "Environment Sector-Size"
  441. depends on ENV_IS_IN_FLASH || ENV_IS_IN_SPI_FLASH
  442. default 0x2000 if ARCH_ROCKCHIP
  443. default 0x40000 if ARCH_ZYNQMP || ARCH_VERSAL
  444. default 0x20000 if ARCH_ZYNQ || ARCH_OMAP2PLUS || ARCH_AT91
  445. default 0x20000 if MICROBLAZE && ENV_IS_IN_SPI_FLASH
  446. help
  447. Size of the sector containing the environment.
  448. config ENV_UBI_PART
  449. string "UBI partition name"
  450. depends on ENV_IS_IN_UBI
  451. help
  452. MTD partition containing the UBI device
  453. config ENV_UBI_VOLUME
  454. string "UBI volume name"
  455. depends on ENV_IS_IN_UBI
  456. help
  457. Name of the volume that you want to store the environment in.
  458. config ENV_UBI_VOLUME_REDUND
  459. string "UBI redundant volume name"
  460. depends on ENV_IS_IN_UBI && SYS_REDUNDAND_ENVIRONMENT
  461. help
  462. Name of the redundant volume that you want to store the environment in.
  463. config ENV_UBI_VID_OFFSET
  464. int "ubi environment VID offset"
  465. depends on ENV_IS_IN_UBI
  466. default 0
  467. help
  468. UBI VID offset for environment. If 0, no custom VID offset is used.
  469. config SYS_RELOC_GD_ENV_ADDR
  470. bool "Relocate gd->env_addr"
  471. help
  472. Relocate the early env_addr pointer so we know it is not inside
  473. the binary. Some systems need this and for the rest, it doesn't hurt.
  474. config SYS_MMC_ENV_DEV
  475. int "mmc device number"
  476. depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT || SYS_LS_PPA_FW_IN_MMC || \
  477. CMD_MVEBU_BUBT || FMAN_ENET || QE
  478. default 0
  479. help
  480. MMC device number on the platform where the environment is stored.
  481. config SYS_MMC_ENV_PART
  482. int "mmc partition number"
  483. depends on ENV_IS_IN_MMC || ENV_IS_IN_FAT
  484. default 0
  485. help
  486. MMC hardware partition device number on the platform where the
  487. environment is stored. Note that this is not related to any software
  488. defined partition table but instead if we are in the user area, which is
  489. partition 0 or the first boot partition, which is 1 or some other defined
  490. partition.
  491. config USE_DEFAULT_ENV_FILE
  492. bool "Create default environment from file"
  493. help
  494. Normally, the default environment is automatically generated
  495. based on the settings of various CONFIG_* options, as well
  496. as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
  497. you can instead define the entire default environment in an
  498. external file.
  499. config DEFAULT_ENV_FILE
  500. string "Path to default environment file"
  501. depends on USE_DEFAULT_ENV_FILE
  502. help
  503. The path containing the default environment. The format is
  504. the same as accepted by the mkenvimage tool: lines
  505. containing key=value pairs, blank lines and lines beginning
  506. with # are ignored.
  507. config ENV_VARS_UBOOT_RUNTIME_CONFIG
  508. bool "Add run-time information to the environment"
  509. help
  510. Enable this in order to add variables describing certain
  511. run-time determined information about the hardware to the
  512. environment. These will be named board_name, board_rev.
  513. config DELAY_ENVIRONMENT
  514. bool "Delay environment loading"
  515. depends on !OF_CONTROL
  516. help
  517. Enable this to inhibit loading the environment during board
  518. initialization. This can address the security risk of untrusted data
  519. being used during boot. Normally the environment is loaded when the
  520. board is initialised so that it is available to U-Boot. This inhibits
  521. that so that the environment is not available until explicitly loaded
  522. later by U-Boot code. With CONFIG_OF_CONTROL this is instead
  523. controlled by the value of /config/load-environment.
  524. config ENV_APPEND
  525. bool "Always append the environment with new data"
  526. default n
  527. help
  528. If defined, the environment hash table is only ever appended with new
  529. data, but the existing hash table can never be dropped and reloaded
  530. with newly imported data. This may be used in combination with static
  531. flags to e.g. to protect variables which must not be modified.
  532. config ENV_WRITEABLE_LIST
  533. bool "Permit write access only to listed variables"
  534. default n
  535. help
  536. If defined, only environment variables which explicitly set the 'w'
  537. writeable flag can be written and modified at runtime. No variables
  538. can be otherwise created, written or imported into the environment.
  539. config ENV_ACCESS_IGNORE_FORCE
  540. bool "Block forced environment operations"
  541. default n
  542. help
  543. If defined, don't allow the -f switch to env set override variable
  544. access flags.
  545. if SPL_ENV_SUPPORT
  546. config SPL_ENV_IS_NOWHERE
  547. bool "SPL Environment is not stored"
  548. default y if ENV_IS_NOWHERE
  549. help
  550. Similar to ENV_IS_NOWHERE, used for SPL environment.
  551. config SPL_ENV_IS_IN_MMC
  552. bool "SPL Environment in an MMC device"
  553. depends on !SPL_ENV_IS_NOWHERE
  554. depends on ENV_IS_IN_MMC
  555. default y
  556. help
  557. Similar to ENV_IS_IN_MMC, used for SPL environment.
  558. config SPL_ENV_IS_IN_FAT
  559. bool "SPL Environment is in a FAT filesystem"
  560. depends on !SPL_ENV_IS_NOWHERE
  561. depends on ENV_IS_IN_FAT
  562. default y
  563. help
  564. Similar to ENV_IS_IN_FAT, used for SPL environment.
  565. config SPL_ENV_IS_IN_EXT4
  566. bool "SPL Environment is in a EXT4 filesystem"
  567. depends on !SPL_ENV_IS_NOWHERE
  568. depends on ENV_IS_IN_EXT4
  569. default y
  570. help
  571. Similar to ENV_IS_IN_EXT4, used for SPL environment.
  572. config SPL_ENV_IS_IN_NAND
  573. bool "SPL Environment in a NAND device"
  574. depends on !SPL_ENV_IS_NOWHERE
  575. depends on ENV_IS_IN_NAND
  576. default y
  577. help
  578. Similar to ENV_IS_IN_NAND, used for SPL environment.
  579. config SPL_ENV_IS_IN_SPI_FLASH
  580. bool "SPL Environment is in SPI flash"
  581. depends on !SPL_ENV_IS_NOWHERE
  582. depends on ENV_IS_IN_SPI_FLASH
  583. default y
  584. help
  585. Similar to ENV_IS_IN_SPI_FLASH, used for SPL environment.
  586. config SPL_ENV_IS_IN_FLASH
  587. bool "SPL Environment in flash memory"
  588. depends on !SPL_ENV_IS_NOWHERE
  589. depends on ENV_IS_IN_FLASH
  590. default y
  591. help
  592. Similar to ENV_IS_IN_FLASH, used for SPL environment.
  593. endif
  594. if TPL_ENV_SUPPORT
  595. config TPL_ENV_IS_NOWHERE
  596. bool "TPL Environment is not stored"
  597. default y if ENV_IS_NOWHERE
  598. help
  599. Similar to ENV_IS_NOWHERE, used for TPL environment.
  600. config TPL_ENV_IS_IN_MMC
  601. bool "TPL Environment in an MMC device"
  602. depends on !TPL_ENV_IS_NOWHERE
  603. depends on ENV_IS_IN_MMC
  604. default y
  605. help
  606. Similar to ENV_IS_IN_MMC, used for TPL environment.
  607. config TPL_ENV_IS_IN_FAT
  608. bool "TPL Environment is in a FAT filesystem"
  609. depends on !TPL_ENV_IS_NOWHERE
  610. depends on ENV_IS_IN_FAT
  611. default y
  612. help
  613. Similar to ENV_IS_IN_FAT, used for TPL environment.
  614. config TPL_ENV_IS_IN_EXT4
  615. bool "TPL Environment is in a EXT4 filesystem"
  616. depends on !TPL_ENV_IS_NOWHERE
  617. depends on ENV_IS_IN_EXT4
  618. default y
  619. help
  620. Similar to ENV_IS_IN_EXT4, used for TPL environment.
  621. config TPL_ENV_IS_IN_NAND
  622. bool "TPL Environment in a NAND device"
  623. depends on !TPL_ENV_IS_NOWHERE
  624. depends on ENV_IS_IN_NAND
  625. default y
  626. help
  627. Similar to ENV_IS_IN_NAND, used for TPL environment.
  628. config TPL_ENV_IS_IN_SPI_FLASH
  629. bool "TPL Environment is in SPI flash"
  630. depends on !TPL_ENV_IS_NOWHERE
  631. depends on ENV_IS_IN_SPI_FLASH
  632. default y
  633. help
  634. Similar to ENV_IS_IN_SPI_FLASH, used for TPL environment.
  635. config TPL_ENV_IS_IN_FLASH
  636. bool "TPL Environment in flash memory"
  637. depends on !TPL_ENV_IS_NOWHERE
  638. depends on ENV_IS_IN_FLASH
  639. default y
  640. help
  641. Similar to ENV_IS_IN_FLASH, used for TPL environment.
  642. endif
  643. endmenu