Kconfig 16 KB

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