Kconfig 16 KB

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