Kconfig 22 KB

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