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 DISTRO_DEFAULTS 63 bool "Select defaults suitable for booting general purpose Linux distributions" 64 default y if ARCH_SUNXI || TEGRA 65 default y if ARCH_LS2080A 66 default y if ARCH_MESON 67 default y if ARCH_ROCKCHIP 68 default n 69 select CMD_BOOTZ if ARM && !ARM64 70 select CMD_BOOTI if ARM64 71 select CMD_DHCP 72 imply CMD_PXE 73 select CMD_EXT2 74 select CMD_EXT4 75 select CMD_FAT 76 select CMD_FS_GENERIC 77 imply CMD_MII 78 select CMD_PING 79 select CMD_PART 80 select HUSH_PARSER 81 help 82 Select this to enable various options and commands which are suitable 83 for building u-boot for booting general purpose Linux distributions. 84 85config SYS_MALLOC_F 86 bool "Enable malloc() pool before relocation" 87 default y if DM 88 help 89 Before relocation, memory is very limited on many platforms. Still, 90 we can provide a small malloc() pool if needed. Driver model in 91 particular needs this to operate, so that it can allocate the 92 initial serial device and any others that are needed. 93 94config SYS_MALLOC_F_LEN 95 hex "Size of malloc() pool before relocation" 96 depends on SYS_MALLOC_F 97 default 0x400 98 help 99 Before relocation, memory is very limited on many platforms. Still, 100 we can provide a small malloc() pool if needed. Driver model in 101 particular needs this to operate, so that it can allocate the 102 initial serial device and any others that are needed. 103 104config SPL_SYS_MALLOC_F_LEN 105 hex "Size of malloc() pool in SPL before relocation" 106 depends on SYS_MALLOC_F 107 default SYS_MALLOC_F_LEN 108 help 109 Before relocation, memory is very limited on many platforms. Still, 110 we can provide a small malloc() pool if needed. Driver model in 111 particular needs this to operate, so that it can allocate the 112 initial serial device and any others that are needed. 113 114config TPL_SYS_MALLOC_F_LEN 115 hex "Size of malloc() pool in TPL before relocation" 116 depends on SYS_MALLOC_F 117 default SYS_MALLOC_F_LEN 118 help 119 Before relocation, memory is very limited on many platforms. Still, 120 we can provide a small malloc() pool if needed. Driver model in 121 particular needs this to operate, so that it can allocate the 122 initial serial device and any others that are needed. 123 124menuconfig EXPERT 125 bool "Configure standard U-Boot features (expert users)" 126 default y 127 help 128 This option allows certain base U-Boot options and settings 129 to be disabled or tweaked. This is for specialized 130 environments which can tolerate a "non-standard" U-Boot. 131 Use this only if you really know what you are doing. 132 133if EXPERT 134 config SYS_MALLOC_CLEAR_ON_INIT 135 bool "Init with zeros the memory reserved for malloc (slow)" 136 default y if !ARCH_ROCKCHIP 137 help 138 This setting is enabled by default. The reserved malloc 139 memory is initialized with zeros, so first malloc calls 140 will return the pointer to the zeroed memory. But this 141 slows the boot time. 142 143 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN 144 value, has more than few MiB, e.g. when uses bzip2 or bmp logo. 145 Then the boot time can be significantly reduced. 146 Warning: 147 When disabling this, please check if malloc calls, maybe 148 should be replaced by calloc - if one expects zeroed memory. 149 150config TOOLS_DEBUG 151 bool "Enable debug information for tools" 152 help 153 Enable generation of debug information for tools such as mkimage. 154 This can be used for debugging purposes. With debug information 155 it is possible to set breakpoints on particular lines, single-step 156 debug through the source code, etc. 157 158endif # EXPERT 159 160config PHYS_64BIT 161 bool "64bit physical address support" 162 help 163 Say Y here to support 64bit physical memory address. 164 This can be used not only for 64bit SoCs, but also for 165 large physical address extention on 32bit SoCs. 166 167endmenu # General setup 168 169menu "Boot images" 170 171config ANDROID_BOOT_IMAGE 172 bool "Enable support for Android Boot Images" 173 default y if FASTBOOT 174 help 175 This enables support for booting images which use the Android 176 image format header. 177 178config FIT 179 bool "Support Flattened Image Tree" 180 help 181 This option allows you to boot the new uImage structure, 182 Flattened Image Tree. FIT is formally a FDT, which can include 183 images of various types (kernel, FDT blob, ramdisk, etc.) 184 in a single blob. To boot this new uImage structure, 185 pass the address of the blob to the "bootm" command. 186 FIT is very flexible, supporting compression, multiple images, 187 multiple configurations, verification through hashing and also 188 verified boot (secure boot using RSA). 189 190if FIT 191 192config FIT_ENABLE_SHA256_SUPPORT 193 bool "Support SHA256 checksum of FIT image contents" 194 select SHA256 if !DM_CRYPTO 195 default y 196 help 197 Enable this to support SHA256 checksum of FIT image contents. A 198 SHA256 checksum is a 256-bit (32-byte) hash value used to check that 199 the image contents have not been corrupted. SHA256 is recommended 200 for use in secure applications since (as at 2016) there is no known 201 feasible attack that could produce a 'collision' with differing 202 input data. Use this for the highest security. Note that only the 203 SHA256 variant is supported: SHA512 and others are not currently 204 supported in U-Boot. 205 206config FIT_SIGNATURE 207 bool "Enable signature verification of FIT uImages" 208 depends on DM 209 select RSA 210 select CONSOLE_DISABLE_CLI 211 help 212 This option enables signature verification of FIT uImages, 213 using a hash signed and verified using RSA. If 214 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive 215 hashing is available using hardware, then the RSA library will use 216 it. See doc/uImage.FIT/signature.txt for more details. 217 218 WARNING: When relying on signed FIT images with a required signature 219 check the legacy image format is disabled by default, so that 220 unsigned images cannot be loaded. If a board needs the legacy image 221 format support in this case, enable it using 222 CONFIG_IMAGE_FORMAT_LEGACY. 223 224config FIT_ROLLBACK_PROTECT 225 bool "Enable rollback-index protection for FIT image" 226 depends on FIT_SIGNATURE 227 help 228 Enable rollback-index protection for FIT image 229 230config FIT_ENABLE_RSASSA_PSS_SUPPORT 231 bool "Support rsassa-pss signature scheme of FIT image contents" 232 depends on FIT_SIGNATURE 233 default y 234 help 235 Enable this to support the pss padding algorithm as described 236 in the rfc8017 (https://tools.ietf.org/html/rfc8017). 237 238config FIT_VERBOSE 239 bool "Show verbose messages when FIT images fail" 240 help 241 Generally a system will have valid FIT images so debug messages 242 are a waste of code space. If you are debugging your images then 243 you can enable this option to get more verbose information about 244 failures. 245 246config FIT_BEST_MATCH 247 bool "Select the best match for the kernel device tree" 248 help 249 When no configuration is explicitly selected, default to the 250 one whose fdt's compatibility field best matches that of 251 U-Boot itself. A match is considered "best" if it matches the 252 most specific compatibility entry of U-Boot's fdt's root node. 253 The order of entries in the configuration's fdt is ignored. 254 255config FIT_IMAGE_POST_PROCESS 256 bool "Enable post-processing of FIT artifacts after loading by U-Boot" 257 help 258 Allows doing any sort of manipulation to blobs after they got extracted 259 from FIT images like stripping off headers or modifying the size of the 260 blob, verification, authentication, decryption etc. in a platform or 261 board specific way. In order to use this feature a platform or board- 262 specific implementation of board_fit_image_post_process() must be 263 provided. Also, anything done during this post-processing step would 264 need to be comprehended in how the images were prepared before being 265 injected into the FIT creation (i.e. the blobs would have been pre- 266 processed before being added to the FIT image). 267 268config FIT_HW_CRYPTO 269 bool "Enable hardware crypto for FIT image checksum and rsa verify" 270 depends on DM_CRYPTO 271 help 272 Enable hardware crypto for FIT image checksum and rsa verify. 273 274config FIT_PRINT 275 bool "Enable fit image structure and data print" 276 default y 277 help 278 Say y here if you want to enable fit image structure and data 279 print. 280 281if SPL 282 283config SPL_FIT 284 bool "Support Flattened Image Tree within SPL" 285 depends on SPL 286 select SPL_OF_LIBFDT 287 288config SPL_FIT_SIGNATURE 289 bool "Enable signature verification of FIT firmware within SPL" 290 depends on SPL_DM 291 select SPL_FIT 292 select SPL_RSA 293 294config SPL_FIT_ROLLBACK_PROTECT 295 bool "Enable SPL rollback-index protection for FIT image" 296 depends on SPL_FIT_SIGNATURE 297 help 298 Enable SPL rollback-index protection for FIT image 299 300config SPL_LOAD_FIT 301 bool "Enable SPL loading U-Boot as a FIT" 302 select SPL_FIT 303 help 304 Normally with the SPL framework a legacy image is generated as part 305 of the build. This contains U-Boot along with information as to 306 where it should be loaded. This option instead enables generation 307 of a FIT (Flat Image Tree) which provides more flexibility. In 308 particular it can handle selecting from multiple device tree 309 and passing the correct one to U-Boot. 310 311config SPL_FIT_IMAGE_POST_PROCESS 312 bool "Enable post-processing of FIT artifacts after loading by the SPL" 313 depends on SPL_LOAD_FIT 314 help 315 Allows doing any sort of manipulation to blobs after they got extracted 316 from the U-Boot FIT image like stripping off headers or modifying the 317 size of the blob, verification, authentication, decryption etc. in a 318 platform or board specific way. In order to use this feature a platform 319 or board-specific implementation of board_fit_image_post_process() must 320 be provided. Also, anything done during this post-processing step would 321 need to be comprehended in how the images were prepared before being 322 injected into the FIT creation (i.e. the blobs would have been pre- 323 processed before being added to the FIT image). 324 325config SPL_FIT_HW_CRYPTO 326 bool "Enable SPL hardware crypto for FIT image checksum and rsa verify" 327 depends on SPL_DM_CRYPTO 328 help 329 Enable SPL hardware crypto for FIT image checksum and rsa verify. 330 331config SPL_SYS_DCACHE_OFF 332 bool "Disable SPL dcache" 333 default y 334 help 335 Disable SPL dcache. Please make sure CONFIG_SPL_SYS_MALLOC_F_LEN 336 is large enough to malloc TLB and bd_t buffer while enabling dcache. 337 338config SPL_FIT_PRINT 339 bool "Enable fit image structure and data print in SPL" 340 default n 341 help 342 Say y here if you want to enable fit image structure and data 343 print in SPL. 344 345endif # SPL 346 347config SPL_FIT_SOURCE 348 string ".its source file for U-Boot FIT image" 349 depends on SPL_FIT || FIT 350 help 351 Specifies a (platform specific) FIT source file to generate the 352 U-Boot FIT image. This could specify further image to load and/or 353 execute. 354 355config SPL_FIT_GENERATOR 356 string ".its file generator script for U-Boot FIT image" 357 depends on SPL_FIT || FIT 358 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI 359 help 360 Specifies a (platform specific) script file to generate the FIT 361 source file used to build the U-Boot FIT image file. This gets 362 passed a list of supported device tree file stub names to 363 include in the generated image. 364 365config SPL_FIT_IMAGE_KB 366 int "SPL FIT image size in KiB" 367 depends on SPL_FIT || FIT 368 default 2048 369 help 370 SPL FIT image size in KiB, default 2048KB = 1024KB(u-boot) + 1024KB(tee/atf + others). 371 372config SPL_FIT_IMAGE_MULTIPLE 373 int "SPL FIT image multiple number" 374 depends on SPL_FIT || FIT 375 default 2 376 help 377 SPL FIT image multiple number. 378 379endif # FIT 380 381config OF_BOARD_SETUP 382 bool "Set up board-specific details in device tree before boot" 383 depends on OF_LIBFDT 384 help 385 This causes U-Boot to call ft_board_setup() before booting into 386 the Operating System. This function can set up various 387 board-specific information in the device tree for use by the OS. 388 The device tree is then passed to the OS. 389 390config OF_SYSTEM_SETUP 391 bool "Set up system-specific details in device tree before boot" 392 depends on OF_LIBFDT 393 help 394 This causes U-Boot to call ft_system_setup() before booting into 395 the Operating System. This function can set up various 396 system-specific information in the device tree for use by the OS. 397 The device tree is then passed to the OS. 398 399config OF_STDOUT_VIA_ALIAS 400 bool "Update the device-tree stdout alias from U-Boot" 401 depends on OF_LIBFDT 402 help 403 This uses U-Boot's serial alias from the aliases node to update 404 the device tree passed to the OS. The "linux,stdout-path" property 405 in the chosen node is set to point to the correct serial node. 406 This option currently references CONFIG_CONS_INDEX, which is 407 incorrect when used with device tree as this option does not 408 exist / should not be used. 409 410config SYS_EXTRA_OPTIONS 411 string "Extra Options (DEPRECATED)" 412 help 413 The old configuration infrastructure (= mkconfig + boards.cfg) 414 provided the extra options field. If you have something like 415 "HAS_BAR,BAZ=64", the optional options 416 #define CONFIG_HAS 417 #define CONFIG_BAZ 64 418 will be defined in include/config.h. 419 This option was prepared for the smooth migration from the old 420 configuration to Kconfig. Since this option will be removed sometime, 421 new boards should not use this option. 422 423config SYS_TEXT_BASE 424 depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \ 425 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \ 426 ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS 427 depends on !EFI_APP 428 hex "Text Base" 429 help 430 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture 431 432 default 0x80800000 if ARCH_OMAP2PLUS 433 434 435config SYS_CLK_FREQ 436 depends on ARC || ARCH_SUNXI 437 int "CPU clock frequency" 438 help 439 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture 440 441config ARCH_FIXUP_FDT_MEMORY 442 bool "Enable arch_fixup_memory_banks() call" 443 default y 444 help 445 Enable FDT memory map syncup before OS boot. This feature can be 446 used for booting OS with different memory setup where the part of 447 the memory location should be used for different purpose. 448 449endmenu # Boot images 450 451source "api/Kconfig" 452 453source "common/Kconfig" 454 455source "cmd/Kconfig" 456 457source "disk/Kconfig" 458 459source "dts/Kconfig" 460 461source "env/Kconfig" 462 463source "net/Kconfig" 464 465source "drivers/Kconfig" 466 467source "fs/Kconfig" 468 469source "lib/Kconfig" 470 471source "test/Kconfig" 472