Kconfig 24 KB

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