Kconfig 27 KB

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