Kconfig 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784
  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 XEN
  89. bool "Select U-Boot be run as a bootloader for XEN Virtual Machine"
  90. help
  91. Enabling this option will make U-Boot be run as a bootloader
  92. for XEN [1] Virtual Machine.
  93. Xen is a virtual machine monitor (VMM) or a type-1 hypervisor with support
  94. for para-virtualization. Xen can organize the safe execution of several
  95. virtual machines on the same physical system with performance close to
  96. native. It is used as the basis for a number of different commercial and
  97. open source applications, such as: server virtualization, Infrastructure
  98. as a Service (IaaS), desktop virtualization, security applications,
  99. embedded and hardware appliances.
  100. Xen has a special VM called Domain-0 that runs the Dom0 kernel and allows
  101. Xen to use the device drivers for the Domain-0 kernel by default.
  102. [1] - https://xenproject.org/
  103. config DISTRO_DEFAULTS
  104. bool "Select defaults suitable for booting general purpose Linux distributions"
  105. select AUTO_COMPLETE
  106. select CMDLINE_EDITING
  107. select CMD_BOOTI if ARM64
  108. select CMD_BOOTZ if ARM && !ARM64
  109. select CMD_DHCP if CMD_NET
  110. select CMD_ENV_EXISTS
  111. select CMD_EXT2
  112. select CMD_EXT4
  113. select CMD_FAT
  114. select CMD_FS_GENERIC
  115. select CMD_PART if PARTITIONS
  116. select CMD_PING if CMD_NET
  117. select CMD_PXE if NET
  118. select CMD_SYSBOOT
  119. select ENV_VARS_UBOOT_CONFIG
  120. select HUSH_PARSER
  121. select SUPPORT_RAW_INITRD
  122. select SYS_LONGHELP
  123. imply CMD_MII if NET
  124. imply USB_STORAGE
  125. imply USE_BOOTCOMMAND
  126. help
  127. Select this to enable various options and commands which are suitable
  128. for building u-boot for booting general purpose Linux distributions.
  129. config ENV_VARS_UBOOT_CONFIG
  130. bool "Add arch, board, vendor and soc variables to default environment"
  131. help
  132. Define this in order to add variables describing the
  133. U-Boot build configuration to the default environment.
  134. These will be named arch, cpu, board, vendor, and soc.
  135. Enabling this option will cause the following to be defined:
  136. - CONFIG_SYS_ARCH
  137. - CONFIG_SYS_CPU
  138. - CONFIG_SYS_BOARD
  139. - CONFIG_SYS_VENDOR
  140. - CONFIG_SYS_SOC
  141. config NR_DRAM_BANKS
  142. int "Number of DRAM banks"
  143. default 1 if ARCH_SUNXI || ARCH_OWL
  144. default 4
  145. help
  146. This defines the number of DRAM banks.
  147. config SYS_BOOT_GET_CMDLINE
  148. bool "Enable kernel command line setup"
  149. help
  150. Enables allocating and saving kernel cmdline in space between
  151. "bootm_low" and "bootm_low" + BOOTMAPSZ.
  152. config SYS_BOOT_GET_KBD
  153. bool "Enable kernel board information setup"
  154. help
  155. Enables allocating and saving a kernel copy of the bd_info in
  156. space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
  157. config SYS_MALLOC_F
  158. bool "Enable malloc() pool before relocation"
  159. default y if DM
  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_F_LEN
  166. hex "Size of malloc() pool before relocation"
  167. depends on SYS_MALLOC_F
  168. default 0x1000 if AM33XX
  169. default 0x2800 if SANDBOX
  170. default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
  171. ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
  172. ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
  173. ARCH_LS1046A || ARCH_QEMU)
  174. default 0x400
  175. help
  176. Before relocation, memory is very limited on many platforms. Still,
  177. we can provide a small malloc() pool if needed. Driver model in
  178. particular needs this to operate, so that it can allocate the
  179. initial serial device and any others that are needed.
  180. config SYS_MALLOC_LEN
  181. hex "Define memory for Dynamic allocation"
  182. depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
  183. default 0x2000000 if ARCH_ROCKCHIP
  184. help
  185. This defines memory to be allocated for Dynamic allocation
  186. TODO: Use for other architectures
  187. config SPL_SYS_MALLOC_F_LEN
  188. hex "Size of malloc() pool in SPL before relocation"
  189. depends on SYS_MALLOC_F && SPL
  190. default 0x2800 if RCAR_GEN3
  191. default SYS_MALLOC_F_LEN
  192. help
  193. Before relocation, memory is very limited on many platforms. Still,
  194. we can provide a small malloc() pool if needed. Driver model in
  195. particular needs this to operate, so that it can allocate the
  196. initial serial device and any others that are needed.
  197. config TPL_SYS_MALLOC_F_LEN
  198. hex "Size of malloc() pool in TPL before relocation"
  199. depends on SYS_MALLOC_F && TPL
  200. default SYS_MALLOC_F_LEN
  201. help
  202. Before relocation, memory is very limited on many platforms. Still,
  203. we can provide a small malloc() pool if needed. Driver model in
  204. particular needs this to operate, so that it can allocate the
  205. initial serial device and any others that are needed.
  206. menuconfig EXPERT
  207. bool "Configure standard U-Boot features (expert users)"
  208. default y
  209. help
  210. This option allows certain base U-Boot options and settings
  211. to be disabled or tweaked. This is for specialized
  212. environments which can tolerate a "non-standard" U-Boot.
  213. Use this only if you really know what you are doing.
  214. if EXPERT
  215. config SYS_MALLOC_CLEAR_ON_INIT
  216. bool "Init with zeros the memory reserved for malloc (slow)"
  217. default y
  218. help
  219. This setting is enabled by default. The reserved malloc
  220. memory is initialized with zeros, so first malloc calls
  221. will return the pointer to the zeroed memory. But this
  222. slows the boot time.
  223. It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
  224. value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
  225. Then the boot time can be significantly reduced.
  226. Warning:
  227. When disabling this, please check if malloc calls, maybe
  228. should be replaced by calloc - if one expects zeroed memory.
  229. config SYS_MALLOC_DEFAULT_TO_INIT
  230. bool "Default malloc to init while reserving the memory for it"
  231. default n
  232. help
  233. It may happen that one needs to move the dynamic allocation
  234. from one to another memory range, eg. when moving the malloc
  235. from the limited static to a potentially large dynamic (DDR)
  236. memory.
  237. If so then on top of setting the updated memory aside one
  238. needs to bring the malloc init.
  239. If such a scenario is sought choose yes.
  240. config TOOLS_DEBUG
  241. bool "Enable debug information for tools"
  242. help
  243. Enable generation of debug information for tools such as mkimage.
  244. This can be used for debugging purposes. With debug information
  245. it is possible to set breakpoints on particular lines, single-step
  246. debug through the source code, etc.
  247. endif # EXPERT
  248. config PHYS_64BIT
  249. bool "64bit physical address support"
  250. help
  251. Say Y here to support 64bit physical memory address.
  252. This can be used not only for 64bit SoCs, but also for
  253. large physical address extension on 32bit SoCs.
  254. config HAS_ROM
  255. bool
  256. select BINMAN
  257. help
  258. Enables building of a u-boot.rom target. This collects U-Boot and
  259. any necessary binary blobs.
  260. config ROM_NEEDS_BLOBS
  261. bool
  262. depends on HAS_ROM
  263. help
  264. Enable this if building the u-boot.rom target needs binary blobs, and
  265. so cannot be done normally. In this case, U-Boot will only build the
  266. ROM if the required blobs exist. If not, you will see an warning like:
  267. Image 'main-section' is missing external blobs and is non-functional:
  268. intel-descriptor intel-me intel-refcode intel-vga intel-mrc
  269. config BUILD_ROM
  270. bool "Build U-Boot as BIOS replacement"
  271. depends on HAS_ROM
  272. default y if !ROM_NEEDS_BLOBS
  273. help
  274. This option allows to build a ROM version of U-Boot.
  275. The build process generally requires several binary blobs
  276. which are not shipped in the U-Boot source tree.
  277. Please, see doc/arch/x86.rst for details.
  278. config SPL_IMAGE
  279. string "SPL image used in the combined SPL+U-Boot image"
  280. default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  281. default "spl/u-boot-spl.bin"
  282. depends on SPL
  283. help
  284. Select the SPL build target that shall be generated by the SPL
  285. build process (default spl/u-boot-spl.bin). This image will be
  286. used to generate a combined image with SPL and main U-Boot
  287. proper as one single image.
  288. config BUILD_TARGET
  289. string "Build target special images"
  290. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
  291. default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
  292. default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
  293. default "u-boot-elf.srec" if RCAR_GEN3
  294. default "u-boot.itb" if !BINMAN && SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
  295. ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
  296. default "u-boot.kwb" if ARCH_KIRKWOOD
  297. default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
  298. default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
  299. help
  300. Some SoCs need special image types (e.g. U-Boot binary
  301. with a special header) as build targets. By defining
  302. CONFIG_BUILD_TARGET in the SoC / board header, this
  303. special image will be automatically built upon calling
  304. make / buildman.
  305. config SYS_CUSTOM_LDSCRIPT
  306. bool "Use a custom location for the U-Boot linker script"
  307. help
  308. Normally when linking U-Boot we will look in the board directory,
  309. the CPU directory and finally the "cpu" directory of the architecture
  310. for the ile "u-boot.lds" and use that as our linker. However, in
  311. some cases we need to provide a different linker script. To do so,
  312. enable this option and then provide the location under
  313. CONFIG_SYS_LDSCRIPT.
  314. config SYS_LDSCRIPT
  315. depends on SYS_CUSTOM_LDSCRIPT
  316. string "Custom ldscript location"
  317. help
  318. Path within the source tree to the linker script to use for the
  319. main U-Boot binary.
  320. config ERR_PTR_OFFSET
  321. hex
  322. default 0x0
  323. help
  324. Some U-Boot pointers have redundant information, so we can use a
  325. scheme where we can return either an error code or a pointer with the
  326. same return value. The default implementation just casts the pointer
  327. to a number, however, this may fail on platforms where the end of the
  328. address range is used for valid pointers (e.g. 0xffffff00 is a valid
  329. heap pointer in socfpga SPL).
  330. For such platforms, this value provides an upper range of those error
  331. pointer values - up to 'MAX_ERRNO' bytes below this value must be
  332. unused/invalid addresses.
  333. config PLATFORM_ELFENTRY
  334. string
  335. default "__start" if MIPS
  336. default "_start"
  337. config STACK_SIZE
  338. hex "Define max stack size that can be used by U-Boot"
  339. default 0x4000000 if ARCH_VERSAL || ARCH_ZYNQMP
  340. default 0x200000 if MICROBLAZE
  341. default 0x1000000
  342. help
  343. Define Max stack size that can be used by U-Boot. This value is used
  344. by the UEFI sub-system. On some boards initrd_high is calculated as
  345. base stack pointer minus this stack size.
  346. config SYS_HAS_SRAM
  347. bool
  348. default y if TARGET_PIC32MZDASK
  349. default y if TARGET_DEVKIT8000
  350. default y if TARGET_TRICORDER
  351. default n
  352. help
  353. Enable this to allow support for the on board SRAM.
  354. SRAM base address is controlled by CONFIG_SYS_SRAM_BASE.
  355. SRAM size is controlled by CONFIG_SYS_SRAM_SIZE.
  356. config SYS_SRAM_BASE
  357. hex
  358. default 0x80000000 if TARGET_PIC32MZDASK
  359. default 0x40200000 if TARGET_DEVKIT8000
  360. default 0x40200000 if TARGET_TRICORDER
  361. default 0x0
  362. config SYS_SRAM_SIZE
  363. hex
  364. default 0x00080000 if TARGET_PIC32MZDASK
  365. default 0x10000 if TARGET_DEVKIT8000
  366. default 0x10000 if TARGET_TRICORDER
  367. default 0x0
  368. endmenu # General setup
  369. menu "Boot images"
  370. config ANDROID_BOOT_IMAGE
  371. bool "Enable support for Android Boot Images"
  372. default y if FASTBOOT
  373. help
  374. This enables support for booting images which use the Android
  375. image format header.
  376. config FIT
  377. bool "Support Flattened Image Tree"
  378. select MD5
  379. select SHA1
  380. help
  381. This option allows you to boot the new uImage structure,
  382. Flattened Image Tree. FIT is formally a FDT, which can include
  383. images of various types (kernel, FDT blob, ramdisk, etc.)
  384. in a single blob. To boot this new uImage structure,
  385. pass the address of the blob to the "bootm" command.
  386. FIT is very flexible, supporting compression, multiple images,
  387. multiple configurations, verification through hashing and also
  388. verified boot (secure boot using RSA).
  389. if FIT
  390. config FIT_EXTERNAL_OFFSET
  391. hex "FIT external data offset"
  392. default 0x0
  393. help
  394. This specifies a data offset in fit image.
  395. The offset is from data payload offset to the beginning of
  396. fit image header. When specifies a offset, specific data
  397. could be put in the hole between data payload and fit image
  398. header, such as CSF data on i.MX platform.
  399. config FIT_ENABLE_SHA256_SUPPORT
  400. bool "Support SHA256 checksum of FIT image contents"
  401. default y
  402. select SHA256
  403. help
  404. Enable this to support SHA256 checksum of FIT image contents. A
  405. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  406. the image contents have not been corrupted.
  407. config FIT_ENABLE_SHA384_SUPPORT
  408. bool "Support SHA384 checksum of FIT image contents"
  409. default n
  410. select SHA384
  411. help
  412. Enable this to support SHA384 checksum of FIT image contents. A
  413. SHA384 checksum is a 384-bit (48-byte) hash value used to check that
  414. the image contents have not been corrupted. Use this for the highest
  415. security.
  416. config FIT_ENABLE_SHA512_SUPPORT
  417. bool "Support SHA512 checksum of FIT image contents"
  418. default n
  419. select SHA512
  420. help
  421. Enable this to support SHA512 checksum of FIT image contents. A
  422. SHA512 checksum is a 512-bit (64-byte) hash value used to check that
  423. the image contents have not been corrupted.
  424. config FIT_SIGNATURE
  425. bool "Enable signature verification of FIT uImages"
  426. depends on DM
  427. select HASH
  428. select RSA
  429. select RSA_VERIFY
  430. select IMAGE_SIGN_INFO
  431. help
  432. This option enables signature verification of FIT uImages,
  433. using a hash signed and verified using RSA. If
  434. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  435. hashing is available using hardware, then the RSA library will use
  436. it. See doc/uImage.FIT/signature.txt for more details.
  437. WARNING: When relying on signed FIT images with a required signature
  438. check the legacy image format is disabled by default, so that
  439. unsigned images cannot be loaded. If a board needs the legacy image
  440. format support in this case, enable it using
  441. CONFIG_LEGACY_IMAGE_FORMAT.
  442. config FIT_SIGNATURE_MAX_SIZE
  443. hex "Max size of signed FIT structures"
  444. depends on FIT_SIGNATURE
  445. default 0x10000000
  446. help
  447. This option sets a max size in bytes for verified FIT uImages.
  448. A sane value of 256MB protects corrupted DTB structures from overlapping
  449. device memory. Assure this size does not extend past expected storage
  450. space.
  451. config FIT_ENABLE_RSASSA_PSS_SUPPORT
  452. bool "Support rsassa-pss signature scheme of FIT image contents"
  453. depends on FIT_SIGNATURE
  454. default n
  455. help
  456. Enable this to support the pss padding algorithm as described
  457. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  458. config FIT_CIPHER
  459. bool "Enable ciphering data in a FIT uImages"
  460. depends on DM
  461. select AES
  462. help
  463. Enable the feature of data ciphering/unciphering in the tool mkimage
  464. and in the u-boot support of the FIT image.
  465. config FIT_VERBOSE
  466. bool "Show verbose messages when FIT images fail"
  467. help
  468. Generally a system will have valid FIT images so debug messages
  469. are a waste of code space. If you are debugging your images then
  470. you can enable this option to get more verbose information about
  471. failures.
  472. config FIT_BEST_MATCH
  473. bool "Select the best match for the kernel device tree"
  474. help
  475. When no configuration is explicitly selected, default to the
  476. one whose fdt's compatibility field best matches that of
  477. U-Boot itself. A match is considered "best" if it matches the
  478. most specific compatibility entry of U-Boot's fdt's root node.
  479. The order of entries in the configuration's fdt is ignored.
  480. config FIT_IMAGE_POST_PROCESS
  481. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  482. depends on TI_SECURE_DEVICE
  483. help
  484. Allows doing any sort of manipulation to blobs after they got extracted
  485. from FIT images like stripping off headers or modifying the size of the
  486. blob, verification, authentication, decryption etc. in a platform or
  487. board specific way. In order to use this feature a platform or board-
  488. specific implementation of board_fit_image_post_process() must be
  489. provided. Also, anything done during this post-processing step would
  490. need to be comprehended in how the images were prepared before being
  491. injected into the FIT creation (i.e. the blobs would have been pre-
  492. processed before being added to the FIT image).
  493. if SPL
  494. config SPL_FIT
  495. bool "Support Flattened Image Tree within SPL"
  496. depends on SPL
  497. select SPL_OF_LIBFDT
  498. config SPL_FIT_PRINT
  499. bool "Support FIT printing within SPL"
  500. depends on SPL_FIT
  501. help
  502. Support printing the content of the fitImage in a verbose manner in SPL.
  503. config SPL_FIT_SIGNATURE
  504. bool "Enable signature verification of FIT firmware within SPL"
  505. depends on SPL_DM
  506. select SPL_FIT
  507. select SPL_CRYPTO_SUPPORT
  508. select SPL_HASH_SUPPORT
  509. select SPL_RSA
  510. select SPL_RSA_VERIFY
  511. select SPL_IMAGE_SIGN_INFO
  512. config SPL_LOAD_FIT
  513. bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
  514. select SPL_FIT
  515. help
  516. Normally with the SPL framework a legacy image is generated as part
  517. of the build. This contains U-Boot along with information as to
  518. where it should be loaded. This option instead enables generation
  519. of a FIT (Flat Image Tree) which provides more flexibility. In
  520. particular it can handle selecting from multiple device tree
  521. and passing the correct one to U-Boot.
  522. config SPL_LOAD_FIT_ADDRESS
  523. hex "load address of fit image"
  524. depends on SPL_LOAD_FIT
  525. default 0x0
  526. help
  527. Specify the load address of the fit image that will be loaded
  528. by SPL.
  529. config SPL_LOAD_FIT_APPLY_OVERLAY
  530. bool "Enable SPL applying DT overlays from FIT"
  531. depends on SPL_LOAD_FIT
  532. select OF_LIBFDT_OVERLAY
  533. help
  534. The device tree is loaded from the FIT image. Allow the SPL is to
  535. also load device-tree overlays from the FIT image an apply them
  536. over the device tree.
  537. config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
  538. depends on SPL_LOAD_FIT_APPLY_OVERLAY
  539. default 0x10000
  540. hex "size of temporary buffer used to load the overlays"
  541. help
  542. The size of the area where the overlays will be loaded and
  543. uncompress. Must be at least as large as biggest overlay
  544. (uncompressed)
  545. config SPL_LOAD_FIT_FULL
  546. bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
  547. select SPL_FIT
  548. help
  549. Normally with the SPL framework a legacy image is generated as part
  550. of the build. This contains U-Boot along with information as to
  551. where it should be loaded. This option instead enables generation
  552. of a FIT (Flat Image Tree) which provides more flexibility. In
  553. particular it can handle selecting from multiple device tree
  554. and passing the correct one to U-Boot.
  555. config SPL_FIT_IMAGE_POST_PROCESS
  556. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  557. depends on SPL_LOAD_FIT
  558. help
  559. Allows doing any sort of manipulation to blobs after they got extracted
  560. from the U-Boot FIT image like stripping off headers or modifying the
  561. size of the blob, verification, authentication, decryption etc. in a
  562. platform or board specific way. In order to use this feature a platform
  563. or board-specific implementation of board_fit_image_post_process() must
  564. be provided. Also, anything done during this post-processing step would
  565. need to be comprehended in how the images were prepared before being
  566. injected into the FIT creation (i.e. the blobs would have been pre-
  567. processed before being added to the FIT image).
  568. config SPL_FIT_SOURCE
  569. string ".its source file for U-Boot FIT image"
  570. depends on SPL_FIT
  571. help
  572. Specifies a (platform specific) FIT source file to generate the
  573. U-Boot FIT image. This could specify further image to load and/or
  574. execute.
  575. config USE_SPL_FIT_GENERATOR
  576. bool "Use a script to generate the .its script"
  577. default y if SPL_FIT && !ARCH_SUNXI
  578. config SPL_FIT_GENERATOR
  579. string ".its file generator script for U-Boot FIT image"
  580. depends on USE_SPL_FIT_GENERATOR
  581. default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
  582. default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
  583. default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
  584. help
  585. Specifies a (platform specific) script file to generate the FIT
  586. source file used to build the U-Boot FIT image file. This gets
  587. passed a list of supported device tree file stub names to
  588. include in the generated image.
  589. endif # SPL
  590. endif # FIT
  591. config LEGACY_IMAGE_FORMAT
  592. bool "Enable support for the legacy image format"
  593. default y if !FIT_SIGNATURE
  594. help
  595. This option enables the legacy image format. It is enabled by
  596. default for backward compatibility, unless FIT_SIGNATURE is
  597. set where it is disabled so that unsigned images cannot be
  598. loaded. If a board needs the legacy image format support in this
  599. case, enable it here.
  600. config OF_BOARD_SETUP
  601. bool "Set up board-specific details in device tree before boot"
  602. depends on OF_LIBFDT
  603. help
  604. This causes U-Boot to call ft_board_setup() before booting into
  605. the Operating System. This function can set up various
  606. board-specific information in the device tree for use by the OS.
  607. The device tree is then passed to the OS.
  608. config OF_SYSTEM_SETUP
  609. bool "Set up system-specific details in device tree before boot"
  610. depends on OF_LIBFDT
  611. help
  612. This causes U-Boot to call ft_system_setup() before booting into
  613. the Operating System. This function can set up various
  614. system-specific information in the device tree for use by the OS.
  615. The device tree is then passed to the OS.
  616. config OF_STDOUT_VIA_ALIAS
  617. bool "Update the device-tree stdout alias from U-Boot"
  618. depends on OF_LIBFDT
  619. help
  620. This uses U-Boot's serial alias from the aliases node to update
  621. the device tree passed to the OS. The "linux,stdout-path" property
  622. in the chosen node is set to point to the correct serial node.
  623. This option currently references CONFIG_CONS_INDEX, which is
  624. incorrect when used with device tree as this option does not
  625. exist / should not be used.
  626. config SYS_EXTRA_OPTIONS
  627. string "Extra Options (DEPRECATED)"
  628. help
  629. The old configuration infrastructure (= mkconfig + boards.cfg)
  630. provided the extra options field. If you have something like
  631. "HAS_BAR,BAZ=64", the optional options
  632. #define CONFIG_HAS
  633. #define CONFIG_BAZ 64
  634. will be defined in include/config.h.
  635. This option was prepared for the smooth migration from the old
  636. configuration to Kconfig. Since this option will be removed sometime,
  637. new boards should not use this option.
  638. config HAVE_SYS_TEXT_BASE
  639. bool
  640. depends on !NIOS2 && !XTENSA
  641. depends on !EFI_APP
  642. default y
  643. config SYS_TEXT_BASE
  644. depends on HAVE_SYS_TEXT_BASE
  645. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  646. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  647. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  648. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  649. hex "Text Base"
  650. help
  651. The address in memory that U-Boot will be running from, initially.
  652. config SYS_CLK_FREQ
  653. depends on ARC || ARCH_SUNXI || MPC83xx
  654. int "CPU clock frequency"
  655. help
  656. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  657. config ARCH_FIXUP_FDT_MEMORY
  658. bool "Enable arch_fixup_memory_banks() call"
  659. default y
  660. help
  661. Enable FDT memory map syncup before OS boot. This feature can be
  662. used for booting OS with different memory setup where the part of
  663. the memory location should be used for different purpose.
  664. endmenu # Boot images
  665. source "api/Kconfig"
  666. source "common/Kconfig"
  667. source "cmd/Kconfig"
  668. source "disk/Kconfig"
  669. source "dts/Kconfig"
  670. source "env/Kconfig"
  671. source "net/Kconfig"
  672. source "drivers/Kconfig"
  673. source "fs/Kconfig"
  674. source "lib/Kconfig"
  675. source "test/Kconfig"