Kconfig 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700
  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. comment "Compiler: $(CC_VERSION_TEXT)"
  8. source "scripts/Kconfig.include"
  9. # Allow defaults in arch-specific code to override any given here
  10. source "arch/Kconfig"
  11. menu "General setup"
  12. config BROKEN
  13. bool
  14. help
  15. This option cannot be enabled. It is used as dependency
  16. for broken and incomplete features.
  17. config DEPRECATED
  18. bool
  19. help
  20. This option cannot be enabled. It it used as a dependency for
  21. code that relies on deprecated features that will be removed and
  22. the conversion deadline has passed.
  23. config LOCALVERSION
  24. string "Local version - append to U-Boot release"
  25. help
  26. Append an extra string to the end of your U-Boot version.
  27. This will show up in your boot log, for example.
  28. The string you set here will be appended after the contents of
  29. any files with a filename matching localversion* in your
  30. object and source tree, in that order. Your total string can
  31. be a maximum of 64 characters.
  32. config LOCALVERSION_AUTO
  33. bool "Automatically append version information to the version string"
  34. default y
  35. help
  36. This will try to automatically determine if the current tree is a
  37. release tree by looking for Git tags that belong to the current
  38. top of tree revision.
  39. A string of the format -gxxxxxxxx will be added to the localversion
  40. if a Git-based tree is found. The string generated by this will be
  41. appended after any matching localversion* files, and after the value
  42. set in CONFIG_LOCALVERSION.
  43. (The actual string used here is the first eight characters produced
  44. by running the command:
  45. $ git rev-parse --verify HEAD
  46. which is done within the script "scripts/setlocalversion".)
  47. config CC_OPTIMIZE_FOR_SIZE
  48. bool "Optimize for size"
  49. default y
  50. help
  51. Enabling this option will pass "-Os" instead of "-O2" to gcc
  52. resulting in a smaller U-Boot image.
  53. This option is enabled by default for U-Boot.
  54. config OPTIMIZE_INLINING
  55. bool "Allow compiler to uninline functions marked 'inline' in full U-Boot"
  56. default n
  57. help
  58. This option determines if U-Boot forces gcc to inline the functions
  59. developers have marked 'inline'. Doing so takes away freedom from gcc to
  60. do what it thinks is best, which is desirable in some cases for size
  61. reasons.
  62. config SPL_OPTIMIZE_INLINING
  63. bool "Allow compiler to uninline functions marked 'inline' in SPL"
  64. depends on SPL
  65. default n
  66. help
  67. This option determines if U-Boot forces gcc to inline the functions
  68. developers have marked 'inline'. Doing so takes away freedom from gcc to
  69. do what it thinks is best, which is desirable in some cases for size
  70. reasons.
  71. config TPL_OPTIMIZE_INLINING
  72. bool "Allow compiler to uninline functions marked 'inline' in TPL"
  73. depends on TPL
  74. default n
  75. help
  76. This option determines if U-Boot forces gcc to inline the functions
  77. developers have marked 'inline'. Doing so takes away freedom from gcc to
  78. do what it thinks is best, which is desirable in some cases for size
  79. reasons.
  80. config CC_COVERAGE
  81. bool "Enable code coverage analysis"
  82. depends on SANDBOX
  83. help
  84. Enabling this option will pass "--coverage" to gcc to compile
  85. and link code instrumented for coverage analysis.
  86. config CC_HAS_ASM_INLINE
  87. def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null)
  88. config DISTRO_DEFAULTS
  89. bool "Select defaults suitable for booting general purpose Linux distributions"
  90. select AUTO_COMPLETE
  91. select CMDLINE_EDITING
  92. select CMD_BOOTI if ARM64
  93. select CMD_BOOTZ if ARM && !ARM64
  94. select CMD_DHCP if CMD_NET
  95. select CMD_ENV_EXISTS
  96. select CMD_EXT2
  97. select CMD_EXT4
  98. select CMD_FAT
  99. select CMD_FS_GENERIC
  100. select CMD_PART if PARTITIONS
  101. select CMD_PING if CMD_NET
  102. select CMD_PXE if NET
  103. select CMD_SYSBOOT
  104. select ENV_VARS_UBOOT_CONFIG
  105. select HUSH_PARSER
  106. select SUPPORT_RAW_INITRD
  107. select SYS_LONGHELP
  108. imply CMD_MII if NET
  109. imply USB_STORAGE
  110. imply USE_BOOTCOMMAND
  111. help
  112. Select this to enable various options and commands which are suitable
  113. for building u-boot for booting general purpose Linux distributions.
  114. config ENV_VARS_UBOOT_CONFIG
  115. bool "Add arch, board, vendor and soc variables to default environment"
  116. help
  117. Define this in order to add variables describing the
  118. U-Boot build configuration to the default environment.
  119. These will be named arch, cpu, board, vendor, and soc.
  120. Enabling this option will cause the following to be defined:
  121. - CONFIG_SYS_ARCH
  122. - CONFIG_SYS_CPU
  123. - CONFIG_SYS_BOARD
  124. - CONFIG_SYS_VENDOR
  125. - CONFIG_SYS_SOC
  126. config NR_DRAM_BANKS
  127. int "Number of DRAM banks"
  128. default 1 if ARCH_SUNXI || ARCH_OWL
  129. default 4
  130. help
  131. This defines the number of DRAM banks.
  132. config SYS_BOOT_GET_CMDLINE
  133. bool "Enable kernel command line setup"
  134. help
  135. Enables allocating and saving kernel cmdline in space between
  136. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  137. config SYS_BOOT_GET_KBD
  138. bool "Enable kernel board information setup"
  139. help
  140. Enables allocating and saving a kernel copy of the bd_info in
  141. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  142. config SYS_MALLOC_F
  143. bool "Enable malloc() pool before relocation"
  144. default y if DM
  145. help
  146. Before relocation, memory is very limited on many platforms. Still,
  147. we can provide a small malloc() pool if needed. Driver model in
  148. particular needs this to operate, so that it can allocate the
  149. initial serial device and any others that are needed.
  150. config SYS_MALLOC_F_LEN
  151. hex "Size of malloc() pool before relocation"
  152. depends on SYS_MALLOC_F
  153. default 0x1000 if AM33XX
  154. default 0x2800 if SANDBOX
  155. default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
  156. ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
  157. ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
  158. ARCH_LS1046A || ARCH_QEMU)
  159. default 0x400
  160. help
  161. Before relocation, memory is very limited on many platforms. Still,
  162. we can provide a small malloc() pool if needed. Driver model in
  163. particular needs this to operate, so that it can allocate the
  164. initial serial device and any others that are needed.
  165. config SYS_MALLOC_LEN
  166. hex "Define memory for Dynamic allocation"
  167. depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
  168. default 0x2000000 if ARCH_ROCKCHIP
  169. help
  170. This defines memory to be allocated for Dynamic allocation
  171. TODO: Use for other architectures
  172. config SPL_SYS_MALLOC_F_LEN
  173. hex "Size of malloc() pool in SPL before relocation"
  174. depends on SYS_MALLOC_F && SPL
  175. default 0x2800 if RCAR_GEN3
  176. default SYS_MALLOC_F_LEN
  177. help
  178. Before relocation, memory is very limited on many platforms. Still,
  179. we can provide a small malloc() pool if needed. Driver model in
  180. particular needs this to operate, so that it can allocate the
  181. initial serial device and any others that are needed.
  182. config TPL_SYS_MALLOC_F_LEN
  183. hex "Size of malloc() pool in TPL before relocation"
  184. depends on SYS_MALLOC_F && TPL
  185. default SYS_MALLOC_F_LEN
  186. help
  187. Before relocation, memory is very limited on many platforms. Still,
  188. we can provide a small malloc() pool if needed. Driver model in
  189. particular needs this to operate, so that it can allocate the
  190. initial serial device and any others that are needed.
  191. menuconfig EXPERT
  192. bool "Configure standard U-Boot features (expert users)"
  193. default y
  194. help
  195. This option allows certain base U-Boot options and settings
  196. to be disabled or tweaked. This is for specialized
  197. environments which can tolerate a "non-standard" U-Boot.
  198. Use this only if you really know what you are doing.
  199. if EXPERT
  200. config SYS_MALLOC_CLEAR_ON_INIT
  201. bool "Init with zeros the memory reserved for malloc (slow)"
  202. default y
  203. help
  204. This setting is enabled by default. The reserved malloc
  205. memory is initialized with zeros, so first malloc calls
  206. will return the pointer to the zeroed memory. But this
  207. slows the boot time.
  208. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  209. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  210. Then the boot time can be significantly reduced.
  211. Warning:
  212. When disabling this, please check if malloc calls, maybe
  213. should be replaced by calloc - if one expects zeroed memory.
  214. config SYS_MALLOC_DEFAULT_TO_INIT
  215. bool "Default malloc to init while reserving the memory for it"
  216. default n
  217. help
  218. It may happen that one needs to move the dynamic allocation
  219. from one to another memory range, eg. when moving the malloc
  220. from the limited static to a potentially large dynamic (DDR)
  221. memory.
  222. If so then on top of setting the updated memory aside one
  223. needs to bring the malloc init.
  224. If such a scenario is sought choose yes.
  225. config TOOLS_DEBUG
  226. bool "Enable debug information for tools"
  227. help
  228. Enable generation of debug information for tools such as mkimage.
  229. This can be used for debugging purposes. With debug information
  230. it is possible to set breakpoints on particular lines, single-step
  231. debug through the source code, etc.
  232. endif # EXPERT
  233. config PHYS_64BIT
  234. bool "64bit physical address support"
  235. help
  236. Say Y here to support 64bit physical memory address.
  237. This can be used not only for 64bit SoCs, but also for
  238. large physical address extension on 32bit SoCs.
  239. config BUILD_ROM
  240. bool "Build U-Boot as BIOS replacement"
  241. depends on X86
  242. help
  243. This option allows to build a ROM version of U-Boot.
  244. The build process generally requires several binary blobs
  245. which are not shipped in the U-Boot source tree.
  246. Please, see doc/arch/x86.rst for details.
  247. config SPL_IMAGE
  248. string "SPL image used in the combined SPL+U-Boot image"
  249. default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  250. default "spl/u-boot-spl.bin"
  251. depends on SPL
  252. help
  253. Select the SPL build target that shall be generated by the SPL
  254. build process (default spl/u-boot-spl.bin). This image will be
  255. used to generate a combined image with SPL and main U-Boot
  256. proper as one single image.
  257. config BUILD_TARGET
  258. string "Build target special images"
  259. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
  260. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
  261. default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
  262. default "u-boot-elf.srec" if RCAR_GEN3
  263. default "u-boot.itb" if SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
  264. ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
  265. default "u-boot.kwb" if ARCH_KIRKWOOD
  266. default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  267. default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
  268. help
  269. Some SoCs need special image types (e.g. U-Boot binary
  270. with a special header) as build targets. By defining
  271. CONFIG_BUILD_TARGET in the SoC / board header, this
  272. special image will be automatically built upon calling
  273. make / buildman.
  274. config SYS_CUSTOM_LDSCRIPT
  275. bool "Use a custom location for the U-Boot linker script"
  276. help
  277. Normally when linking U-Boot we will look in the board directory,
  278. the CPU directory and finally the "cpu" directory of the architecture
  279. for the ile "u-boot.lds" and use that as our linker. However, in
  280. some cases we need to provide a different linker script. To do so,
  281. enable this option and then provide the location under
  282. CONFIG_SYS_LDSCRIPT.
  283. config SYS_LDSCRIPT
  284. depends on SYS_CUSTOM_LDSCRIPT
  285. string "Custom ldscript location"
  286. help
  287. Path within the source tree to the linker script to use for the
  288. main U-Boot binary.
  289. config ERR_PTR_OFFSET
  290. hex
  291. default 0x0
  292. help
  293. Some U-Boot pointers have redundant information, so we can use a
  294. scheme where we can return either an error code or a pointer with the
  295. same return value. The default implementation just casts the pointer
  296. to a number, however, this may fail on platforms where the end of the
  297. address range is used for valid pointers (e.g. 0xffffff00 is a valid
  298. heap pointer in socfpga SPL).
  299. For such platforms, this value provides an upper range of those error
  300. pointer values - up to 'MAX_ERRNO' bytes below this value must be
  301. unused/invalid addresses.
  302. config PLATFORM_ELFENTRY
  303. string
  304. default "__start" if MIPS
  305. default "_start"
  306. endmenu # General setup
  307. menu "Boot images"
  308. config ANDROID_BOOT_IMAGE
  309. bool "Enable support for Android Boot Images"
  310. default y if FASTBOOT
  311. help
  312. This enables support for booting images which use the Android
  313. image format header.
  314. config FIT
  315. bool "Support Flattened Image Tree"
  316. select MD5
  317. select SHA1
  318. help
  319. This option allows you to boot the new uImage structure,
  320. Flattened Image Tree. FIT is formally a FDT, which can include
  321. images of various types (kernel, FDT blob, ramdisk, etc.)
  322. in a single blob. To boot this new uImage structure,
  323. pass the address of the blob to the "bootm" command.
  324. FIT is very flexible, supporting compression, multiple images,
  325. multiple configurations, verification through hashing and also
  326. verified boot (secure boot using RSA).
  327. if FIT
  328. config FIT_EXTERNAL_OFFSET
  329. hex "FIT external data offset"
  330. default 0x0
  331. help
  332. This specifies a data offset in fit image.
  333. The offset is from data payload offset to the beginning of
  334. fit image header. When specifies a offset, specific data
  335. could be put in the hole between data payload and fit image
  336. header, such as CSF data on i.MX platform.
  337. config FIT_ENABLE_SHA256_SUPPORT
  338. bool "Support SHA256 checksum of FIT image contents"
  339. default y
  340. select SHA256
  341. help
  342. Enable this to support SHA256 checksum of FIT image contents. A
  343. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  344. the image contents have not been corrupted.
  345. config FIT_ENABLE_SHA384_SUPPORT
  346. bool "Support SHA384 checksum of FIT image contents"
  347. default n
  348. select SHA384
  349. help
  350. Enable this to support SHA384 checksum of FIT image contents. A
  351. SHA384 checksum is a 384-bit (48-byte) hash value used to check that
  352. the image contents have not been corrupted. Use this for the highest
  353. security.
  354. config FIT_ENABLE_SHA512_SUPPORT
  355. bool "Support SHA512 checksum of FIT image contents"
  356. default n
  357. select SHA512
  358. help
  359. Enable this to support SHA512 checksum of FIT image contents. A
  360. SHA512 checksum is a 512-bit (64-byte) hash value used to check that
  361. the image contents have not been corrupted.
  362. config FIT_SIGNATURE
  363. bool "Enable signature verification of FIT uImages"
  364. depends on DM
  365. select HASH
  366. select RSA
  367. select RSA_VERIFY
  368. select IMAGE_SIGN_INFO
  369. help
  370. This option enables signature verification of FIT uImages,
  371. using a hash signed and verified using RSA. If
  372. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  373. hashing is available using hardware, then the RSA library will use
  374. it. See doc/uImage.FIT/signature.txt for more details.
  375. WARNING: When relying on signed FIT images with a required signature
  376. check the legacy image format is disabled by default, so that
  377. unsigned images cannot be loaded. If a board needs the legacy image
  378. format support in this case, enable it using
  379. CONFIG_LEGACY_IMAGE_FORMAT.
  380. config FIT_SIGNATURE_MAX_SIZE
  381. hex "Max size of signed FIT structures"
  382. depends on FIT_SIGNATURE
  383. default 0x10000000
  384. help
  385. This option sets a max size in bytes for verified FIT uImages.
  386. A sane value of 256MB protects corrupted DTB structures from overlapping
  387. device memory. Assure this size does not extend past expected storage
  388. space.
  389. config FIT_ENABLE_RSASSA_PSS_SUPPORT
  390. bool "Support rsassa-pss signature scheme of FIT image contents"
  391. depends on FIT_SIGNATURE
  392. default n
  393. help
  394. Enable this to support the pss padding algorithm as described
  395. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  396. config FIT_CIPHER
  397. bool "Enable ciphering data in a FIT uImages"
  398. depends on DM
  399. select AES
  400. help
  401. Enable the feature of data ciphering/unciphering in the tool mkimage
  402. and in the u-boot support of the FIT image.
  403. config FIT_VERBOSE
  404. bool "Show verbose messages when FIT images fail"
  405. help
  406. Generally a system will have valid FIT images so debug messages
  407. are a waste of code space. If you are debugging your images then
  408. you can enable this option to get more verbose information about
  409. failures.
  410. config FIT_BEST_MATCH
  411. bool "Select the best match for the kernel device tree"
  412. help
  413. When no configuration is explicitly selected, default to the
  414. one whose fdt's compatibility field best matches that of
  415. U-Boot itself. A match is considered "best" if it matches the
  416. most specific compatibility entry of U-Boot's fdt's root node.
  417. The order of entries in the configuration's fdt is ignored.
  418. config FIT_IMAGE_POST_PROCESS
  419. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  420. depends on TI_SECURE_DEVICE
  421. help
  422. Allows doing any sort of manipulation to blobs after they got extracted
  423. from FIT images like stripping off headers or modifying the size of the
  424. blob, verification, authentication, decryption etc. in a platform or
  425. board specific way. In order to use this feature a platform or board-
  426. specific implementation of board_fit_image_post_process() must be
  427. provided. Also, anything done during this post-processing step would
  428. need to be comprehended in how the images were prepared before being
  429. injected into the FIT creation (i.e. the blobs would have been pre-
  430. processed before being added to the FIT image).
  431. if SPL
  432. config SPL_FIT
  433. bool "Support Flattened Image Tree within SPL"
  434. depends on SPL
  435. select SPL_OF_LIBFDT
  436. config SPL_FIT_PRINT
  437. bool "Support FIT printing within SPL"
  438. depends on SPL_FIT
  439. help
  440. Support printing the content of the fitImage in a verbose manner in SPL.
  441. config SPL_FIT_SIGNATURE
  442. bool "Enable signature verification of FIT firmware within SPL"
  443. depends on SPL_DM
  444. select SPL_FIT
  445. select SPL_HASH_SUPPORT
  446. select SPL_RSA
  447. select SPL_RSA_VERIFY
  448. select SPL_IMAGE_SIGN_INFO
  449. config SPL_LOAD_FIT
  450. bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
  451. select SPL_FIT
  452. help
  453. Normally with the SPL framework a legacy image is generated as part
  454. of the build. This contains U-Boot along with information as to
  455. where it should be loaded. This option instead enables generation
  456. of a FIT (Flat Image Tree) which provides more flexibility. In
  457. particular it can handle selecting from multiple device tree
  458. and passing the correct one to U-Boot.
  459. config SPL_LOAD_FIT_APPLY_OVERLAY
  460. bool "Enable SPL applying DT overlays from FIT"
  461. depends on SPL_LOAD_FIT
  462. select OF_LIBFDT_OVERLAY
  463. help
  464. The device tree is loaded from the FIT image. Allow the SPL is to
  465. also load device-tree overlays from the FIT image an apply them
  466. over the device tree.
  467. config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
  468. depends on SPL_LOAD_FIT_APPLY_OVERLAY
  469. default 0x10000
  470. hex "size of temporary buffer used to load the overlays"
  471. help
  472. The size of the area where the overlays will be loaded and
  473. uncompress. Must be at least as large as biggest overlay
  474. (uncompressed)
  475. config SPL_LOAD_FIT_FULL
  476. bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
  477. select SPL_FIT
  478. help
  479. Normally with the SPL framework a legacy image is generated as part
  480. of the build. This contains U-Boot along with information as to
  481. where it should be loaded. This option instead enables generation
  482. of a FIT (Flat Image Tree) which provides more flexibility. In
  483. particular it can handle selecting from multiple device tree
  484. and passing the correct one to U-Boot.
  485. config SPL_FIT_IMAGE_POST_PROCESS
  486. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  487. depends on SPL_LOAD_FIT
  488. help
  489. Allows doing any sort of manipulation to blobs after they got extracted
  490. from the U-Boot FIT image like stripping off headers or modifying the
  491. size of the blob, verification, authentication, decryption etc. in a
  492. platform or board specific way. In order to use this feature a platform
  493. or board-specific implementation of board_fit_image_post_process() must
  494. be provided. Also, anything done during this post-processing step would
  495. need to be comprehended in how the images were prepared before being
  496. injected into the FIT creation (i.e. the blobs would have been pre-
  497. processed before being added to the FIT image).
  498. config SPL_FIT_SOURCE
  499. string ".its source file for U-Boot FIT image"
  500. depends on SPL_FIT
  501. help
  502. Specifies a (platform specific) FIT source file to generate the
  503. U-Boot FIT image. This could specify further image to load and/or
  504. execute.
  505. config SPL_FIT_GENERATOR
  506. string ".its file generator script for U-Boot FIT image"
  507. depends on SPL_FIT
  508. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  509. default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
  510. default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
  511. default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
  512. help
  513. Specifies a (platform specific) script file to generate the FIT
  514. source file used to build the U-Boot FIT image file. This gets
  515. passed a list of supported device tree file stub names to
  516. include in the generated image.
  517. endif # SPL
  518. endif # FIT
  519. config LEGACY_IMAGE_FORMAT
  520. bool "Enable support for the legacy image format"
  521. default y if !FIT_SIGNATURE
  522. help
  523. This option enables the legacy image format. It is enabled by
  524. default for backward compatibility, unless FIT_SIGNATURE is
  525. set where it is disabled so that unsigned images cannot be
  526. loaded. If a board needs the legacy image format support in this
  527. case, enable it here.
  528. config OF_BOARD_SETUP
  529. bool "Set up board-specific details in device tree before boot"
  530. depends on OF_LIBFDT
  531. help
  532. This causes U-Boot to call ft_board_setup() before booting into
  533. the Operating System. This function can set up various
  534. board-specific information in the device tree for use by the OS.
  535. The device tree is then passed to the OS.
  536. config OF_SYSTEM_SETUP
  537. bool "Set up system-specific details in device tree before boot"
  538. depends on OF_LIBFDT
  539. help
  540. This causes U-Boot to call ft_system_setup() before booting into
  541. the Operating System. This function can set up various
  542. system-specific information in the device tree for use by the OS.
  543. The device tree is then passed to the OS.
  544. config OF_STDOUT_VIA_ALIAS
  545. bool "Update the device-tree stdout alias from U-Boot"
  546. depends on OF_LIBFDT
  547. help
  548. This uses U-Boot's serial alias from the aliases node to update
  549. the device tree passed to the OS. The "linux,stdout-path" property
  550. in the chosen node is set to point to the correct serial node.
  551. This option currently references CONFIG_CONS_INDEX, which is
  552. incorrect when used with device tree as this option does not
  553. exist / should not be used.
  554. config SYS_EXTRA_OPTIONS
  555. string "Extra Options (DEPRECATED)"
  556. help
  557. The old configuration infrastructure (= mkconfig + boards.cfg)
  558. provided the extra options field. If you have something like
  559. "HAS_BAR,BAZ=64", the optional options
  560. #define CONFIG_HAS
  561. #define CONFIG_BAZ 64
  562. will be defined in include/config.h.
  563. This option was prepared for the smooth migration from the old
  564. configuration to Kconfig. Since this option will be removed sometime,
  565. new boards should not use this option.
  566. config HAVE_SYS_TEXT_BASE
  567. bool
  568. depends on !NIOS2 && !XTENSA
  569. depends on !EFI_APP
  570. default y
  571. config SYS_TEXT_BASE
  572. depends on HAVE_SYS_TEXT_BASE
  573. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  574. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  575. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  576. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  577. hex "Text Base"
  578. help
  579. The address in memory that U-Boot will be running from, initially.
  580. config SYS_CLK_FREQ
  581. depends on ARC || ARCH_SUNXI || MPC83xx
  582. int "CPU clock frequency"
  583. help
  584. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  585. config ARCH_FIXUP_FDT_MEMORY
  586. bool "Enable arch_fixup_memory_banks() call"
  587. default y
  588. help
  589. Enable FDT memory map syncup before OS boot. This feature can be
  590. used for booting OS with different memory setup where the part of
  591. the memory location should be used for different purpose.
  592. endmenu # Boot images
  593. source "api/Kconfig"
  594. source "common/Kconfig"
  595. source "cmd/Kconfig"
  596. source "disk/Kconfig"
  597. source "dts/Kconfig"
  598. source "env/Kconfig"
  599. source "net/Kconfig"
  600. source "drivers/Kconfig"
  601. source "fs/Kconfig"
  602. source "lib/Kconfig"
  603. source "test/Kconfig"