Kconfig 23 KB

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