Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507
  1. menu "Environment"
  2. config ENV_IS_NOWHERE
  3. bool "Environment is not stored"
  4. depends on !ENV_IS_IN_EEPROM
  5. depends on !ENV_IS_IN_FAT
  6. depends on !ENV_IS_IN_FLASH
  7. depends on !ENV_IS_IN_MMC
  8. depends on !ENV_IS_IN_NAND
  9. depends on !ENV_IS_IN_NVRAM
  10. depends on !ENV_IS_IN_ONENAND
  11. depends on !ENV_IS_IN_REMOTE
  12. depends on !ENV_IS_IN_SPI_FLASH
  13. depends on !ENV_IS_IN_UBI
  14. default y
  15. help
  16. Define this if you don't want to or can't have an environment stored
  17. on a storage medium. In this case the environemnt will still exist
  18. while U-Boot is running, but once U-Boot exits it will not be
  19. stored. U-Boot will therefore always start up with a default
  20. environment.
  21. config ENV_IS_IN_EEPROM
  22. bool "Environment in EEPROM"
  23. depends on !CHAIN_OF_TRUST
  24. help
  25. Use this if you have an EEPROM or similar serial access
  26. device and a driver for it.
  27. - CONFIG_ENV_OFFSET:
  28. - CONFIG_ENV_SIZE:
  29. These two #defines specify the offset and size of the
  30. environment area within the total memory of your EEPROM.
  31. Note that we consider the length of the address field to
  32. still be one byte because the extra address bits are hidden
  33. in the chip address.
  34. - CONFIG_ENV_EEPROM_IS_ON_I2C
  35. define this, if you have I2C and SPI activated, and your
  36. EEPROM, which holds the environment, is on the I2C bus.
  37. - CONFIG_I2C_ENV_EEPROM_BUS
  38. if you have an Environment on an EEPROM reached over
  39. I2C muxes, you can define here, how to reach this
  40. EEPROM. For example:
  41. #define CONFIG_I2C_ENV_EEPROM_BUS 1
  42. EEPROM which holds the environment, is reached over
  43. a pca9547 i2c mux with address 0x70, channel 3.
  44. config ENV_IS_IN_FAT
  45. bool "Environment is in a FAT filesystem"
  46. depends on !CHAIN_OF_TRUST
  47. default y if ARCH_BCM283X
  48. default y if ARCH_SUNXI && MMC
  49. default y if MMC_OMAP_HS && TI_COMMON_CMD_OPTIONS
  50. select FS_FAT
  51. select FAT_WRITE
  52. help
  53. Define this if you want to use the FAT file system for the environment.
  54. config ENV_IS_IN_EXT4
  55. bool "Environment is in a EXT4 filesystem"
  56. depends on !CHAIN_OF_TRUST
  57. select EXT4_WRITE
  58. help
  59. Define this if you want to use the EXT4 file system for the environment.
  60. config ENV_IS_IN_FLASH
  61. bool "Environment in flash memory"
  62. depends on !CHAIN_OF_TRUST
  63. default y if ARCH_CINTEGRATOR
  64. default y if ARCH_INTEGRATOR_CP
  65. default y if M548x || M547x || M5282 || MCF547x_8x
  66. default y if MCF532x || MCF52x2
  67. default y if MPC86xx || MPC83xx
  68. default y if ARCH_MPC8572 || ARCH_MPC8548 || ARCH_MPC8641
  69. default y if SH && !CPU_SH4
  70. help
  71. Define this if you have a flash device which you want to use for the
  72. environment.
  73. a) The environment occupies one whole flash sector, which is
  74. "embedded" in the text segment with the U-Boot code. This
  75. happens usually with "bottom boot sector" or "top boot
  76. sector" type flash chips, which have several smaller
  77. sectors at the start or the end. For instance, such a
  78. layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
  79. such a case you would place the environment in one of the
  80. 4 kB sectors - with U-Boot code before and after it. With
  81. "top boot sector" type flash chips, you would put the
  82. environment in one of the last sectors, leaving a gap
  83. between U-Boot and the environment.
  84. CONFIG_ENV_OFFSET:
  85. Offset of environment data (variable area) to the
  86. beginning of flash memory; for instance, with bottom boot
  87. type flash chips the second sector can be used: the offset
  88. for this sector is given here.
  89. CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
  90. CONFIG_ENV_ADDR:
  91. This is just another way to specify the start address of
  92. the flash sector containing the environment (instead of
  93. CONFIG_ENV_OFFSET).
  94. CONFIG_ENV_SECT_SIZE:
  95. Size of the sector containing the environment.
  96. b) Sometimes flash chips have few, equal sized, BIG sectors.
  97. In such a case you don't want to spend a whole sector for
  98. the environment.
  99. CONFIG_ENV_SIZE:
  100. If you use this in combination with CONFIG_ENV_IS_IN_FLASH
  101. and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
  102. of this flash sector for the environment. This saves
  103. memory for the RAM copy of the environment.
  104. It may also save flash memory if you decide to use this
  105. when your environment is "embedded" within U-Boot code,
  106. since then the remainder of the flash sector could be used
  107. for U-Boot code. It should be pointed out that this is
  108. STRONGLY DISCOURAGED from a robustness point of view:
  109. updating the environment in flash makes it always
  110. necessary to erase the WHOLE sector. If something goes
  111. wrong before the contents has been restored from a copy in
  112. RAM, your target system will be dead.
  113. CONFIG_ENV_ADDR_REDUND
  114. CONFIG_ENV_SIZE_REDUND
  115. These settings describe a second storage area used to hold
  116. a redundant copy of the environment data, so that there is
  117. a valid backup copy in case there is a power failure during
  118. a "saveenv" operation.
  119. BE CAREFUL! Any changes to the flash layout, and some changes to the
  120. source code will make it necessary to adapt <board>/u-boot.lds*
  121. accordingly!
  122. config ENV_IS_IN_MMC
  123. bool "Environment in an MMC device"
  124. depends on !CHAIN_OF_TRUST
  125. depends on MMC
  126. default y if ARCH_EXYNOS4
  127. default y if MX6SX || MX7D
  128. default y if TEGRA30 || TEGRA124
  129. default y if TEGRA_ARMV8_COMMON
  130. help
  131. Define this if you have an MMC device which you want to use for the
  132. environment.
  133. CONFIG_SYS_MMC_ENV_DEV:
  134. Specifies which MMC device the environment is stored in.
  135. CONFIG_SYS_MMC_ENV_PART (optional):
  136. Specifies which MMC partition the environment is stored in. If not
  137. set, defaults to partition 0, the user area. Common values might be
  138. 1 (first MMC boot partition), 2 (second MMC boot partition).
  139. CONFIG_ENV_OFFSET:
  140. CONFIG_ENV_SIZE:
  141. These two #defines specify the offset and size of the environment
  142. area within the specified MMC device.
  143. If offset is positive (the usual case), it is treated as relative to
  144. the start of the MMC partition. If offset is negative, it is treated
  145. as relative to the end of the MMC partition. This can be useful if
  146. your board may be fitted with different MMC devices, which have
  147. different sizes for the MMC partitions, and you always want the
  148. environment placed at the very end of the partition, to leave the
  149. maximum possible space before it, to store other data.
  150. These two values are in units of bytes, but must be aligned to an
  151. MMC sector boundary.
  152. CONFIG_ENV_OFFSET_REDUND (optional):
  153. Specifies a second storage area, of CONFIG_ENV_SIZE size, used to
  154. hold a redundant copy of the environment data. This provides a
  155. valid backup copy in case the other copy is corrupted, e.g. due
  156. to a power failure during a "saveenv" operation.
  157. This value may also be positive or negative; this is handled in the
  158. same way as CONFIG_ENV_OFFSET.
  159. This value is also in units of bytes, but must also be aligned to
  160. an MMC sector boundary.
  161. CONFIG_ENV_SIZE_REDUND (optional):
  162. This value need not be set, even when CONFIG_ENV_OFFSET_REDUND is
  163. set. If this value is set, it must be set to the same value as
  164. CONFIG_ENV_SIZE.
  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 remove 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
  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_SPI_BUS (optional):
  258. - CONFIG_ENV_SPI_CS (optional):
  259. Define the SPI bus and chip select. If not defined they will be 0.
  260. - CONFIG_ENV_SPI_MAX_HZ (optional):
  261. Define the SPI max work clock. If not defined then use 1MHz.
  262. - CONFIG_ENV_SPI_MODE (optional):
  263. Define the SPI work mode. If not defined then use SPI_MODE_3.
  264. config ENV_IS_IN_UBI
  265. bool "Environment in a UBI volume"
  266. depends on !CHAIN_OF_TRUST
  267. help
  268. Define this if you have an UBI volume that you want to use for the
  269. environment. This has the benefit of wear-leveling the environment
  270. accesses, which is important on NAND.
  271. - CONFIG_ENV_UBI_PART:
  272. Define this to a string that is the mtd partition containing the UBI.
  273. - CONFIG_ENV_UBI_VOLUME:
  274. Define this to the name of the volume that you want to store the
  275. environment in.
  276. - CONFIG_ENV_UBI_VOLUME_REDUND:
  277. Define this to the name of another volume to store a second copy of
  278. the environment in. This will enable redundant environments in UBI.
  279. It is assumed that both volumes are in the same MTD partition.
  280. config ENV_FAT_INTERFACE
  281. string "Name of the block device for the environment"
  282. depends on ENV_IS_IN_FAT
  283. default "mmc" if ARCH_SUNXI
  284. default "mmc" if TI_COMMON_CMD_OPTIONS || ARCH_ZYNQMP || ARCH_AT91
  285. help
  286. Define this to a string that is the name of the block device.
  287. config ENV_FAT_DEVICE_AND_PART
  288. string "Device and partition for where to store the environemt in FAT"
  289. depends on ENV_IS_IN_FAT
  290. default "0:1" if TI_COMMON_CMD_OPTIONS
  291. default "0:auto" if ARCH_ZYNQMP
  292. default "0:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA = -1
  293. default "1:auto" if ARCH_SUNXI && MMC_SUNXI_SLOT_EXTRA != -1
  294. default "0" if ARCH_AT91
  295. help
  296. Define this to a string to specify the partition of the device. It can
  297. be as following:
  298. "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
  299. - "D:P": device D partition P. Error occurs if device D has no
  300. partition table.
  301. - "D:0": device D.
  302. - "D" or "D:": device D partition 1 if device D has partition
  303. table, or the whole device D if has no partition
  304. table.
  305. - "D:auto": first partition in device D with bootable flag set.
  306. If none, first valid partition in device D. If no
  307. partition table then means device D.
  308. config ENV_FAT_FILE
  309. string "Name of the FAT file to use for the environemnt"
  310. depends on ENV_IS_IN_FAT
  311. default "uboot.env"
  312. help
  313. It's a string of the FAT file name. This file use to store the
  314. environment.
  315. config ENV_EXT4_INTERFACE
  316. string "Name of the block device for the environment"
  317. depends on ENV_IS_IN_EXT4
  318. help
  319. Define this to a string that is the name of the block device.
  320. config ENV_EXT4_DEVICE_AND_PART
  321. string "Device and partition for where to store the environemt in EXT4"
  322. depends on ENV_IS_IN_EXT4
  323. help
  324. Define this to a string to specify the partition of the device. It can
  325. be as following:
  326. "D:P", "D:0", "D", "D:" or "D:auto" (D, P are integers. And P >= 1)
  327. - "D:P": device D partition P. Error occurs if device D has no
  328. partition table.
  329. - "D:0": device D.
  330. - "D" or "D:": device D partition 1 if device D has partition
  331. table, or the whole device D if has no partition
  332. table.
  333. - "D:auto": first partition in device D with bootable flag set.
  334. If none, first valid partition in device D. If no
  335. partition table then means device D.
  336. config ENV_EXT4_FILE
  337. string "Name of the EXT4 file to use for the environemnt"
  338. depends on ENV_IS_IN_EXT4
  339. default "uboot.env"
  340. help
  341. It's a string of the EXT4 file name. This file use to store the
  342. environment (explicit path to the file)
  343. if ARCH_SUNXI
  344. config ENV_OFFSET
  345. hex "Environment Offset"
  346. depends on !ENV_IS_IN_UBI
  347. depends on !ENV_IS_NOWHERE
  348. default 0x88000 if ARCH_SUNXI
  349. help
  350. Offset from the start of the device (or partition)
  351. config ENV_SIZE
  352. hex "Environment Size"
  353. depends on !ENV_IS_NOWHERE
  354. default 0x20000 if ARCH_SUNXI
  355. help
  356. Size of the environment storage area
  357. config ENV_UBI_PART
  358. string "UBI partition name"
  359. depends on ENV_IS_IN_UBI
  360. help
  361. MTD partition containing the UBI device
  362. config ENV_UBI_VOLUME
  363. string "UBI volume name"
  364. depends on ENV_IS_IN_UBI
  365. help
  366. Name of the volume that you want to store the environment in.
  367. endif
  368. if ARCH_ROCKCHIP
  369. config ENV_OFFSET
  370. hex
  371. depends on !ENV_IS_IN_UBI
  372. depends on !ENV_IS_NOWHERE
  373. default 0x3f8000
  374. help
  375. Offset from the start of the device (or partition)
  376. config ENV_SIZE
  377. hex
  378. default 0x8000
  379. help
  380. Size of the environment storage area
  381. endif
  382. config USE_DEFAULT_ENV_FILE
  383. bool "Create default environment from file"
  384. help
  385. Normally, the default environment is automatically generated
  386. based on the settings of various CONFIG_* options, as well
  387. as the CONFIG_EXTRA_ENV_SETTINGS. By selecting this option,
  388. you can instead define the entire default environment in an
  389. external file.
  390. config DEFAULT_ENV_FILE
  391. string "Path to default environment file"
  392. depends on USE_DEFAULT_ENV_FILE
  393. help
  394. The path containing the default environment. The format is
  395. the same as accepted by the mkenvimage tool: lines
  396. containing key=value pairs, blank lines and lines beginning
  397. with # are ignored.
  398. config ENV_VARS_UBOOT_RUNTIME_CONFIG
  399. bool "Add run-time information to the environment"
  400. help
  401. Enable this in order to add variables describing certain
  402. run-time determined information about the hardware to the
  403. environment. These will be named board_name, board_rev.
  404. endmenu