Kconfig 15 KB

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