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
260 Some SoCs need special image types (e.g. U-Boot binary
261 with a special header) as build targets. By defining
262 CONFIG_BUILD_TARGET in the SoC / board header, this
263 special image will be automatically built upon calling
266 config SYS_CUSTOM_LDSCRIPT
267 bool "Use a custom location for the U-Boot linker script"
269 Normally when linking U-Boot we will look in the board directory,
270 the CPU directory and finally the "cpu" directory of the architecture
271 for the ile "u-boot.lds" and use that as our linker. However, in
272 some cases we need to provide a different linker script. To do so,
273 enable this option and then provide the location under
277 depends on SYS_CUSTOM_LDSCRIPT
278 string "Custom ldscript location"
280 Path within the source tree to the linker script to use for the
283 endmenu # General setup
287 config ANDROID_BOOT_IMAGE
288 bool "Enable support for Android Boot Images"
289 default y if FASTBOOT
291 This enables support for booting images which use the Android
295 bool "Support Flattened Image Tree"
299 This option allows you to boot the new uImage structure,
300 Flattened Image Tree. FIT is formally a FDT, which can include
301 images of various types (kernel, FDT blob, ramdisk, etc.)
302 in a single blob. To boot this new uImage structure,
303 pass the address of the blob to the "bootm" command.
304 FIT is very flexible, supporting compression, multiple images,
305 multiple configurations, verification through hashing and also
306 verified boot (secure boot using RSA).
310 config FIT_EXTERNAL_OFFSET
311 hex "FIT external data offset"
314 This specifies a data offset in fit image.
315 The offset is from data payload offset to the beginning of
316 fit image header. When specifies a offset, specific data
317 could be put in the hole between data payload and fit image
318 header, such as CSF data on i.MX platform.
320 config FIT_ENABLE_SHA256_SUPPORT
321 bool "Support SHA256 checksum of FIT image contents"
325 Enable this to support SHA256 checksum of FIT image contents. A
326 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
327 the image contents have not been corrupted. SHA256 is recommended
328 for use in secure applications since (as at 2016) there is no known
329 feasible attack that could produce a 'collision' with differing
330 input data. Use this for the highest security. Note that only the
331 SHA256 variant is supported: SHA512 and others are not currently
335 bool "Enable signature verification of FIT uImages"
340 This option enables signature verification of FIT uImages,
341 using a hash signed and verified using RSA. If
342 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
343 hashing is available using hardware, then the RSA library will use
344 it. See doc/uImage.FIT/signature.txt for more details.
346 WARNING: When relying on signed FIT images with a required signature
347 check the legacy image format is disabled by default, so that
348 unsigned images cannot be loaded. If a board needs the legacy image
349 format support in this case, enable it using
350 CONFIG_LEGACY_IMAGE_FORMAT.
352 config FIT_SIGNATURE_MAX_SIZE
353 hex "Max size of signed FIT structures"
354 depends on FIT_SIGNATURE
357 This option sets a max size in bytes for verified FIT uImages.
358 A sane value of 256MB protects corrupted DTB structures from overlapping
359 device memory. Assure this size does not extend past expected storage
362 config FIT_ENABLE_RSASSA_PSS_SUPPORT
363 bool "Support rsassa-pss signature scheme of FIT image contents"
364 depends on FIT_SIGNATURE
367 Enable this to support the pss padding algorithm as described
368 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
371 bool "Show verbose messages when FIT images fail"
373 Generally a system will have valid FIT images so debug messages
374 are a waste of code space. If you are debugging your images then
375 you can enable this option to get more verbose information about
378 config FIT_BEST_MATCH
379 bool "Select the best match for the kernel device tree"
381 When no configuration is explicitly selected, default to the
382 one whose fdt's compatibility field best matches that of
383 U-Boot itself. A match is considered "best" if it matches the
384 most specific compatibility entry of U-Boot's fdt's root node.
385 The order of entries in the configuration's fdt is ignored.
387 config FIT_IMAGE_POST_PROCESS
388 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
389 depends on TI_SECURE_DEVICE
391 Allows doing any sort of manipulation to blobs after they got extracted
392 from FIT images like stripping off headers or modifying the size of the
393 blob, verification, authentication, decryption etc. in a platform or
394 board specific way. In order to use this feature a platform or board-
395 specific implementation of board_fit_image_post_process() must be
396 provided. Also, anything done during this post-processing step would
397 need to be comprehended in how the images were prepared before being
398 injected into the FIT creation (i.e. the blobs would have been pre-
399 processed before being added to the FIT image).
404 bool "Support Flattened Image Tree within SPL"
409 bool "Support FIT printing within SPL"
412 Support printing the content of the fitImage in a verbose manner in SPL.
414 config SPL_FIT_SIGNATURE
415 bool "Enable signature verification of FIT firmware within SPL"
421 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
424 Normally with the SPL framework a legacy image is generated as part
425 of the build. This contains U-Boot along with information as to
426 where it should be loaded. This option instead enables generation
427 of a FIT (Flat Image Tree) which provides more flexibility. In
428 particular it can handle selecting from multiple device tree
429 and passing the correct one to U-Boot.
431 config SPL_LOAD_FIT_FULL
432 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
435 Normally with the SPL framework a legacy image is generated as part
436 of the build. This contains U-Boot along with information as to
437 where it should be loaded. This option instead enables generation
438 of a FIT (Flat Image Tree) which provides more flexibility. In
439 particular it can handle selecting from multiple device tree
440 and passing the correct one to U-Boot.
442 config SPL_FIT_IMAGE_POST_PROCESS
443 bool "Enable post-processing of FIT artifacts after loading by the SPL"
444 depends on SPL_LOAD_FIT
446 Allows doing any sort of manipulation to blobs after they got extracted
447 from the U-Boot FIT image like stripping off headers or modifying the
448 size of the blob, verification, authentication, decryption etc. in a
449 platform or board specific way. In order to use this feature a platform
450 or board-specific implementation of board_fit_image_post_process() must
451 be provided. Also, anything done during this post-processing step would
452 need to be comprehended in how the images were prepared before being
453 injected into the FIT creation (i.e. the blobs would have been pre-
454 processed before being added to the FIT image).
456 config SPL_FIT_SOURCE
457 string ".its source file for U-Boot FIT image"
460 Specifies a (platform specific) FIT source file to generate the
461 U-Boot FIT image. This could specify further image to load and/or
464 config SPL_FIT_GENERATOR
465 string ".its file generator script for U-Boot FIT image"
467 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
468 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
469 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
471 Specifies a (platform specific) script file to generate the FIT
472 source file used to build the U-Boot FIT image file. This gets
473 passed a list of supported device tree file stub names to
474 include in the generated image.
480 config LEGACY_IMAGE_FORMAT
481 bool "Enable support for the legacy image format"
482 default y if !FIT_SIGNATURE
484 This option enables the legacy image format. It is enabled by
485 default for backward compatibility, unless FIT_SIGNATURE is
486 set where it is disabled so that unsigned images cannot be
487 loaded. If a board needs the legacy image format support in this
488 case, enable it here.
490 config OF_BOARD_SETUP
491 bool "Set up board-specific details in device tree before boot"
494 This causes U-Boot to call ft_board_setup() before booting into
495 the Operating System. This function can set up various
496 board-specific information in the device tree for use by the OS.
497 The device tree is then passed to the OS.
499 config OF_SYSTEM_SETUP
500 bool "Set up system-specific details in device tree before boot"
503 This causes U-Boot to call ft_system_setup() before booting into
504 the Operating System. This function can set up various
505 system-specific information in the device tree for use by the OS.
506 The device tree is then passed to the OS.
508 config OF_STDOUT_VIA_ALIAS
509 bool "Update the device-tree stdout alias from U-Boot"
512 This uses U-Boot's serial alias from the aliases node to update
513 the device tree passed to the OS. The "linux,stdout-path" property
514 in the chosen node is set to point to the correct serial node.
515 This option currently references CONFIG_CONS_INDEX, which is
516 incorrect when used with device tree as this option does not
517 exist / should not be used.
519 config SYS_EXTRA_OPTIONS
520 string "Extra Options (DEPRECATED)"
522 The old configuration infrastructure (= mkconfig + boards.cfg)
523 provided the extra options field. If you have something like
524 "HAS_BAR,BAZ=64", the optional options
526 #define CONFIG_BAZ 64
527 will be defined in include/config.h.
528 This option was prepared for the smooth migration from the old
529 configuration to Kconfig. Since this option will be removed sometime,
530 new boards should not use this option.
533 depends on !NIOS2 && !XTENSA
535 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
536 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
537 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
538 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
541 The address in memory that U-Boot will be running from, initially.
546 depends on ARC || ARCH_SUNXI || MPC83xx
547 int "CPU clock frequency"
549 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
551 config ARCH_FIXUP_FDT_MEMORY
552 bool "Enable arch_fixup_memory_banks() call"
555 Enable FDT memory map syncup before OS boot. This feature can be
556 used for booting OS with different memory setup where the part of
557 the memory location should be used for different purpose.
559 endmenu # Boot images
563 source "common/Kconfig"
567 source "disk/Kconfig"
575 source "drivers/Kconfig"
581 source "test/Kconfig"