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"
10 option env="UBOOTVERSION"
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.
70 bool "Enable code coverage analysis"
73 Enabling this option will pass "--coverage" to gcc to compile
74 and link code instrumented for coverage analysis.
76 config DISTRO_DEFAULTS
77 bool "Select defaults suitable for booting general purpose Linux distributions"
79 select CMDLINE_EDITING
80 select CMD_BOOTI if ARM64
81 select CMD_BOOTZ if ARM && !ARM64
82 select CMD_DHCP if CMD_NET
88 select CMD_PART if PARTITIONS
89 select CMD_PING if CMD_NET
91 select ENV_VARS_UBOOT_CONFIG
93 select SUPPORT_RAW_INITRD
99 Select this to enable various options and commands which are suitable
100 for building u-boot for booting general purpose Linux distributions.
102 config ENV_VARS_UBOOT_CONFIG
103 bool "Add arch, board, vendor and soc variables to default environment"
105 Define this in order to add variables describing the
106 U-Boot build configuration to the default environment.
107 These will be named arch, cpu, board, vendor, and soc.
108 Enabling this option will cause the following to be defined:
116 int "Number of DRAM banks"
119 This defines the number of DRAM banks.
121 config SYS_BOOT_GET_CMDLINE
122 bool "Enable kernel command line setup"
124 Enables allocating and saving kernel cmdline in space between
125 "bootm_low" and "bootm_low" + BOOTMAPSZ.
127 config SYS_BOOT_GET_KBD
128 bool "Enable kernel board information setup"
130 Enables allocating and saving a kernel copy of the bd_info in
131 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
134 bool "Enable malloc() pool before relocation"
138 Before relocation, memory is very limited on many platforms. Still,
139 we can provide a small malloc() pool if needed. Driver model in
140 particular needs this to operate, so that it can allocate the
141 initial serial device and any others that are needed.
143 config SYS_MALLOC_F_LEN
144 hex "Size of malloc() pool before relocation"
145 depends on SYS_MALLOC_F
146 default 0x1000 if AM33XX
147 default 0x2800 if SANDBOX
148 default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
149 ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5)
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/README.x86 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 && (ROCKCHIP_RK3399 || \
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 endmenu # General setup
288 config ANDROID_BOOT_IMAGE
289 bool "Enable support for Android Boot Images"
290 default y if FASTBOOT
292 This enables support for booting images which use the Android
296 bool "Support Flattened Image Tree"
300 This option allows you to boot the new uImage structure,
301 Flattened Image Tree. FIT is formally a FDT, which can include
302 images of various types (kernel, FDT blob, ramdisk, etc.)
303 in a single blob. To boot this new uImage structure,
304 pass the address of the blob to the "bootm" command.
305 FIT is very flexible, supporting compression, multiple images,
306 multiple configurations, verification through hashing and also
307 verified boot (secure boot using RSA).
311 config FIT_EXTERNAL_OFFSET
312 hex "FIT external data offset"
315 This specifies a data offset in fit image.
316 The offset is from data payload offset to the beginning of
317 fit image header. When specifies a offset, specific data
318 could be put in the hole between data payload and fit image
319 header, such as CSF data on i.MX platform.
321 config FIT_ENABLE_SHA256_SUPPORT
322 bool "Support SHA256 checksum of FIT image contents"
326 Enable this to support SHA256 checksum of FIT image contents. A
327 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
328 the image contents have not been corrupted. SHA256 is recommended
329 for use in secure applications since (as at 2016) there is no known
330 feasible attack that could produce a 'collision' with differing
331 input data. Use this for the highest security. Note that only the
332 SHA256 variant is supported: SHA512 and others are not currently
336 bool "Enable signature verification of FIT uImages"
341 This option enables signature verification of FIT uImages,
342 using a hash signed and verified using RSA. If
343 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
344 hashing is available using hardware, then the RSA library will use
345 it. See doc/uImage.FIT/signature.txt for more details.
347 WARNING: When relying on signed FIT images with a required signature
348 check the legacy image format is disabled by default, so that
349 unsigned images cannot be loaded. If a board needs the legacy image
350 format support in this case, enable it using
351 CONFIG_LEGACY_IMAGE_FORMAT.
353 config FIT_SIGNATURE_MAX_SIZE
354 hex "Max size of signed FIT structures"
355 depends on FIT_SIGNATURE
358 This option sets a max size in bytes for verified FIT uImages.
359 A sane value of 256MB protects corrupted DTB structures from overlapping
360 device memory. Assure this size does not extend past expected storage
363 config FIT_ENABLE_RSASSA_PSS_SUPPORT
364 bool "Support rsassa-pss signature scheme of FIT image contents"
365 depends on FIT_SIGNATURE
368 Enable this to support the pss padding algorithm as described
369 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
372 bool "Show verbose messages when FIT images fail"
374 Generally a system will have valid FIT images so debug messages
375 are a waste of code space. If you are debugging your images then
376 you can enable this option to get more verbose information about
379 config FIT_BEST_MATCH
380 bool "Select the best match for the kernel device tree"
382 When no configuration is explicitly selected, default to the
383 one whose fdt's compatibility field best matches that of
384 U-Boot itself. A match is considered "best" if it matches the
385 most specific compatibility entry of U-Boot's fdt's root node.
386 The order of entries in the configuration's fdt is ignored.
388 config FIT_IMAGE_POST_PROCESS
389 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
390 depends on TI_SECURE_DEVICE
392 Allows doing any sort of manipulation to blobs after they got extracted
393 from FIT images like stripping off headers or modifying the size of the
394 blob, verification, authentication, decryption etc. in a platform or
395 board specific way. In order to use this feature a platform or board-
396 specific implementation of board_fit_image_post_process() must be
397 provided. Also, anything done during this post-processing step would
398 need to be comprehended in how the images were prepared before being
399 injected into the FIT creation (i.e. the blobs would have been pre-
400 processed before being added to the FIT image).
405 bool "Support Flattened Image Tree within SPL"
410 bool "Support FIT printing within SPL"
413 Support printing the content of the fitImage in a verbose manner in SPL.
415 config SPL_FIT_SIGNATURE
416 bool "Enable signature verification of FIT firmware within SPL"
422 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
425 Normally with the SPL framework a legacy image is generated as part
426 of the build. This contains U-Boot along with information as to
427 where it should be loaded. This option instead enables generation
428 of a FIT (Flat Image Tree) which provides more flexibility. In
429 particular it can handle selecting from multiple device tree
430 and passing the correct one to U-Boot.
432 config SPL_LOAD_FIT_FULL
433 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
436 Normally with the SPL framework a legacy image is generated as part
437 of the build. This contains U-Boot along with information as to
438 where it should be loaded. This option instead enables generation
439 of a FIT (Flat Image Tree) which provides more flexibility. In
440 particular it can handle selecting from multiple device tree
441 and passing the correct one to U-Boot.
443 config SPL_FIT_IMAGE_POST_PROCESS
444 bool "Enable post-processing of FIT artifacts after loading by the SPL"
445 depends on SPL_LOAD_FIT
447 Allows doing any sort of manipulation to blobs after they got extracted
448 from the U-Boot FIT image like stripping off headers or modifying the
449 size of the blob, verification, authentication, decryption etc. in a
450 platform or board specific way. In order to use this feature a platform
451 or board-specific implementation of board_fit_image_post_process() must
452 be provided. Also, anything done during this post-processing step would
453 need to be comprehended in how the images were prepared before being
454 injected into the FIT creation (i.e. the blobs would have been pre-
455 processed before being added to the FIT image).
457 config SPL_FIT_SOURCE
458 string ".its source file for U-Boot FIT image"
461 Specifies a (platform specific) FIT source file to generate the
462 U-Boot FIT image. This could specify further image to load and/or
465 config SPL_FIT_GENERATOR
466 string ".its file generator script for U-Boot FIT image"
468 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
469 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
470 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
472 Specifies a (platform specific) script file to generate the FIT
473 source file used to build the U-Boot FIT image file. This gets
474 passed a list of supported device tree file stub names to
475 include in the generated image.
481 config LEGACY_IMAGE_FORMAT
482 bool "Enable support for the legacy image format"
483 default y if !FIT_SIGNATURE
485 This option enables the legacy image format. It is enabled by
486 default for backward compatibility, unless FIT_SIGNATURE is
487 set where it is disabled so that unsigned images cannot be
488 loaded. If a board needs the legacy image format support in this
489 case, enable it here.
491 config OF_BOARD_SETUP
492 bool "Set up board-specific details in device tree before boot"
495 This causes U-Boot to call ft_board_setup() before booting into
496 the Operating System. This function can set up various
497 board-specific information in the device tree for use by the OS.
498 The device tree is then passed to the OS.
500 config OF_SYSTEM_SETUP
501 bool "Set up system-specific details in device tree before boot"
504 This causes U-Boot to call ft_system_setup() before booting into
505 the Operating System. This function can set up various
506 system-specific information in the device tree for use by the OS.
507 The device tree is then passed to the OS.
509 config OF_STDOUT_VIA_ALIAS
510 bool "Update the device-tree stdout alias from U-Boot"
513 This uses U-Boot's serial alias from the aliases node to update
514 the device tree passed to the OS. The "linux,stdout-path" property
515 in the chosen node is set to point to the correct serial node.
516 This option currently references CONFIG_CONS_INDEX, which is
517 incorrect when used with device tree as this option does not
518 exist / should not be used.
520 config SYS_EXTRA_OPTIONS
521 string "Extra Options (DEPRECATED)"
523 The old configuration infrastructure (= mkconfig + boards.cfg)
524 provided the extra options field. If you have something like
525 "HAS_BAR,BAZ=64", the optional options
527 #define CONFIG_BAZ 64
528 will be defined in include/config.h.
529 This option was prepared for the smooth migration from the old
530 configuration to Kconfig. Since this option will be removed sometime,
531 new boards should not use this option.
534 depends on !NIOS2 && !XTENSA
536 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
537 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
538 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
539 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
542 The address in memory that U-Boot will be running from, initially.
547 depends on ARC || ARCH_SUNXI || MPC83xx
548 int "CPU clock frequency"
550 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
552 config ARCH_FIXUP_FDT_MEMORY
553 bool "Enable arch_fixup_memory_banks() call"
556 Enable FDT memory map syncup before OS boot. This feature can be
557 used for booting OS with different memory setup where the part of
558 the memory location should be used for different purpose.
560 endmenu # Boot images
564 source "common/Kconfig"
568 source "disk/Kconfig"
576 source "drivers/Kconfig"
582 source "test/Kconfig"