Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see the file Documentation/kbuild/kconfig-language.txt in the
  4. # Linux kernel source tree.
  5. #
  6. mainmenu "U-Boot $UBOOTVERSION Configuration"
  7. config UBOOTVERSION
  8. string
  9. option env="UBOOTVERSION"
  10. # Allow defaults in arch-specific code to override any given here
  11. source "arch/Kconfig"
  12. menu "General setup"
  13. config BROKEN
  14. bool
  15. help
  16. This option cannot be enabled. It is used as dependency
  17. for broken and incomplete features.
  18. config LOCALVERSION
  19. string "Local version - append to U-Boot release"
  20. help
  21. Append an extra string to the end of your U-Boot version.
  22. This will show up in your boot log, for example.
  23. The string you set here will be appended after the contents of
  24. any files with a filename matching localversion* in your
  25. object and source tree, in that order. Your total string can
  26. be a maximum of 64 characters.
  27. config LOCALVERSION_AUTO
  28. bool "Automatically append version information to the version string"
  29. default y
  30. help
  31. This will try to automatically determine if the current tree is a
  32. release tree by looking for Git tags that belong to the current
  33. top of tree revision.
  34. A string of the format -gxxxxxxxx will be added to the localversion
  35. if a Git-based tree is found. The string generated by this will be
  36. appended after any matching localversion* files, and after the value
  37. set in CONFIG_LOCALVERSION.
  38. (The actual string used here is the first eight characters produced
  39. by running the command:
  40. $ git rev-parse --verify HEAD
  41. which is done within the script "scripts/setlocalversion".)
  42. config CC_OPTIMIZE_FOR_SIZE
  43. bool "Optimize for size"
  44. default y
  45. help
  46. Enabling this option will pass "-Os" instead of "-O2" to gcc
  47. resulting in a smaller U-Boot image.
  48. This option is enabled by default for U-Boot.
  49. config CC_COVERAGE
  50. bool "Enable code coverage analysis"
  51. depends on SANDBOX
  52. help
  53. Enabling this option will pass "--coverage" to gcc to compile
  54. and link code instrumented for coverage analysis.
  55. config DISTRO_DEFAULTS
  56. bool "Select defaults suitable for booting general purpose Linux distributions"
  57. select AUTO_COMPLETE
  58. select CMDLINE_EDITING
  59. select CMD_BOOTI if ARM64
  60. select CMD_BOOTZ if ARM && !ARM64
  61. select CMD_DHCP if CMD_NET
  62. select CMD_ENV_EXISTS
  63. select CMD_EXT2
  64. select CMD_EXT4
  65. select CMD_FAT
  66. select CMD_FS_GENERIC
  67. select CMD_PART if PARTITIONS
  68. select CMD_PING if CMD_NET
  69. select CMD_PXE if NET
  70. select ENV_VARS_UBOOT_CONFIG
  71. select HUSH_PARSER
  72. select SUPPORT_RAW_INITRD
  73. select SYS_LONGHELP
  74. imply CMD_MII if NET
  75. imply USB_STORAGE
  76. imply USE_BOOTCOMMAND
  77. help
  78. Select this to enable various options and commands which are suitable
  79. for building u-boot for booting general purpose Linux distributions.
  80. config ENV_VARS_UBOOT_CONFIG
  81. bool "Add arch, board, vendor and soc variables to default environment"
  82. help
  83. Define this in order to add variables describing the
  84. U-Boot build configuration to the default environment.
  85. These will be named arch, cpu, board, vendor, and soc.
  86. Enabling this option will cause the following to be defined:
  87. - CONFIG_SYS_ARCH
  88. - CONFIG_SYS_CPU
  89. - CONFIG_SYS_BOARD
  90. - CONFIG_SYS_VENDOR
  91. - CONFIG_SYS_SOC
  92. config NR_DRAM_BANKS
  93. int "Number of DRAM banks"
  94. default 4
  95. help
  96. This defines the number of DRAM banks.
  97. config SYS_BOOT_GET_CMDLINE
  98. bool "Enable kernel command line setup"
  99. help
  100. Enables allocating and saving kernel cmdline in space between
  101. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  102. config SYS_BOOT_GET_KBD
  103. bool "Enable kernel board information setup"
  104. help
  105. Enables allocating and saving a kernel copy of the bd_info in
  106. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  107. config SYS_MALLOC_F
  108. bool "Enable malloc() pool before relocation"
  109. default y if DM
  110. help
  111. Before relocation, memory is very limited on many platforms. Still,
  112. we can provide a small malloc() pool if needed. Driver model in
  113. particular needs this to operate, so that it can allocate the
  114. initial serial device and any others that are needed.
  115. config SYS_MALLOC_F_LEN
  116. hex "Size of malloc() pool before relocation"
  117. depends on SYS_MALLOC_F
  118. default 0x1000 if AM33XX
  119. default 0x400
  120. help
  121. Before relocation, memory is very limited on many platforms. Still,
  122. we can provide a small malloc() pool if needed. Driver model in
  123. particular needs this to operate, so that it can allocate the
  124. initial serial device and any others that are needed.
  125. config SYS_MALLOC_LEN
  126. hex "Define memory for Dynamic allocation"
  127. depends on ARCH_ZYNQ || ARCH_VERSAL
  128. help
  129. This defines memory to be allocated for Dynamic allocation
  130. TODO: Use for other architectures
  131. config SPL_SYS_MALLOC_F_LEN
  132. hex "Size of malloc() pool in SPL before relocation"
  133. depends on SYS_MALLOC_F
  134. default SYS_MALLOC_F_LEN
  135. help
  136. Before relocation, memory is very limited on many platforms. Still,
  137. we can provide a small malloc() pool if needed. Driver model in
  138. particular needs this to operate, so that it can allocate the
  139. initial serial device and any others that are needed.
  140. config TPL_SYS_MALLOC_F_LEN
  141. hex "Size of malloc() pool in TPL before relocation"
  142. depends on SYS_MALLOC_F
  143. default SYS_MALLOC_F_LEN
  144. help
  145. Before relocation, memory is very limited on many platforms. Still,
  146. we can provide a small malloc() pool if needed. Driver model in
  147. particular needs this to operate, so that it can allocate the
  148. initial serial device and any others that are needed.
  149. menuconfig EXPERT
  150. bool "Configure standard U-Boot features (expert users)"
  151. default y
  152. help
  153. This option allows certain base U-Boot options and settings
  154. to be disabled or tweaked. This is for specialized
  155. environments which can tolerate a "non-standard" U-Boot.
  156. Use this only if you really know what you are doing.
  157. if EXPERT
  158. config SYS_MALLOC_CLEAR_ON_INIT
  159. bool "Init with zeros the memory reserved for malloc (slow)"
  160. default y
  161. help
  162. This setting is enabled by default. The reserved malloc
  163. memory is initialized with zeros, so first malloc calls
  164. will return the pointer to the zeroed memory. But this
  165. slows the boot time.
  166. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  167. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  168. Then the boot time can be significantly reduced.
  169. Warning:
  170. When disabling this, please check if malloc calls, maybe
  171. should be replaced by calloc - if one expects zeroed memory.
  172. config TOOLS_DEBUG
  173. bool "Enable debug information for tools"
  174. help
  175. Enable generation of debug information for tools such as mkimage.
  176. This can be used for debugging purposes. With debug information
  177. it is possible to set breakpoints on particular lines, single-step
  178. debug through the source code, etc.
  179. endif # EXPERT
  180. config PHYS_64BIT
  181. bool "64bit physical address support"
  182. help
  183. Say Y here to support 64bit physical memory address.
  184. This can be used not only for 64bit SoCs, but also for
  185. large physical address extention on 32bit SoCs.
  186. config BUILD_ROM
  187. bool "Build U-Boot as BIOS replacement"
  188. depends on X86
  189. help
  190. This option allows to build a ROM version of U-Boot.
  191. The build process generally requires several binary blobs
  192. which are not shipped in the U-Boot source tree.
  193. Please, see doc/README.x86 for details.
  194. endmenu # General setup
  195. menu "Boot images"
  196. config ANDROID_BOOT_IMAGE
  197. bool "Enable support for Android Boot Images"
  198. default y if FASTBOOT
  199. help
  200. This enables support for booting images which use the Android
  201. image format header.
  202. config FIT
  203. bool "Support Flattened Image Tree"
  204. select MD5
  205. select SHA1
  206. help
  207. This option allows you to boot the new uImage structure,
  208. Flattened Image Tree. FIT is formally a FDT, which can include
  209. images of various types (kernel, FDT blob, ramdisk, etc.)
  210. in a single blob. To boot this new uImage structure,
  211. pass the address of the blob to the "bootm" command.
  212. FIT is very flexible, supporting compression, multiple images,
  213. multiple configurations, verification through hashing and also
  214. verified boot (secure boot using RSA).
  215. if FIT
  216. config FIT_ENABLE_SHA256_SUPPORT
  217. bool "Support SHA256 checksum of FIT image contents"
  218. default y
  219. select SHA256
  220. help
  221. Enable this to support SHA256 checksum of FIT image contents. A
  222. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  223. the image contents have not been corrupted. SHA256 is recommended
  224. for use in secure applications since (as at 2016) there is no known
  225. feasible attack that could produce a 'collision' with differing
  226. input data. Use this for the highest security. Note that only the
  227. SHA256 variant is supported: SHA512 and others are not currently
  228. supported in U-Boot.
  229. config FIT_SIGNATURE
  230. bool "Enable signature verification of FIT uImages"
  231. depends on DM
  232. select HASH
  233. select RSA
  234. help
  235. This option enables signature verification of FIT uImages,
  236. using a hash signed and verified using RSA. If
  237. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  238. hashing is available using hardware, then the RSA library will use
  239. it. See doc/uImage.FIT/signature.txt for more details.
  240. WARNING: When relying on signed FIT images with a required signature
  241. check the legacy image format is disabled by default, so that
  242. unsigned images cannot be loaded. If a board needs the legacy image
  243. format support in this case, enable it using
  244. CONFIG_IMAGE_FORMAT_LEGACY.
  245. config FIT_SIGNATURE_MAX_SIZE
  246. hex "Max size of signed FIT structures"
  247. depends on FIT_SIGNATURE
  248. default 0x10000000
  249. help
  250. This option sets a max size in bytes for verified FIT uImages.
  251. A sane value of 256MB protects corrupted DTB structures from overlapping
  252. device memory. Assure this size does not extend past expected storage
  253. space.
  254. config FIT_ENABLE_RSASSA_PSS_SUPPORT
  255. bool "Support rsassa-pss signature scheme of FIT image contents"
  256. depends on FIT_SIGNATURE
  257. default n
  258. help
  259. Enable this to support the pss padding algorithm as described
  260. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  261. config FIT_VERBOSE
  262. bool "Show verbose messages when FIT images fail"
  263. help
  264. Generally a system will have valid FIT images so debug messages
  265. are a waste of code space. If you are debugging your images then
  266. you can enable this option to get more verbose information about
  267. failures.
  268. config FIT_BEST_MATCH
  269. bool "Select the best match for the kernel device tree"
  270. help
  271. When no configuration is explicitly selected, default to the
  272. one whose fdt's compatibility field best matches that of
  273. U-Boot itself. A match is considered "best" if it matches the
  274. most specific compatibility entry of U-Boot's fdt's root node.
  275. The order of entries in the configuration's fdt is ignored.
  276. config FIT_IMAGE_POST_PROCESS
  277. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  278. depends on TI_SECURE_DEVICE
  279. help
  280. Allows doing any sort of manipulation to blobs after they got extracted
  281. from FIT images like stripping off headers or modifying the size of the
  282. blob, verification, authentication, decryption etc. in a platform or
  283. board specific way. In order to use this feature a platform or board-
  284. specific implementation of board_fit_image_post_process() must be
  285. provided. Also, anything done during this post-processing step would
  286. need to be comprehended in how the images were prepared before being
  287. injected into the FIT creation (i.e. the blobs would have been pre-
  288. processed before being added to the FIT image).
  289. if SPL
  290. config SPL_FIT
  291. bool "Support Flattened Image Tree within SPL"
  292. depends on SPL
  293. select SPL_OF_LIBFDT
  294. config SPL_FIT_PRINT
  295. bool "Support FIT printing within SPL"
  296. depends on SPL_FIT
  297. help
  298. Support printing the content of the fitImage in a verbose manner in SPL.
  299. config SPL_FIT_SIGNATURE
  300. bool "Enable signature verification of FIT firmware within SPL"
  301. depends on SPL_DM
  302. select SPL_FIT
  303. select SPL_RSA
  304. config SPL_LOAD_FIT
  305. bool "Enable SPL loading U-Boot as a FIT"
  306. select SPL_FIT
  307. help
  308. Normally with the SPL framework a legacy image is generated as part
  309. of the build. This contains U-Boot along with information as to
  310. where it should be loaded. This option instead enables generation
  311. of a FIT (Flat Image Tree) which provides more flexibility. In
  312. particular it can handle selecting from multiple device tree
  313. and passing the correct one to U-Boot.
  314. config SPL_LOAD_FIT_FULL
  315. bool "Enable SPL loading U-Boot as a FIT"
  316. select SPL_FIT
  317. help
  318. Normally with the SPL framework a legacy image is generated as part
  319. of the build. This contains U-Boot along with information as to
  320. where it should be loaded. This option instead enables generation
  321. of a FIT (Flat Image Tree) which provides more flexibility. In
  322. particular it can handle selecting from multiple device tree
  323. and passing the correct one to U-Boot.
  324. config SPL_FIT_IMAGE_POST_PROCESS
  325. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  326. depends on SPL_LOAD_FIT
  327. help
  328. Allows doing any sort of manipulation to blobs after they got extracted
  329. from the U-Boot FIT image like stripping off headers or modifying the
  330. size of the blob, verification, authentication, decryption etc. in a
  331. platform or board specific way. In order to use this feature a platform
  332. or board-specific implementation of board_fit_image_post_process() must
  333. be provided. Also, anything done during this post-processing step would
  334. need to be comprehended in how the images were prepared before being
  335. injected into the FIT creation (i.e. the blobs would have been pre-
  336. processed before being added to the FIT image).
  337. config SPL_FIT_SOURCE
  338. string ".its source file for U-Boot FIT image"
  339. depends on SPL_FIT
  340. help
  341. Specifies a (platform specific) FIT source file to generate the
  342. U-Boot FIT image. This could specify further image to load and/or
  343. execute.
  344. config SPL_FIT_GENERATOR
  345. string ".its file generator script for U-Boot FIT image"
  346. depends on SPL_FIT
  347. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  348. help
  349. Specifies a (platform specific) script file to generate the FIT
  350. source file used to build the U-Boot FIT image file. This gets
  351. passed a list of supported device tree file stub names to
  352. include in the generated image.
  353. endif # SPL
  354. endif # FIT
  355. config IMAGE_FORMAT_LEGACY
  356. bool "Enable support for the legacy image format"
  357. default y if !FIT_SIGNATURE
  358. help
  359. This option enables the legacy image format. It is enabled by
  360. default for backward compatibility, unless FIT_SIGNATURE is
  361. set where it is disabled so that unsigned images cannot be
  362. loaded. If a board needs the legacy image format support in this
  363. case, enable it here.
  364. config OF_BOARD_SETUP
  365. bool "Set up board-specific details in device tree before boot"
  366. depends on OF_LIBFDT
  367. help
  368. This causes U-Boot to call ft_board_setup() before booting into
  369. the Operating System. This function can set up various
  370. board-specific information in the device tree for use by the OS.
  371. The device tree is then passed to the OS.
  372. config OF_SYSTEM_SETUP
  373. bool "Set up system-specific details in device tree before boot"
  374. depends on OF_LIBFDT
  375. help
  376. This causes U-Boot to call ft_system_setup() before booting into
  377. the Operating System. This function can set up various
  378. system-specific information in the device tree for use by the OS.
  379. The device tree is then passed to the OS.
  380. config OF_STDOUT_VIA_ALIAS
  381. bool "Update the device-tree stdout alias from U-Boot"
  382. depends on OF_LIBFDT
  383. help
  384. This uses U-Boot's serial alias from the aliases node to update
  385. the device tree passed to the OS. The "linux,stdout-path" property
  386. in the chosen node is set to point to the correct serial node.
  387. This option currently references CONFIG_CONS_INDEX, which is
  388. incorrect when used with device tree as this option does not
  389. exist / should not be used.
  390. config SYS_EXTRA_OPTIONS
  391. string "Extra Options (DEPRECATED)"
  392. help
  393. The old configuration infrastructure (= mkconfig + boards.cfg)
  394. provided the extra options field. If you have something like
  395. "HAS_BAR,BAZ=64", the optional options
  396. #define CONFIG_HAS
  397. #define CONFIG_BAZ 64
  398. will be defined in include/config.h.
  399. This option was prepared for the smooth migration from the old
  400. configuration to Kconfig. Since this option will be removed sometime,
  401. new boards should not use this option.
  402. config SYS_TEXT_BASE
  403. depends on !NIOS2 && !XTENSA
  404. depends on !EFI_APP
  405. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  406. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  407. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  408. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  409. hex "Text Base"
  410. help
  411. The address in memory that U-Boot will be running from, initially.
  412. config SYS_CLK_FREQ
  413. depends on ARC || ARCH_SUNXI
  414. int "CPU clock frequency"
  415. help
  416. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  417. config ARCH_FIXUP_FDT_MEMORY
  418. bool "Enable arch_fixup_memory_banks() call"
  419. default y
  420. help
  421. Enable FDT memory map syncup before OS boot. This feature can be
  422. used for booting OS with different memory setup where the part of
  423. the memory location should be used for different purpose.
  424. endmenu # Boot images
  425. source "api/Kconfig"
  426. source "common/Kconfig"
  427. source "cmd/Kconfig"
  428. source "disk/Kconfig"
  429. source "dts/Kconfig"
  430. source "env/Kconfig"
  431. source "net/Kconfig"
  432. source "drivers/Kconfig"
  433. source "fs/Kconfig"
  434. source "lib/Kconfig"
  435. source "test/Kconfig"