Kconfig 22 KB

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