Kconfig 22 KB

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