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 # Allow defaults in arch-specific code to override any given here
16 This option cannot be enabled. It is used as dependency
17 for broken and incomplete features.
22 This option cannot be enabled. It it used as a dependency for
23 code that relies on deprecated features that will be removed and
24 the conversion deadline has passed.
27 string "Local version - append to U-Boot release"
29 Append an extra string to the end of your U-Boot version.
30 This will show up in your boot log, for example.
31 The string you set here will be appended after the contents of
32 any files with a filename matching localversion* in your
33 object and source tree, in that order. Your total string can
34 be a maximum of 64 characters.
36 config LOCALVERSION_AUTO
37 bool "Automatically append version information to the version string"
40 This will try to automatically determine if the current tree is a
41 release tree by looking for Git tags that belong to the current
44 A string of the format -gxxxxxxxx will be added to the localversion
45 if a Git-based tree is found. The string generated by this will be
46 appended after any matching localversion* files, and after the value
47 set in CONFIG_LOCALVERSION.
49 (The actual string used here is the first eight characters produced
50 by running the command:
52 $ git rev-parse --verify HEAD
54 which is done within the script "scripts/setlocalversion".)
56 config CC_OPTIMIZE_FOR_SIZE
57 bool "Optimize for size"
60 Enabling this option will pass "-Os" instead of "-O2" to gcc
61 resulting in a smaller U-Boot image.
63 This option is enabled by default for U-Boot.
66 bool "Enable code coverage analysis"
69 Enabling this option will pass "--coverage" to gcc to compile
70 and link code instrumented for coverage analysis.
72 config DISTRO_DEFAULTS
73 bool "Select defaults suitable for booting general purpose Linux distributions"
75 select CMDLINE_EDITING
76 select CMD_BOOTI if ARM64
77 select CMD_BOOTZ if ARM && !ARM64
78 select CMD_DHCP if CMD_NET
84 select CMD_PART if PARTITIONS
85 select CMD_PING if CMD_NET
88 select ENV_VARS_UBOOT_CONFIG
90 select SUPPORT_RAW_INITRD
96 Select this to enable various options and commands which are suitable
97 for building u-boot for booting general purpose Linux distributions.
99 config ENV_VARS_UBOOT_CONFIG
100 bool "Add arch, board, vendor and soc variables to default environment"
102 Define this in order to add variables describing the
103 U-Boot build configuration to the default environment.
104 These will be named arch, cpu, board, vendor, and soc.
105 Enabling this option will cause the following to be defined:
113 int "Number of DRAM banks"
114 default 1 if ARCH_SUNXI || ARCH_OWL
117 This defines the number of DRAM banks.
119 config SYS_BOOT_GET_CMDLINE
120 bool "Enable kernel command line setup"
122 Enables allocating and saving kernel cmdline in space between
123 "bootm_low" and "bootm_low" + BOOTMAPSZ.
125 config SYS_BOOT_GET_KBD
126 bool "Enable kernel board information setup"
128 Enables allocating and saving a kernel copy of the bd_info in
129 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
132 bool "Enable malloc() pool before relocation"
136 Before relocation, memory is very limited on many platforms. Still,
137 we can provide a small malloc() pool if needed. Driver model in
138 particular needs this to operate, so that it can allocate the
139 initial serial device and any others that are needed.
141 config SYS_MALLOC_F_LEN
142 hex "Size of malloc() pool before relocation"
143 depends on SYS_MALLOC_F
144 default 0x1000 if AM33XX
145 default 0x2800 if SANDBOX
146 default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
147 ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
148 ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
152 Before relocation, memory is very limited on many platforms. Still,
153 we can provide a small malloc() pool if needed. Driver model in
154 particular needs this to operate, so that it can allocate the
155 initial serial device and any others that are needed.
157 config SYS_MALLOC_LEN
158 hex "Define memory for Dynamic allocation"
159 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
160 default 0x2000000 if ARCH_ROCKCHIP
162 This defines memory to be allocated for Dynamic allocation
163 TODO: Use for other architectures
165 config SPL_SYS_MALLOC_F_LEN
166 hex "Size of malloc() pool in SPL before relocation"
167 depends on SYS_MALLOC_F && SPL
168 default 0x2800 if RCAR_GEN3
169 default SYS_MALLOC_F_LEN
171 Before relocation, memory is very limited on many platforms. Still,
172 we can provide a small malloc() pool if needed. Driver model in
173 particular needs this to operate, so that it can allocate the
174 initial serial device and any others that are needed.
176 config TPL_SYS_MALLOC_F_LEN
177 hex "Size of malloc() pool in TPL before relocation"
178 depends on SYS_MALLOC_F && TPL
179 default SYS_MALLOC_F_LEN
181 Before relocation, memory is very limited on many platforms. Still,
182 we can provide a small malloc() pool if needed. Driver model in
183 particular needs this to operate, so that it can allocate the
184 initial serial device and any others that are needed.
187 bool "Configure standard U-Boot features (expert users)"
190 This option allows certain base U-Boot options and settings
191 to be disabled or tweaked. This is for specialized
192 environments which can tolerate a "non-standard" U-Boot.
193 Use this only if you really know what you are doing.
196 config SYS_MALLOC_CLEAR_ON_INIT
197 bool "Init with zeros the memory reserved for malloc (slow)"
200 This setting is enabled by default. The reserved malloc
201 memory is initialized with zeros, so first malloc calls
202 will return the pointer to the zeroed memory. But this
205 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
206 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
207 Then the boot time can be significantly reduced.
209 When disabling this, please check if malloc calls, maybe
210 should be replaced by calloc - if one expects zeroed memory.
213 bool "Enable debug information for tools"
215 Enable generation of debug information for tools such as mkimage.
216 This can be used for debugging purposes. With debug information
217 it is possible to set breakpoints on particular lines, single-step
218 debug through the source code, etc.
223 bool "64bit physical address support"
225 Say Y here to support 64bit physical memory address.
226 This can be used not only for 64bit SoCs, but also for
227 large physical address extension on 32bit SoCs.
230 bool "Build U-Boot as BIOS replacement"
233 This option allows to build a ROM version of U-Boot.
234 The build process generally requires several binary blobs
235 which are not shipped in the U-Boot source tree.
236 Please, see doc/arch/x86.rst for details.
239 string "SPL image used in the combined SPL+U-Boot image"
240 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
241 default "spl/u-boot-spl.bin"
244 Select the SPL build target that shall be generated by the SPL
245 build process (default spl/u-boot-spl.bin). This image will be
246 used to generate a combined image with SPL and main U-Boot
247 proper as one single image.
250 string "Build target special images"
251 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
252 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
253 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
254 default "u-boot-elf.srec" if RCAR_GEN3
255 default "u-boot.itb" if SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
256 ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
257 default "u-boot.kwb" if KIRKWOOD
258 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
259 default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
261 Some SoCs need special image types (e.g. U-Boot binary
262 with a special header) as build targets. By defining
263 CONFIG_BUILD_TARGET in the SoC / board header, this
264 special image will be automatically built upon calling
267 config SYS_CUSTOM_LDSCRIPT
268 bool "Use a custom location for the U-Boot linker script"
270 Normally when linking U-Boot we will look in the board directory,
271 the CPU directory and finally the "cpu" directory of the architecture
272 for the ile "u-boot.lds" and use that as our linker. However, in
273 some cases we need to provide a different linker script. To do so,
274 enable this option and then provide the location under
278 depends on SYS_CUSTOM_LDSCRIPT
279 string "Custom ldscript location"
281 Path within the source tree to the linker script to use for the
284 config ERR_PTR_OFFSET
288 Some U-Boot pointers have redundant information, so we can use a
289 scheme where we can return either an error code or a pointer with the
290 same return value. The default implementation just casts the pointer
291 to a number, however, this may fail on platforms where the end of the
292 address range is used for valid pointers (e.g. 0xffffff00 is a valid
293 heap pointer in socfpga SPL).
294 For such platforms, this value provides an upper range of those error
295 pointer values - up to 'MAX_ERRNO' bytes below this value must be
296 unused/invalid addresses.
298 config PLATFORM_ELFENTRY
300 default "__start" if MIPS
303 endmenu # General setup
307 config ANDROID_BOOT_IMAGE
308 bool "Enable support for Android Boot Images"
309 default y if FASTBOOT
311 This enables support for booting images which use the Android
315 bool "Support Flattened Image Tree"
319 This option allows you to boot the new uImage structure,
320 Flattened Image Tree. FIT is formally a FDT, which can include
321 images of various types (kernel, FDT blob, ramdisk, etc.)
322 in a single blob. To boot this new uImage structure,
323 pass the address of the blob to the "bootm" command.
324 FIT is very flexible, supporting compression, multiple images,
325 multiple configurations, verification through hashing and also
326 verified boot (secure boot using RSA).
330 config FIT_EXTERNAL_OFFSET
331 hex "FIT external data offset"
334 This specifies a data offset in fit image.
335 The offset is from data payload offset to the beginning of
336 fit image header. When specifies a offset, specific data
337 could be put in the hole between data payload and fit image
338 header, such as CSF data on i.MX platform.
340 config FIT_ENABLE_SHA256_SUPPORT
341 bool "Support SHA256 checksum of FIT image contents"
345 Enable this to support SHA256 checksum of FIT image contents. A
346 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
347 the image contents have not been corrupted. SHA256 is recommended
348 for use in secure applications since (as at 2016) there is no known
349 feasible attack that could produce a 'collision' with differing
350 input data. Use this for the highest security. Note that only the
351 SHA256 variant is supported: SHA512 and others are not currently
355 bool "Enable signature verification of FIT uImages"
360 select IMAGE_SIGN_INFO
362 This option enables signature verification of FIT uImages,
363 using a hash signed and verified using RSA. If
364 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
365 hashing is available using hardware, then the RSA library will use
366 it. See doc/uImage.FIT/signature.txt for more details.
368 WARNING: When relying on signed FIT images with a required signature
369 check the legacy image format is disabled by default, so that
370 unsigned images cannot be loaded. If a board needs the legacy image
371 format support in this case, enable it using
372 CONFIG_LEGACY_IMAGE_FORMAT.
374 config FIT_SIGNATURE_MAX_SIZE
375 hex "Max size of signed FIT structures"
376 depends on FIT_SIGNATURE
379 This option sets a max size in bytes for verified FIT uImages.
380 A sane value of 256MB protects corrupted DTB structures from overlapping
381 device memory. Assure this size does not extend past expected storage
384 config FIT_ENABLE_RSASSA_PSS_SUPPORT
385 bool "Support rsassa-pss signature scheme of FIT image contents"
386 depends on FIT_SIGNATURE
389 Enable this to support the pss padding algorithm as described
390 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
393 bool "Enable ciphering data in a FIT uImages"
397 Enable the feature of data ciphering/unciphering in the tool mkimage
398 and in the u-boot support of the FIT image.
401 bool "Show verbose messages when FIT images fail"
403 Generally a system will have valid FIT images so debug messages
404 are a waste of code space. If you are debugging your images then
405 you can enable this option to get more verbose information about
408 config FIT_BEST_MATCH
409 bool "Select the best match for the kernel device tree"
411 When no configuration is explicitly selected, default to the
412 one whose fdt's compatibility field best matches that of
413 U-Boot itself. A match is considered "best" if it matches the
414 most specific compatibility entry of U-Boot's fdt's root node.
415 The order of entries in the configuration's fdt is ignored.
417 config FIT_IMAGE_POST_PROCESS
418 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
419 depends on TI_SECURE_DEVICE
421 Allows doing any sort of manipulation to blobs after they got extracted
422 from FIT images like stripping off headers or modifying the size of the
423 blob, verification, authentication, decryption etc. in a platform or
424 board specific way. In order to use this feature a platform or board-
425 specific implementation of board_fit_image_post_process() must be
426 provided. Also, anything done during this post-processing step would
427 need to be comprehended in how the images were prepared before being
428 injected into the FIT creation (i.e. the blobs would have been pre-
429 processed before being added to the FIT image).
434 bool "Support Flattened Image Tree within SPL"
439 bool "Support FIT printing within SPL"
442 Support printing the content of the fitImage in a verbose manner in SPL.
444 config SPL_FIT_SIGNATURE
445 bool "Enable signature verification of FIT firmware within SPL"
449 select SPL_RSA_VERIFY
450 select SPL_IMAGE_SIGN_INFO
453 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
456 Normally with the SPL framework a legacy image is generated as part
457 of the build. This contains U-Boot along with information as to
458 where it should be loaded. This option instead enables generation
459 of a FIT (Flat Image Tree) which provides more flexibility. In
460 particular it can handle selecting from multiple device tree
461 and passing the correct one to U-Boot.
463 config SPL_LOAD_FIT_APPLY_OVERLAY
464 bool "Enable SPL applying DT overlays from FIT"
465 depends on SPL_LOAD_FIT
466 select OF_LIBFDT_OVERLAY
468 The device tree is loaded from the FIT image. Allow the SPL is to
469 also load device-tree overlays from the FIT image an apply them
470 over the device tree.
472 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
473 depends on SPL_LOAD_FIT_APPLY_OVERLAY
475 hex "size of temporary buffer used to load the overlays"
477 The size of the area where the overlays will be loaded and
478 uncompress. Must be at least as large as biggest overlay
481 config SPL_LOAD_FIT_FULL
482 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
485 Normally with the SPL framework a legacy image is generated as part
486 of the build. This contains U-Boot along with information as to
487 where it should be loaded. This option instead enables generation
488 of a FIT (Flat Image Tree) which provides more flexibility. In
489 particular it can handle selecting from multiple device tree
490 and passing the correct one to U-Boot.
492 config SPL_FIT_IMAGE_POST_PROCESS
493 bool "Enable post-processing of FIT artifacts after loading by the SPL"
494 depends on SPL_LOAD_FIT
496 Allows doing any sort of manipulation to blobs after they got extracted
497 from the U-Boot FIT image like stripping off headers or modifying the
498 size of the blob, verification, authentication, decryption etc. in a
499 platform or board specific way. In order to use this feature a platform
500 or board-specific implementation of board_fit_image_post_process() must
501 be provided. Also, anything done during this post-processing step would
502 need to be comprehended in how the images were prepared before being
503 injected into the FIT creation (i.e. the blobs would have been pre-
504 processed before being added to the FIT image).
506 config SPL_FIT_SOURCE
507 string ".its source file for U-Boot FIT image"
510 Specifies a (platform specific) FIT source file to generate the
511 U-Boot FIT image. This could specify further image to load and/or
514 config SPL_FIT_GENERATOR
515 string ".its file generator script for U-Boot FIT image"
517 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
518 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
519 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
520 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
522 Specifies a (platform specific) script file to generate the FIT
523 source file used to build the U-Boot FIT image file. This gets
524 passed a list of supported device tree file stub names to
525 include in the generated image.
531 config LEGACY_IMAGE_FORMAT
532 bool "Enable support for the legacy image format"
533 default y if !FIT_SIGNATURE
535 This option enables the legacy image format. It is enabled by
536 default for backward compatibility, unless FIT_SIGNATURE is
537 set where it is disabled so that unsigned images cannot be
538 loaded. If a board needs the legacy image format support in this
539 case, enable it here.
541 config OF_BOARD_SETUP
542 bool "Set up board-specific details in device tree before boot"
545 This causes U-Boot to call ft_board_setup() before booting into
546 the Operating System. This function can set up various
547 board-specific information in the device tree for use by the OS.
548 The device tree is then passed to the OS.
550 config OF_SYSTEM_SETUP
551 bool "Set up system-specific details in device tree before boot"
554 This causes U-Boot to call ft_system_setup() before booting into
555 the Operating System. This function can set up various
556 system-specific information in the device tree for use by the OS.
557 The device tree is then passed to the OS.
559 config OF_STDOUT_VIA_ALIAS
560 bool "Update the device-tree stdout alias from U-Boot"
563 This uses U-Boot's serial alias from the aliases node to update
564 the device tree passed to the OS. The "linux,stdout-path" property
565 in the chosen node is set to point to the correct serial node.
566 This option currently references CONFIG_CONS_INDEX, which is
567 incorrect when used with device tree as this option does not
568 exist / should not be used.
570 config SYS_EXTRA_OPTIONS
571 string "Extra Options (DEPRECATED)"
573 The old configuration infrastructure (= mkconfig + boards.cfg)
574 provided the extra options field. If you have something like
575 "HAS_BAR,BAZ=64", the optional options
577 #define CONFIG_BAZ 64
578 will be defined in include/config.h.
579 This option was prepared for the smooth migration from the old
580 configuration to Kconfig. Since this option will be removed sometime,
581 new boards should not use this option.
583 config HAVE_SYS_TEXT_BASE
585 depends on !NIOS2 && !XTENSA
590 depends on HAVE_SYS_TEXT_BASE
591 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
592 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
593 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
594 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
597 The address in memory that U-Boot will be running from, initially.
600 depends on ARC || ARCH_SUNXI || MPC83xx
601 int "CPU clock frequency"
603 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
605 config ARCH_FIXUP_FDT_MEMORY
606 bool "Enable arch_fixup_memory_banks() call"
609 Enable FDT memory map syncup before OS boot. This feature can be
610 used for booting OS with different memory setup where the part of
611 the memory location should be used for different purpose.
613 endmenu # Boot images
617 source "common/Kconfig"
621 source "disk/Kconfig"
629 source "drivers/Kconfig"
635 source "test/Kconfig"