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.
6 mainmenu "U-Boot $(UBOOTVERSION) Configuration"
8 comment "Compiler: $(CC_VERSION_TEXT)"
10 source "scripts/Kconfig.include"
12 # Allow defaults in arch-specific code to override any given here
20 This option cannot be enabled. It is used as dependency
21 for broken and incomplete features.
26 This option cannot be enabled. It it used as a dependency for
27 code that relies on deprecated features that will be removed and
28 the conversion deadline has passed.
31 string "Local version - append to U-Boot release"
33 Append an extra string to the end of your U-Boot version.
34 This will show up in your boot log, for example.
35 The string you set here will be appended after the contents of
36 any files with a filename matching localversion* in your
37 object and source tree, in that order. Your total string can
38 be a maximum of 64 characters.
40 config LOCALVERSION_AUTO
41 bool "Automatically append version information to the version string"
44 This will try to automatically determine if the current tree is a
45 release tree by looking for Git tags that belong to the current
48 A string of the format -gxxxxxxxx will be added to the localversion
49 if a Git-based tree is found. The string generated by this will be
50 appended after any matching localversion* files, and after the value
51 set in CONFIG_LOCALVERSION.
53 (The actual string used here is the first eight characters produced
54 by running the command:
56 $ git rev-parse --verify HEAD
58 which is done within the script "scripts/setlocalversion".)
60 config CC_OPTIMIZE_FOR_SIZE
61 bool "Optimize for size"
64 Enabling this option will pass "-Os" instead of "-O2" to gcc
65 resulting in a smaller U-Boot image.
67 This option is enabled by default for U-Boot.
69 config OPTIMIZE_INLINING
70 bool "Allow compiler to uninline functions marked 'inline' in full U-Boot"
73 This option determines if U-Boot forces gcc to inline the functions
74 developers have marked 'inline'. Doing so takes away freedom from gcc to
75 do what it thinks is best, which is desirable in some cases for size
78 config SPL_OPTIMIZE_INLINING
79 bool "Allow compiler to uninline functions marked 'inline' in SPL"
83 This option determines if U-Boot forces gcc to inline the functions
84 developers have marked 'inline'. Doing so takes away freedom from gcc to
85 do what it thinks is best, which is desirable in some cases for size
88 config TPL_OPTIMIZE_INLINING
89 bool "Allow compiler to uninline functions marked 'inline' in TPL"
93 This option determines if U-Boot forces gcc to inline the functions
94 developers have marked 'inline'. Doing so takes away freedom from gcc to
95 do what it thinks is best, which is desirable in some cases for size
99 bool "Enable code coverage analysis"
102 Enabling this option will pass "--coverage" to gcc to compile
103 and link code instrumented for coverage analysis.
105 config CC_HAS_ASM_INLINE
106 def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null)
108 config DISTRO_DEFAULTS
109 bool "Select defaults suitable for booting general purpose Linux distributions"
111 select CMDLINE_EDITING
112 select CMD_BOOTI if ARM64
113 select CMD_BOOTZ if ARM && !ARM64
114 select CMD_DHCP if CMD_NET
115 select CMD_ENV_EXISTS
119 select CMD_FS_GENERIC
120 select CMD_PART if PARTITIONS
121 select CMD_PING if CMD_NET
122 select CMD_PXE if NET
124 select ENV_VARS_UBOOT_CONFIG
126 select SUPPORT_RAW_INITRD
130 imply USE_BOOTCOMMAND
132 Select this to enable various options and commands which are suitable
133 for building u-boot for booting general purpose Linux distributions.
135 config ENV_VARS_UBOOT_CONFIG
136 bool "Add arch, board, vendor and soc variables to default environment"
138 Define this in order to add variables describing the
139 U-Boot build configuration to the default environment.
140 These will be named arch, cpu, board, vendor, and soc.
141 Enabling this option will cause the following to be defined:
149 int "Number of DRAM banks"
150 default 1 if ARCH_SUNXI || ARCH_OWL
153 This defines the number of DRAM banks.
155 config SYS_BOOT_GET_CMDLINE
156 bool "Enable kernel command line setup"
158 Enables allocating and saving kernel cmdline in space between
159 "bootm_low" and "bootm_low" + BOOTMAPSZ.
161 config SYS_BOOT_GET_KBD
162 bool "Enable kernel board information setup"
164 Enables allocating and saving a kernel copy of the bd_info in
165 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
168 bool "Enable malloc() pool before relocation"
172 Before relocation, memory is very limited on many platforms. Still,
173 we can provide a small malloc() pool if needed. Driver model in
174 particular needs this to operate, so that it can allocate the
175 initial serial device and any others that are needed.
177 config SYS_MALLOC_F_LEN
178 hex "Size of malloc() pool before relocation"
179 depends on SYS_MALLOC_F
180 default 0x1000 if AM33XX
181 default 0x2800 if SANDBOX
182 default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
183 ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
184 ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
185 ARCH_LS1046A || ARCH_QEMU)
188 Before relocation, memory is very limited on many platforms. Still,
189 we can provide a small malloc() pool if needed. Driver model in
190 particular needs this to operate, so that it can allocate the
191 initial serial device and any others that are needed.
193 config SYS_MALLOC_LEN
194 hex "Define memory for Dynamic allocation"
195 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
196 default 0x2000000 if ARCH_ROCKCHIP
198 This defines memory to be allocated for Dynamic allocation
199 TODO: Use for other architectures
201 config SPL_SYS_MALLOC_F_LEN
202 hex "Size of malloc() pool in SPL before relocation"
203 depends on SYS_MALLOC_F && SPL
204 default 0x2800 if RCAR_GEN3
205 default SYS_MALLOC_F_LEN
207 Before relocation, memory is very limited on many platforms. Still,
208 we can provide a small malloc() pool if needed. Driver model in
209 particular needs this to operate, so that it can allocate the
210 initial serial device and any others that are needed.
212 config TPL_SYS_MALLOC_F_LEN
213 hex "Size of malloc() pool in TPL before relocation"
214 depends on SYS_MALLOC_F && TPL
215 default SYS_MALLOC_F_LEN
217 Before relocation, memory is very limited on many platforms. Still,
218 we can provide a small malloc() pool if needed. Driver model in
219 particular needs this to operate, so that it can allocate the
220 initial serial device and any others that are needed.
223 bool "Configure standard U-Boot features (expert users)"
226 This option allows certain base U-Boot options and settings
227 to be disabled or tweaked. This is for specialized
228 environments which can tolerate a "non-standard" U-Boot.
229 Use this only if you really know what you are doing.
232 config SYS_MALLOC_CLEAR_ON_INIT
233 bool "Init with zeros the memory reserved for malloc (slow)"
236 This setting is enabled by default. The reserved malloc
237 memory is initialized with zeros, so first malloc calls
238 will return the pointer to the zeroed memory. But this
241 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
242 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
243 Then the boot time can be significantly reduced.
245 When disabling this, please check if malloc calls, maybe
246 should be replaced by calloc - if one expects zeroed memory.
248 config SYS_MALLOC_DEFAULT_TO_INIT
249 bool "Default malloc to init while reserving the memory for it"
252 It may happen that one needs to move the dynamic allocation
253 from one to another memory range, eg. when moving the malloc
254 from the limited static to a potentially large dynamic (DDR)
257 If so then on top of setting the updated memory aside one
258 needs to bring the malloc init.
260 If such a scenario is sought choose yes.
263 bool "Enable debug information for tools"
265 Enable generation of debug information for tools such as mkimage.
266 This can be used for debugging purposes. With debug information
267 it is possible to set breakpoints on particular lines, single-step
268 debug through the source code, etc.
273 bool "64bit physical address support"
275 Say Y here to support 64bit physical memory address.
276 This can be used not only for 64bit SoCs, but also for
277 large physical address extension on 32bit SoCs.
283 Enables building of a u-boot.rom target. This collects U-Boot and
284 any necessary binary blobs.
286 config ROM_NEEDS_BLOBS
290 Enable this if building the u-boot.rom target needs binary blobs, and
291 so cannot be done normally. In this case, U-Boot will only build the
292 ROM if the required blobs exist. If not, you will see an warning like:
294 Image 'main-section' is missing external blobs and is non-functional:
295 intel-descriptor intel-me intel-refcode intel-vga intel-mrc
298 bool "Build U-Boot as BIOS replacement"
300 default y if !ROM_NEEDS_BLOBS
302 This option allows to build a ROM version of U-Boot.
303 The build process generally requires several binary blobs
304 which are not shipped in the U-Boot source tree.
305 Please, see doc/arch/x86.rst for details.
308 string "SPL image used in the combined SPL+U-Boot image"
309 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
310 default "spl/u-boot-spl.bin"
313 Select the SPL build target that shall be generated by the SPL
314 build process (default spl/u-boot-spl.bin). This image will be
315 used to generate a combined image with SPL and main U-Boot
316 proper as one single image.
319 string "Build target special images"
320 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
321 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
322 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
323 default "u-boot-elf.srec" if RCAR_GEN3
324 default "u-boot.itb" if !BINMAN && SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
325 ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
326 default "u-boot.kwb" if ARCH_KIRKWOOD
327 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
328 default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
330 Some SoCs need special image types (e.g. U-Boot binary
331 with a special header) as build targets. By defining
332 CONFIG_BUILD_TARGET in the SoC / board header, this
333 special image will be automatically built upon calling
336 config SYS_CUSTOM_LDSCRIPT
337 bool "Use a custom location for the U-Boot linker script"
339 Normally when linking U-Boot we will look in the board directory,
340 the CPU directory and finally the "cpu" directory of the architecture
341 for the ile "u-boot.lds" and use that as our linker. However, in
342 some cases we need to provide a different linker script. To do so,
343 enable this option and then provide the location under
347 depends on SYS_CUSTOM_LDSCRIPT
348 string "Custom ldscript location"
350 Path within the source tree to the linker script to use for the
353 config ERR_PTR_OFFSET
357 Some U-Boot pointers have redundant information, so we can use a
358 scheme where we can return either an error code or a pointer with the
359 same return value. The default implementation just casts the pointer
360 to a number, however, this may fail on platforms where the end of the
361 address range is used for valid pointers (e.g. 0xffffff00 is a valid
362 heap pointer in socfpga SPL).
363 For such platforms, this value provides an upper range of those error
364 pointer values - up to 'MAX_ERRNO' bytes below this value must be
365 unused/invalid addresses.
367 config PLATFORM_ELFENTRY
369 default "__start" if MIPS
373 hex "Define max stack size that can be used by U-Boot"
374 default 0x4000000 if ARCH_VERSAL || ARCH_ZYNQMP
375 default 0x200000 if MICROBLAZE
378 Define Max stack size that can be used by U-Boot. This value is used
379 by the UEFI sub-system. On some boards initrd_high is calculated as
380 base stack pointer minus this stack size.
384 default y if TARGET_PIC32MZDASK
385 default y if TARGET_DEVKIT8000
386 default y if TARGET_TRICORDER
389 Enable this to allow support for the on board SRAM.
390 SRAM base address is controlled by CONFIG_SYS_SRAM_BASE.
391 SRAM size is controlled by CONFIG_SYS_SRAM_SIZE.
395 default 0x80000000 if TARGET_PIC32MZDASK
396 default 0x40200000 if TARGET_DEVKIT8000
397 default 0x40200000 if TARGET_TRICORDER
402 default 0x00080000 if TARGET_PIC32MZDASK
403 default 0x10000 if TARGET_DEVKIT8000
404 default 0x10000 if TARGET_TRICORDER
407 endmenu # General setup
411 config ANDROID_BOOT_IMAGE
412 bool "Enable support for Android Boot Images"
413 default y if FASTBOOT
415 This enables support for booting images which use the Android
419 bool "Support Flattened Image Tree"
423 This option allows you to boot the new uImage structure,
424 Flattened Image Tree. FIT is formally a FDT, which can include
425 images of various types (kernel, FDT blob, ramdisk, etc.)
426 in a single blob. To boot this new uImage structure,
427 pass the address of the blob to the "bootm" command.
428 FIT is very flexible, supporting compression, multiple images,
429 multiple configurations, verification through hashing and also
430 verified boot (secure boot using RSA).
434 config FIT_EXTERNAL_OFFSET
435 hex "FIT external data offset"
438 This specifies a data offset in fit image.
439 The offset is from data payload offset to the beginning of
440 fit image header. When specifies a offset, specific data
441 could be put in the hole between data payload and fit image
442 header, such as CSF data on i.MX platform.
444 config FIT_ENABLE_SHA256_SUPPORT
445 bool "Support SHA256 checksum of FIT image contents"
449 Enable this to support SHA256 checksum of FIT image contents. A
450 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
451 the image contents have not been corrupted.
453 config FIT_ENABLE_SHA384_SUPPORT
454 bool "Support SHA384 checksum of FIT image contents"
458 Enable this to support SHA384 checksum of FIT image contents. A
459 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
460 the image contents have not been corrupted. Use this for the highest
463 config FIT_ENABLE_SHA512_SUPPORT
464 bool "Support SHA512 checksum of FIT image contents"
468 Enable this to support SHA512 checksum of FIT image contents. A
469 SHA512 checksum is a 512-bit (64-byte) hash value used to check that
470 the image contents have not been corrupted.
473 bool "Enable signature verification of FIT uImages"
478 select IMAGE_SIGN_INFO
480 This option enables signature verification of FIT uImages,
481 using a hash signed and verified using RSA. If
482 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
483 hashing is available using hardware, then the RSA library will use
484 it. See doc/uImage.FIT/signature.txt for more details.
486 WARNING: When relying on signed FIT images with a required signature
487 check the legacy image format is disabled by default, so that
488 unsigned images cannot be loaded. If a board needs the legacy image
489 format support in this case, enable it using
490 CONFIG_LEGACY_IMAGE_FORMAT.
492 config FIT_SIGNATURE_MAX_SIZE
493 hex "Max size of signed FIT structures"
494 depends on FIT_SIGNATURE
497 This option sets a max size in bytes for verified FIT uImages.
498 A sane value of 256MB protects corrupted DTB structures from overlapping
499 device memory. Assure this size does not extend past expected storage
502 config FIT_ENABLE_RSASSA_PSS_SUPPORT
503 bool "Support rsassa-pss signature scheme of FIT image contents"
504 depends on FIT_SIGNATURE
507 Enable this to support the pss padding algorithm as described
508 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
511 bool "Enable ciphering data in a FIT uImages"
515 Enable the feature of data ciphering/unciphering in the tool mkimage
516 and in the u-boot support of the FIT image.
519 bool "Show verbose messages when FIT images fail"
521 Generally a system will have valid FIT images so debug messages
522 are a waste of code space. If you are debugging your images then
523 you can enable this option to get more verbose information about
526 config FIT_BEST_MATCH
527 bool "Select the best match for the kernel device tree"
529 When no configuration is explicitly selected, default to the
530 one whose fdt's compatibility field best matches that of
531 U-Boot itself. A match is considered "best" if it matches the
532 most specific compatibility entry of U-Boot's fdt's root node.
533 The order of entries in the configuration's fdt is ignored.
535 config FIT_IMAGE_POST_PROCESS
536 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
537 depends on TI_SECURE_DEVICE
539 Allows doing any sort of manipulation to blobs after they got extracted
540 from FIT images like stripping off headers or modifying the size of the
541 blob, verification, authentication, decryption etc. in a platform or
542 board specific way. In order to use this feature a platform or board-
543 specific implementation of board_fit_image_post_process() must be
544 provided. Also, anything done during this post-processing step would
545 need to be comprehended in how the images were prepared before being
546 injected into the FIT creation (i.e. the blobs would have been pre-
547 processed before being added to the FIT image).
552 bool "Support Flattened Image Tree within SPL"
557 bool "Support FIT printing within SPL"
560 Support printing the content of the fitImage in a verbose manner in SPL.
562 config SPL_FIT_SIGNATURE
563 bool "Enable signature verification of FIT firmware within SPL"
566 select SPL_CRYPTO_SUPPORT
567 select SPL_HASH_SUPPORT
569 select SPL_RSA_VERIFY
570 select SPL_IMAGE_SIGN_INFO
573 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
576 Normally with the SPL framework a legacy image is generated as part
577 of the build. This contains U-Boot along with information as to
578 where it should be loaded. This option instead enables generation
579 of a FIT (Flat Image Tree) which provides more flexibility. In
580 particular it can handle selecting from multiple device tree
581 and passing the correct one to U-Boot.
583 config SPL_LOAD_FIT_ADDRESS
584 hex "load address of fit image"
585 depends on SPL_LOAD_FIT
588 Specify the load address of the fit image that will be loaded
591 config SPL_LOAD_FIT_APPLY_OVERLAY
592 bool "Enable SPL applying DT overlays from FIT"
593 depends on SPL_LOAD_FIT
594 select OF_LIBFDT_OVERLAY
596 The device tree is loaded from the FIT image. Allow the SPL is to
597 also load device-tree overlays from the FIT image an apply them
598 over the device tree.
600 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
601 depends on SPL_LOAD_FIT_APPLY_OVERLAY
603 hex "size of temporary buffer used to load the overlays"
605 The size of the area where the overlays will be loaded and
606 uncompress. Must be at least as large as biggest overlay
609 config SPL_LOAD_FIT_FULL
610 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
613 Normally with the SPL framework a legacy image is generated as part
614 of the build. This contains U-Boot along with information as to
615 where it should be loaded. This option instead enables generation
616 of a FIT (Flat Image Tree) which provides more flexibility. In
617 particular it can handle selecting from multiple device tree
618 and passing the correct one to U-Boot.
620 config SPL_FIT_IMAGE_POST_PROCESS
621 bool "Enable post-processing of FIT artifacts after loading by the SPL"
622 depends on SPL_LOAD_FIT
624 Allows doing any sort of manipulation to blobs after they got extracted
625 from the U-Boot FIT image like stripping off headers or modifying the
626 size of the blob, verification, authentication, decryption etc. in a
627 platform or board specific way. In order to use this feature a platform
628 or board-specific implementation of board_fit_image_post_process() must
629 be provided. Also, anything done during this post-processing step would
630 need to be comprehended in how the images were prepared before being
631 injected into the FIT creation (i.e. the blobs would have been pre-
632 processed before being added to the FIT image).
634 config SPL_FIT_SOURCE
635 string ".its source file for U-Boot FIT image"
638 Specifies a (platform specific) FIT source file to generate the
639 U-Boot FIT image. This could specify further image to load and/or
642 config USE_SPL_FIT_GENERATOR
643 bool "Use a script to generate the .its script"
646 config SPL_FIT_GENERATOR
647 string ".its file generator script for U-Boot FIT image"
648 depends on USE_SPL_FIT_GENERATOR
649 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
650 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
651 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
652 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
654 Specifies a (platform specific) script file to generate the FIT
655 source file used to build the U-Boot FIT image file. This gets
656 passed a list of supported device tree file stub names to
657 include in the generated image.
663 config LEGACY_IMAGE_FORMAT
664 bool "Enable support for the legacy image format"
665 default y if !FIT_SIGNATURE
667 This option enables the legacy image format. It is enabled by
668 default for backward compatibility, unless FIT_SIGNATURE is
669 set where it is disabled so that unsigned images cannot be
670 loaded. If a board needs the legacy image format support in this
671 case, enable it here.
673 config OF_BOARD_SETUP
674 bool "Set up board-specific details in device tree before boot"
677 This causes U-Boot to call ft_board_setup() before booting into
678 the Operating System. This function can set up various
679 board-specific information in the device tree for use by the OS.
680 The device tree is then passed to the OS.
682 config OF_SYSTEM_SETUP
683 bool "Set up system-specific details in device tree before boot"
686 This causes U-Boot to call ft_system_setup() before booting into
687 the Operating System. This function can set up various
688 system-specific information in the device tree for use by the OS.
689 The device tree is then passed to the OS.
691 config OF_STDOUT_VIA_ALIAS
692 bool "Update the device-tree stdout alias from U-Boot"
695 This uses U-Boot's serial alias from the aliases node to update
696 the device tree passed to the OS. The "linux,stdout-path" property
697 in the chosen node is set to point to the correct serial node.
698 This option currently references CONFIG_CONS_INDEX, which is
699 incorrect when used with device tree as this option does not
700 exist / should not be used.
702 config SYS_EXTRA_OPTIONS
703 string "Extra Options (DEPRECATED)"
705 The old configuration infrastructure (= mkconfig + boards.cfg)
706 provided the extra options field. If you have something like
707 "HAS_BAR,BAZ=64", the optional options
709 #define CONFIG_BAZ 64
710 will be defined in include/config.h.
711 This option was prepared for the smooth migration from the old
712 configuration to Kconfig. Since this option will be removed sometime,
713 new boards should not use this option.
715 config HAVE_SYS_TEXT_BASE
717 depends on !NIOS2 && !XTENSA
722 depends on HAVE_SYS_TEXT_BASE
723 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
724 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
725 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
726 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
729 The address in memory that U-Boot will be running from, initially.
732 depends on ARC || ARCH_SUNXI || MPC83xx
733 int "CPU clock frequency"
735 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
737 config ARCH_FIXUP_FDT_MEMORY
738 bool "Enable arch_fixup_memory_banks() call"
741 Enable FDT memory map syncup before OS boot. This feature can be
742 used for booting OS with different memory setup where the part of
743 the memory location should be used for different purpose.
745 endmenu # Boot images
749 source "common/Kconfig"
753 source "disk/Kconfig"
761 source "drivers/Kconfig"
767 source "test/Kconfig"