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