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