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 LOCALVERSION
  18         string "Local version - append to U-Boot release"
  19         help
  20           Append an extra string to the end of your U-Boot version.
  21           This will show up in your boot log, for example.
  22           The string you set here will be appended after the contents of
  23           any files with a filename matching localversion* in your
  24           object and source tree, in that order.  Your total string can
  25           be a maximum of 64 characters.
  26
  27 config LOCALVERSION_AUTO
  28         bool "Automatically append version information to the version string"
  29         default y
  30         help
  31           This will try to automatically determine if the current tree is a
  32           release tree by looking for Git tags that belong to the current
  33           top of tree revision.
  34
  35           A string of the format -gxxxxxxxx will be added to the localversion
  36           if a Git-based tree is found.  The string generated by this will be
  37           appended after any matching localversion* files, and after the value
  38           set in CONFIG_LOCALVERSION.
  39
  40           (The actual string used here is the first eight characters produced
  41           by running the command:
  42
  43             $ git rev-parse --verify HEAD
  44
  45           which is done within the script "scripts/setlocalversion".)
  46
  47 config CC_OPTIMIZE_FOR_SIZE
  48         bool "Optimize for size"
  49         default y
  50         help
  51           Enabling this option will pass "-Os" instead of "-O2" to gcc
  52           resulting in a smaller U-Boot image.
  53
  54           This option is enabled by default for U-Boot.
  55
  56 config DISTRO_DEFAULTS
  57         bool "Select defaults suitable for booting general purpose Linux distributions"
  58         default y if ARCH_SUNXI || TEGRA
  59         default y if ARCH_LS2080A
  60         default y if ARCH_MESON
  61         default y if ARCH_ROCKCHIP
  62         default n
  63         select CMD_BOOTZ if ARM && !ARM64
  64         select CMD_BOOTI if ARM64
  65         select CMD_DHCP
  66         select CMD_PXE
  67         select CMD_EXT2
  68         select CMD_EXT4
  69         select CMD_FAT
  70         select CMD_FS_GENERIC
  71         select CMD_MII
  72         select CMD_PING
  73         select CMD_PART
  74         select HUSH_PARSER
  75         help
  76           Select this to enable various options and commands which are suitable
  77           for building u-boot for booting general purpose Linux distributions.
  78
  79 config SYS_MALLOC_F
  80         bool "Enable malloc() pool before relocation"
  81         default y if DM
  82         help
  83           Before relocation, memory is very limited on many platforms. Still,
  84           we can provide a small malloc() pool if needed. Driver model in
  85           particular needs this to operate, so that it can allocate the
  86           initial serial device and any others that are needed.
  87
  88 config SYS_MALLOC_F_LEN
  89         hex "Size of malloc() pool before relocation"
  90         depends on SYS_MALLOC_F
  91         default 0x400
  92         help
  93           Before relocation, memory is very limited on many platforms. Still,
  94           we can provide a small malloc() pool if needed. Driver model in
  95           particular needs this to operate, so that it can allocate the
  96           initial serial device and any others that are needed.
  97
  98 config SPL_SYS_MALLOC_F_LEN
  99         hex "Size of malloc() pool in SPL before relocation"
 100         depends on SYS_MALLOC_F
 101         default SYS_MALLOC_F_LEN
 102         help
 103           Before relocation, memory is very limited on many platforms. Still,
 104           we can provide a small malloc() pool if needed. Driver model in
 105           particular needs this to operate, so that it can allocate the
 106           initial serial device and any others that are needed.
 107
 108 config TPL_SYS_MALLOC_F_LEN
 109         hex "Size of malloc() pool in TPL before relocation"
 110         depends on SYS_MALLOC_F
 111         default SYS_MALLOC_F_LEN
 112         help
 113           Before relocation, memory is very limited on many platforms. Still,
 114           we can provide a small malloc() pool if needed. Driver model in
 115           particular needs this to operate, so that it can allocate the
 116           initial serial device and any others that are needed.
 117
 118 menuconfig EXPERT
 119         bool "Configure standard U-Boot features (expert users)"
 120         default y
 121         help
 122           This option allows certain base U-Boot options and settings
 123           to be disabled or tweaked. This is for specialized
 124           environments which can tolerate a "non-standard" U-Boot.
 125           Use this only if you really know what you are doing.
 126
 127 if EXPERT
 128         config SYS_MALLOC_CLEAR_ON_INIT
 129         bool "Init with zeros the memory reserved for malloc (slow)"
 130         default y
 131         help
 132           This setting is enabled by default. The reserved malloc
 133           memory is initialized with zeros, so first malloc calls
 134           will return the pointer to the zeroed memory. But this
 135           slows the boot time.
 136
 137           It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
 138           value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
 139           Then the boot time can be significantly reduced.
 140           Warning:
 141           When disabling this, please check if malloc calls, maybe
 142           should be replaced by calloc - if one expects zeroed memory.
 143
 144 config TOOLS_DEBUG
 145         bool "Enable debug information for tools"
 146         help
 147           Enable generation of debug information for tools such as mkimage.
 148           This can be used for debugging purposes. With debug information
 149           it is possible to set breakpoints on particular lines, single-step
 150           debug through the source code, etc.
 151
 152 endif # EXPERT
 153
 154 config PHYS_64BIT
 155         bool "64bit physical address support"
 156         help
 157           Say Y here to support 64bit physical memory address.
 158           This can be used not only for 64bit SoCs, but also for
 159           large physical address extention on 32bit SoCs.
 160
 161 config BUILD_ROM
 162         bool "Build U-Boot as BIOS replacement"
 163         depends on X86
 164         help
 165           This option allows to build a ROM version of U-Boot.
 166           The build process generally requires several binary blobs
 167           which are not shipped in the U-Boot source tree.
 168           Please, see doc/README.x86 for details.
 169
 170 endmenu         # General setup
 171
 172 menu "Boot images"
 173
 174 config ANDROID_BOOT_IMAGE
 175         bool "Enable support for Android Boot Images"
 176         default y if FASTBOOT
 177         help
 178           This enables support for booting images which use the Android
 179           image format header.
 180
 181 config FIT
 182         bool "Support Flattened Image Tree"
 183         select MD5
 184         select SHA1
 185         help
 186           This option allows you to boot the new uImage structure,
 187           Flattened Image Tree.  FIT is formally a FDT, which can include
 188           images of various types (kernel, FDT blob, ramdisk, etc.)
 189           in a single blob.  To boot this new uImage structure,
 190           pass the address of the blob to the "bootm" command.
 191           FIT is very flexible, supporting compression, multiple images,
 192           multiple configurations, verification through hashing and also
 193           verified boot (secure boot using RSA).
 194
 195 if FIT
 196
 197 config FIT_ENABLE_SHA256_SUPPORT
 198         bool "Support SHA256 checksum of FIT image contents"
 199         select SHA256
 200         default y
 201         help
 202           Enable this to support SHA256 checksum of FIT image contents. A
 203           SHA256 checksum is a 256-bit (32-byte) hash value used to check that
 204           the image contents have not been corrupted. SHA256 is recommended
 205           for use in secure applications since (as at 2016) there is no known
 206           feasible attack that could produce a 'collision' with differing
 207           input data. Use this for the highest security. Note that only the
 208           SHA256 variant is supported: SHA512 and others are not currently
 209           supported in U-Boot.
 210
 211 config FIT_SIGNATURE
 212         bool "Enable signature verification of FIT uImages"
 213         depends on DM
 214         select RSA
 215         help
 216           This option enables signature verification of FIT uImages,
 217           using a hash signed and verified using RSA. If
 218           CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
 219           hashing is available using hardware, then the RSA library will use
 220           it. See doc/uImage.FIT/signature.txt for more details.
 221
 222           WARNING: When relying on signed FIT images with a required signature
 223           check the legacy image format is disabled by default, so that
 224           unsigned images cannot be loaded. If a board needs the legacy image
 225           format support in this case, enable it using
 226           CONFIG_IMAGE_FORMAT_LEGACY.
 227
 228 config FIT_VERBOSE
 229         bool "Show verbose messages when FIT images fail"
 230         help
 231           Generally a system will have valid FIT images so debug messages
 232           are a waste of code space. If you are debugging your images then
 233           you can enable this option to get more verbose information about
 234           failures.
 235
 236 config FIT_BEST_MATCH
 237         bool "Select the best match for the kernel device tree"
 238         help
 239           When no configuration is explicitly selected, default to the
 240           one whose fdt's compatibility field best matches that of
 241           U-Boot itself. A match is considered "best" if it matches the
 242           most specific compatibility entry of U-Boot's fdt's root node.
 243           The order of entries in the configuration's fdt is ignored.
 244
 245 config FIT_IMAGE_POST_PROCESS
 246         bool "Enable post-processing of FIT artifacts after loading by U-Boot"
 247         depends on TI_SECURE_DEVICE
 248         help
 249           Allows doing any sort of manipulation to blobs after they got extracted
 250           from FIT images like stripping off headers or modifying the size of the
 251           blob, verification, authentication, decryption etc. in a platform or
 252           board specific way. In order to use this feature a platform or board-
 253           specific implementation of board_fit_image_post_process() must be
 254           provided. Also, anything done during this post-processing step would
 255           need to be comprehended in how the images were prepared before being
 256           injected into the FIT creation (i.e. the blobs would have been pre-
 257           processed before being added to the FIT image).
 258
 259 if SPL
 260
 261 config SPL_FIT
 262         bool "Support Flattened Image Tree within SPL"
 263         depends on SPL
 264         select SPL_OF_LIBFDT
 265
 266 config SPL_FIT_SIGNATURE
 267         bool "Enable signature verification of FIT firmware within SPL"
 268         depends on SPL_DM
 269         select SPL_FIT
 270         select SPL_RSA
 271
 272 config SPL_LOAD_FIT
 273         bool "Enable SPL loading U-Boot as a FIT"
 274         select SPL_FIT
 275         help
 276           Normally with the SPL framework a legacy image is generated as part
 277           of the build. This contains U-Boot along with information as to
 278           where it should be loaded. This option instead enables generation
 279           of a FIT (Flat Image Tree) which provides more flexibility. In
 280           particular it can handle selecting from multiple device tree
 281           and passing the correct one to U-Boot.
 282
 283 config SPL_FIT_IMAGE_POST_PROCESS
 284         bool "Enable post-processing of FIT artifacts after loading by the SPL"
 285         depends on SPL_LOAD_FIT
 286         help
 287           Allows doing any sort of manipulation to blobs after they got extracted
 288           from the U-Boot FIT image like stripping off headers or modifying the
 289           size of the blob, verification, authentication, decryption etc. in a
 290           platform or board specific way. In order to use this feature a platform
 291           or board-specific implementation of board_fit_image_post_process() must
 292           be provided. Also, anything done during this post-processing step would
 293           need to be comprehended in how the images were prepared before being
 294           injected into the FIT creation (i.e. the blobs would have been pre-
 295           processed before being added to the FIT image).
 296
 297 config SPL_FIT_SOURCE
 298         string ".its source file for U-Boot FIT image"
 299         depends on SPL_FIT
 300         help
 301           Specifies a (platform specific) FIT source file to generate the
 302           U-Boot FIT image. This could specify further image to load and/or
 303           execute.
 304
 305 config SPL_FIT_GENERATOR
 306         string ".its file generator script for U-Boot FIT image"
 307         depends on SPL_FIT
 308         default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
 309         help
 310           Specifies a (platform specific) script file to generate the FIT
 311           source file used to build the U-Boot FIT image file. This gets
 312           passed a list of supported device tree file stub names to
 313           include in the generated image.
 314
 315 endif # SPL
 316
 317 endif # FIT
 318
 319 config OF_BOARD_SETUP
 320         bool "Set up board-specific details in device tree before boot"
 321         depends on OF_LIBFDT
 322         help
 323           This causes U-Boot to call ft_board_setup() before booting into
 324           the Operating System. This function can set up various
 325           board-specific information in the device tree for use by the OS.
 326           The device tree is then passed to the OS.
 327
 328 config OF_SYSTEM_SETUP
 329         bool "Set up system-specific details in device tree before boot"
 330         depends on OF_LIBFDT
 331         help
 332           This causes U-Boot to call ft_system_setup() before booting into
 333           the Operating System. This function can set up various
 334           system-specific information in the device tree for use by the OS.
 335           The device tree is then passed to the OS.
 336
 337 config OF_STDOUT_VIA_ALIAS
 338         bool "Update the device-tree stdout alias from U-Boot"
 339         depends on OF_LIBFDT
 340         help
 341           This uses U-Boot's serial alias from the aliases node to update
 342           the device tree passed to the OS. The "linux,stdout-path" property
 343           in the chosen node is set to point to the correct serial node.
 344           This option currently references CONFIG_CONS_INDEX, which is
 345           incorrect when used with device tree as this option does not
 346           exist / should not be used.
 347
 348 config SYS_EXTRA_OPTIONS
 349         string "Extra Options (DEPRECATED)"
 350         help
 351           The old configuration infrastructure (= mkconfig + boards.cfg)
 352           provided the extra options field. If you have something like
 353           "HAS_BAR,BAZ=64", the optional options
 354             #define CONFIG_HAS
 355             #define CONFIG_BAZ  64
 356           will be defined in include/config.h.
 357           This option was prepared for the smooth migration from the old
 358           configuration to Kconfig. Since this option will be removed sometime,
 359           new boards should not use this option.
 360
 361 config SYS_TEXT_BASE
 362         depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
 363                 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
 364                 ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS
 365         depends on !EFI_APP
 366         hex "Text Base"
 367         help
 368           TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
 369
 370         default 0x80800000 if ARCH_OMAP2PLUS
 371
 372
 373 config SYS_CLK_FREQ
 374         depends on ARC || ARCH_SUNXI
 375         int "CPU clock frequency"
 376         help
 377           TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
 378
 379 config ARCH_FIXUP_FDT_MEMORY
 380         bool "Enable arch_fixup_memory_banks() call"
 381         default y
 382         help
 383           Enable FDT memory map syncup before OS boot. This feature can be
 384           used for booting OS with different memory setup where the part of
 385           the memory location should be used for different purpose.
 386
 387 endmenu         # Boot images
 388
 389 source "api/Kconfig"
 390
 391 source "common/Kconfig"
 392
 393 source "cmd/Kconfig"
 394
 395 source "disk/Kconfig"
 396
 397 source "dts/Kconfig"
 398
 399 source "env/Kconfig"
 400
 401 source "net/Kconfig"
 402
 403 source "drivers/Kconfig"
 404
 405 source "fs/Kconfig"
 406
 407 source "lib/Kconfig"
 408
 409 source "test/Kconfig"