Kconfig

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