Kconfig 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767
  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 HAS_ROM
  240. bool
  241. select BINMAN
  242. help
  243. Enables building of a u-boot.rom target. This collects U-Boot and
  244. any necessary binary blobs.
  245. config ROM_NEEDS_BLOBS
  246. bool
  247. depends on HAS_ROM
  248. help
  249. Enable this if building the u-boot.rom target needs binary blobs, and
  250. so cannot be done normally. In this case, U-Boot will only build the
  251. ROM if the required blobs exist. If not, you will see an warning like:
  252. Image 'main-section' is missing external blobs and is non-functional:
  253. intel-descriptor intel-me intel-refcode intel-vga intel-mrc
  254. config BUILD_ROM
  255. bool "Build U-Boot as BIOS replacement"
  256. depends on HAS_ROM
  257. default y if !ROM_NEEDS_BLOBS
  258. help
  259. This option allows to build a ROM version of U-Boot.
  260. The build process generally requires several binary blobs
  261. which are not shipped in the U-Boot source tree.
  262. Please, see doc/arch/x86.rst for details.
  263. config SPL_IMAGE
  264. string "SPL image used in the combined SPL+U-Boot image"
  265. default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  266. default "spl/u-boot-spl.bin"
  267. depends on SPL
  268. help
  269. Select the SPL build target that shall be generated by the SPL
  270. build process (default spl/u-boot-spl.bin). This image will be
  271. used to generate a combined image with SPL and main U-Boot
  272. proper as one single image.
  273. config BUILD_TARGET
  274. string "Build target special images"
  275. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
  276. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
  277. default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
  278. default "u-boot-elf.srec" if RCAR_GEN3
  279. default "u-boot.itb" if !BINMAN && SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
  280. ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
  281. default "u-boot.kwb" if ARCH_KIRKWOOD
  282. default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  283. default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
  284. help
  285. Some SoCs need special image types (e.g. U-Boot binary
  286. with a special header) as build targets. By defining
  287. CONFIG_BUILD_TARGET in the SoC / board header, this
  288. special image will be automatically built upon calling
  289. make / buildman.
  290. config SYS_CUSTOM_LDSCRIPT
  291. bool "Use a custom location for the U-Boot linker script"
  292. help
  293. Normally when linking U-Boot we will look in the board directory,
  294. the CPU directory and finally the "cpu" directory of the architecture
  295. for the ile "u-boot.lds" and use that as our linker. However, in
  296. some cases we need to provide a different linker script. To do so,
  297. enable this option and then provide the location under
  298. CONFIG_SYS_LDSCRIPT.
  299. config SYS_LDSCRIPT
  300. depends on SYS_CUSTOM_LDSCRIPT
  301. string "Custom ldscript location"
  302. help
  303. Path within the source tree to the linker script to use for the
  304. main U-Boot binary.
  305. config ERR_PTR_OFFSET
  306. hex
  307. default 0x0
  308. help
  309. Some U-Boot pointers have redundant information, so we can use a
  310. scheme where we can return either an error code or a pointer with the
  311. same return value. The default implementation just casts the pointer
  312. to a number, however, this may fail on platforms where the end of the
  313. address range is used for valid pointers (e.g. 0xffffff00 is a valid
  314. heap pointer in socfpga SPL).
  315. For such platforms, this value provides an upper range of those error
  316. pointer values - up to 'MAX_ERRNO' bytes below this value must be
  317. unused/invalid addresses.
  318. config PLATFORM_ELFENTRY
  319. string
  320. default "__start" if MIPS
  321. default "_start"
  322. config STACK_SIZE
  323. hex "Define max stack size that can be used by U-Boot"
  324. default 0x4000000 if ARCH_VERSAL || ARCH_ZYNQMP
  325. default 0x200000 if MICROBLAZE
  326. default 0x1000000
  327. help
  328. Define Max stack size that can be used by U-Boot. This value is used
  329. by the UEFI sub-system. On some boards initrd_high is calculated as
  330. base stack pointer minus this stack size.
  331. config SYS_HAS_SRAM
  332. bool
  333. default y if TARGET_PIC32MZDASK
  334. default y if TARGET_DEVKIT8000
  335. default y if TARGET_TRICORDER
  336. default n
  337. help
  338. Enable this to allow support for the on board SRAM.
  339. SRAM base address is controlled by CONFIG_SYS_SRAM_BASE.
  340. SRAM size is controlled by CONFIG_SYS_SRAM_SIZE.
  341. config SYS_SRAM_BASE
  342. hex
  343. default 0x80000000 if TARGET_PIC32MZDASK
  344. default 0x40200000 if TARGET_DEVKIT8000
  345. default 0x40200000 if TARGET_TRICORDER
  346. default 0x0
  347. config SYS_SRAM_SIZE
  348. hex
  349. default 0x00080000 if TARGET_PIC32MZDASK
  350. default 0x10000 if TARGET_DEVKIT8000
  351. default 0x10000 if TARGET_TRICORDER
  352. default 0x0
  353. endmenu # General setup
  354. menu "Boot images"
  355. config ANDROID_BOOT_IMAGE
  356. bool "Enable support for Android Boot Images"
  357. default y if FASTBOOT
  358. help
  359. This enables support for booting images which use the Android
  360. image format header.
  361. config FIT
  362. bool "Support Flattened Image Tree"
  363. select MD5
  364. select SHA1
  365. help
  366. This option allows you to boot the new uImage structure,
  367. Flattened Image Tree. FIT is formally a FDT, which can include
  368. images of various types (kernel, FDT blob, ramdisk, etc.)
  369. in a single blob. To boot this new uImage structure,
  370. pass the address of the blob to the "bootm" command.
  371. FIT is very flexible, supporting compression, multiple images,
  372. multiple configurations, verification through hashing and also
  373. verified boot (secure boot using RSA).
  374. if FIT
  375. config FIT_EXTERNAL_OFFSET
  376. hex "FIT external data offset"
  377. default 0x0
  378. help
  379. This specifies a data offset in fit image.
  380. The offset is from data payload offset to the beginning of
  381. fit image header. When specifies a offset, specific data
  382. could be put in the hole between data payload and fit image
  383. header, such as CSF data on i.MX platform.
  384. config FIT_ENABLE_SHA256_SUPPORT
  385. bool "Support SHA256 checksum of FIT image contents"
  386. default y
  387. select SHA256
  388. help
  389. Enable this to support SHA256 checksum of FIT image contents. A
  390. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  391. the image contents have not been corrupted.
  392. config FIT_ENABLE_SHA384_SUPPORT
  393. bool "Support SHA384 checksum of FIT image contents"
  394. default n
  395. select SHA384
  396. help
  397. Enable this to support SHA384 checksum of FIT image contents. A
  398. SHA384 checksum is a 384-bit (48-byte) hash value used to check that
  399. the image contents have not been corrupted. Use this for the highest
  400. security.
  401. config FIT_ENABLE_SHA512_SUPPORT
  402. bool "Support SHA512 checksum of FIT image contents"
  403. default n
  404. select SHA512
  405. help
  406. Enable this to support SHA512 checksum of FIT image contents. A
  407. SHA512 checksum is a 512-bit (64-byte) hash value used to check that
  408. the image contents have not been corrupted.
  409. config FIT_SIGNATURE
  410. bool "Enable signature verification of FIT uImages"
  411. depends on DM
  412. select HASH
  413. select RSA
  414. select RSA_VERIFY
  415. select IMAGE_SIGN_INFO
  416. help
  417. This option enables signature verification of FIT uImages,
  418. using a hash signed and verified using RSA. If
  419. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  420. hashing is available using hardware, then the RSA library will use
  421. it. See doc/uImage.FIT/signature.txt for more details.
  422. WARNING: When relying on signed FIT images with a required signature
  423. check the legacy image format is disabled by default, so that
  424. unsigned images cannot be loaded. If a board needs the legacy image
  425. format support in this case, enable it using
  426. CONFIG_LEGACY_IMAGE_FORMAT.
  427. config FIT_SIGNATURE_MAX_SIZE
  428. hex "Max size of signed FIT structures"
  429. depends on FIT_SIGNATURE
  430. default 0x10000000
  431. help
  432. This option sets a max size in bytes for verified FIT uImages.
  433. A sane value of 256MB protects corrupted DTB structures from overlapping
  434. device memory. Assure this size does not extend past expected storage
  435. space.
  436. config FIT_ENABLE_RSASSA_PSS_SUPPORT
  437. bool "Support rsassa-pss signature scheme of FIT image contents"
  438. depends on FIT_SIGNATURE
  439. default n
  440. help
  441. Enable this to support the pss padding algorithm as described
  442. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  443. config FIT_CIPHER
  444. bool "Enable ciphering data in a FIT uImages"
  445. depends on DM
  446. select AES
  447. help
  448. Enable the feature of data ciphering/unciphering in the tool mkimage
  449. and in the u-boot support of the FIT image.
  450. config FIT_VERBOSE
  451. bool "Show verbose messages when FIT images fail"
  452. help
  453. Generally a system will have valid FIT images so debug messages
  454. are a waste of code space. If you are debugging your images then
  455. you can enable this option to get more verbose information about
  456. failures.
  457. config FIT_BEST_MATCH
  458. bool "Select the best match for the kernel device tree"
  459. help
  460. When no configuration is explicitly selected, default to the
  461. one whose fdt's compatibility field best matches that of
  462. U-Boot itself. A match is considered "best" if it matches the
  463. most specific compatibility entry of U-Boot's fdt's root node.
  464. The order of entries in the configuration's fdt is ignored.
  465. config FIT_IMAGE_POST_PROCESS
  466. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  467. depends on TI_SECURE_DEVICE
  468. help
  469. Allows doing any sort of manipulation to blobs after they got extracted
  470. from FIT images like stripping off headers or modifying the size of the
  471. blob, verification, authentication, decryption etc. in a platform or
  472. board specific way. In order to use this feature a platform or board-
  473. specific implementation of board_fit_image_post_process() must be
  474. provided. Also, anything done during this post-processing step would
  475. need to be comprehended in how the images were prepared before being
  476. injected into the FIT creation (i.e. the blobs would have been pre-
  477. processed before being added to the FIT image).
  478. if SPL
  479. config SPL_FIT
  480. bool "Support Flattened Image Tree within SPL"
  481. depends on SPL
  482. select SPL_OF_LIBFDT
  483. config SPL_FIT_PRINT
  484. bool "Support FIT printing within SPL"
  485. depends on SPL_FIT
  486. help
  487. Support printing the content of the fitImage in a verbose manner in SPL.
  488. config SPL_FIT_SIGNATURE
  489. bool "Enable signature verification of FIT firmware within SPL"
  490. depends on SPL_DM
  491. select SPL_FIT
  492. select SPL_CRYPTO_SUPPORT
  493. select SPL_HASH_SUPPORT
  494. select SPL_RSA
  495. select SPL_RSA_VERIFY
  496. select SPL_IMAGE_SIGN_INFO
  497. config SPL_LOAD_FIT
  498. bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
  499. select SPL_FIT
  500. help
  501. Normally with the SPL framework a legacy image is generated as part
  502. of the build. This contains U-Boot along with information as to
  503. where it should be loaded. This option instead enables generation
  504. of a FIT (Flat Image Tree) which provides more flexibility. In
  505. particular it can handle selecting from multiple device tree
  506. and passing the correct one to U-Boot.
  507. config SPL_LOAD_FIT_ADDRESS
  508. hex "load address of fit image"
  509. depends on SPL_LOAD_FIT
  510. default 0x0
  511. help
  512. Specify the load address of the fit image that will be loaded
  513. by SPL.
  514. config SPL_LOAD_FIT_APPLY_OVERLAY
  515. bool "Enable SPL applying DT overlays from FIT"
  516. depends on SPL_LOAD_FIT
  517. select OF_LIBFDT_OVERLAY
  518. help
  519. The device tree is loaded from the FIT image. Allow the SPL is to
  520. also load device-tree overlays from the FIT image an apply them
  521. over the device tree.
  522. config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
  523. depends on SPL_LOAD_FIT_APPLY_OVERLAY
  524. default 0x10000
  525. hex "size of temporary buffer used to load the overlays"
  526. help
  527. The size of the area where the overlays will be loaded and
  528. uncompress. Must be at least as large as biggest overlay
  529. (uncompressed)
  530. config SPL_LOAD_FIT_FULL
  531. bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
  532. select SPL_FIT
  533. help
  534. Normally with the SPL framework a legacy image is generated as part
  535. of the build. This contains U-Boot along with information as to
  536. where it should be loaded. This option instead enables generation
  537. of a FIT (Flat Image Tree) which provides more flexibility. In
  538. particular it can handle selecting from multiple device tree
  539. and passing the correct one to U-Boot.
  540. config SPL_FIT_IMAGE_POST_PROCESS
  541. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  542. depends on SPL_LOAD_FIT
  543. help
  544. Allows doing any sort of manipulation to blobs after they got extracted
  545. from the U-Boot FIT image like stripping off headers or modifying the
  546. size of the blob, verification, authentication, decryption etc. in a
  547. platform or board specific way. In order to use this feature a platform
  548. or board-specific implementation of board_fit_image_post_process() must
  549. be provided. Also, anything done during this post-processing step would
  550. need to be comprehended in how the images were prepared before being
  551. injected into the FIT creation (i.e. the blobs would have been pre-
  552. processed before being added to the FIT image).
  553. config SPL_FIT_SOURCE
  554. string ".its source file for U-Boot FIT image"
  555. depends on SPL_FIT
  556. help
  557. Specifies a (platform specific) FIT source file to generate the
  558. U-Boot FIT image. This could specify further image to load and/or
  559. execute.
  560. config USE_SPL_FIT_GENERATOR
  561. bool "Use a script to generate the .its script"
  562. default y if SPL_FIT
  563. config SPL_FIT_GENERATOR
  564. string ".its file generator script for U-Boot FIT image"
  565. depends on USE_SPL_FIT_GENERATOR
  566. default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
  567. default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
  568. default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
  569. default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
  570. help
  571. Specifies a (platform specific) script file to generate the FIT
  572. source file used to build the U-Boot FIT image file. This gets
  573. passed a list of supported device tree file stub names to
  574. include in the generated image.
  575. endif # SPL
  576. endif # FIT
  577. config LEGACY_IMAGE_FORMAT
  578. bool "Enable support for the legacy image format"
  579. default y if !FIT_SIGNATURE
  580. help
  581. This option enables the legacy image format. It is enabled by
  582. default for backward compatibility, unless FIT_SIGNATURE is
  583. set where it is disabled so that unsigned images cannot be
  584. loaded. If a board needs the legacy image format support in this
  585. case, enable it here.
  586. config OF_BOARD_SETUP
  587. bool "Set up board-specific details in device tree before boot"
  588. depends on OF_LIBFDT
  589. help
  590. This causes U-Boot to call ft_board_setup() before booting into
  591. the Operating System. This function can set up various
  592. board-specific information in the device tree for use by the OS.
  593. The device tree is then passed to the OS.
  594. config OF_SYSTEM_SETUP
  595. bool "Set up system-specific details in device tree before boot"
  596. depends on OF_LIBFDT
  597. help
  598. This causes U-Boot to call ft_system_setup() before booting into
  599. the Operating System. This function can set up various
  600. system-specific information in the device tree for use by the OS.
  601. The device tree is then passed to the OS.
  602. config OF_STDOUT_VIA_ALIAS
  603. bool "Update the device-tree stdout alias from U-Boot"
  604. depends on OF_LIBFDT
  605. help
  606. This uses U-Boot's serial alias from the aliases node to update
  607. the device tree passed to the OS. The "linux,stdout-path" property
  608. in the chosen node is set to point to the correct serial node.
  609. This option currently references CONFIG_CONS_INDEX, which is
  610. incorrect when used with device tree as this option does not
  611. exist / should not be used.
  612. config SYS_EXTRA_OPTIONS
  613. string "Extra Options (DEPRECATED)"
  614. help
  615. The old configuration infrastructure (= mkconfig + boards.cfg)
  616. provided the extra options field. If you have something like
  617. "HAS_BAR,BAZ=64", the optional options
  618. #define CONFIG_HAS
  619. #define CONFIG_BAZ 64
  620. will be defined in include/config.h.
  621. This option was prepared for the smooth migration from the old
  622. configuration to Kconfig. Since this option will be removed sometime,
  623. new boards should not use this option.
  624. config HAVE_SYS_TEXT_BASE
  625. bool
  626. depends on !NIOS2 && !XTENSA
  627. depends on !EFI_APP
  628. default y
  629. config SYS_TEXT_BASE
  630. depends on HAVE_SYS_TEXT_BASE
  631. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  632. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  633. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  634. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  635. hex "Text Base"
  636. help
  637. The address in memory that U-Boot will be running from, initially.
  638. config SYS_CLK_FREQ
  639. depends on ARC || ARCH_SUNXI || MPC83xx
  640. int "CPU clock frequency"
  641. help
  642. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  643. config ARCH_FIXUP_FDT_MEMORY
  644. bool "Enable arch_fixup_memory_banks() call"
  645. default y
  646. help
  647. Enable FDT memory map syncup before OS boot. This feature can be
  648. used for booting OS with different memory setup where the part of
  649. the memory location should be used for different purpose.
  650. endmenu # Boot images
  651. source "api/Kconfig"
  652. source "common/Kconfig"
  653. source "cmd/Kconfig"
  654. source "disk/Kconfig"
  655. source "dts/Kconfig"
  656. source "env/Kconfig"
  657. source "net/Kconfig"
  658. source "drivers/Kconfig"
  659. source "fs/Kconfig"
  660. source "lib/Kconfig"
  661. source "test/Kconfig"