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.
24 string "Local version - append to U-Boot release"
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.
33 config LOCALVERSION_AUTO
34 bool "Automatically append version information to the version string"
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
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.
46 (The actual string used here is the first eight characters produced
47 by running the command:
49 $ git rev-parse --verify HEAD
51 which is done within the script "scripts/setlocalversion".)
53 config CC_OPTIMIZE_FOR_SIZE
54 bool "Optimize for size"
57 Enabling this option will pass "-Os" instead of "-O2" to gcc
58 resulting in a smaller U-Boot image.
60 This option is enabled by default for U-Boot.
63 bool "Enable code coverage analysis"
66 Enabling this option will pass "--coverage" to gcc to compile
67 and link code instrumented for coverage analysis.
69 config DISTRO_DEFAULTS
70 bool "Select defaults suitable for booting general purpose Linux distributions"
72 select CMDLINE_EDITING
73 select CMD_BOOTI if ARM64
74 select CMD_BOOTZ if ARM && !ARM64
75 select CMD_DHCP if CMD_NET
81 select CMD_PART if PARTITIONS
82 select CMD_PING if CMD_NET
84 select ENV_VARS_UBOOT_CONFIG
86 select SUPPORT_RAW_INITRD
92 Select this to enable various options and commands which are suitable
93 for building u-boot for booting general purpose Linux distributions.
95 config ENV_VARS_UBOOT_CONFIG
96 bool "Add arch, board, vendor and soc variables to default environment"
98 Define this in order to add variables describing the
99 U-Boot build configuration to the default environment.
100 These will be named arch, cpu, board, vendor, and soc.
101 Enabling this option will cause the following to be defined:
109 int "Number of DRAM banks"
112 This defines the number of DRAM banks.
114 config SYS_BOOT_GET_CMDLINE
115 bool "Enable kernel command line setup"
117 Enables allocating and saving kernel cmdline in space between
118 "bootm_low" and "bootm_low" + BOOTMAPSZ.
120 config SYS_BOOT_GET_KBD
121 bool "Enable kernel board information setup"
123 Enables allocating and saving a kernel copy of the bd_info in
124 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
127 bool "Enable malloc() pool before relocation"
131 Before relocation, memory is very limited on many platforms. Still,
132 we can provide a small malloc() pool if needed. Driver model in
133 particular needs this to operate, so that it can allocate the
134 initial serial device and any others that are needed.
136 config SYS_MALLOC_F_LEN
137 hex "Size of malloc() pool before relocation"
138 depends on SYS_MALLOC_F
139 default 0x1000 if AM33XX
140 default 0x2800 if SANDBOX
143 Before relocation, memory is very limited on many platforms. Still,
144 we can provide a small malloc() pool if needed. Driver model in
145 particular needs this to operate, so that it can allocate the
146 initial serial device and any others that are needed.
148 config SYS_MALLOC_LEN
149 hex "Define memory for Dynamic allocation"
150 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP
152 This defines memory to be allocated for Dynamic allocation
153 TODO: Use for other architectures
155 config SPL_SYS_MALLOC_F_LEN
156 hex "Size of malloc() pool in SPL before relocation"
157 depends on SYS_MALLOC_F
158 default 0x2800 if RCAR_GEN3
159 default SYS_MALLOC_F_LEN
161 Before relocation, memory is very limited on many platforms. Still,
162 we can provide a small malloc() pool if needed. Driver model in
163 particular needs this to operate, so that it can allocate the
164 initial serial device and any others that are needed.
166 config TPL_SYS_MALLOC_F_LEN
167 hex "Size of malloc() pool in TPL before relocation"
168 depends on SYS_MALLOC_F
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.
177 bool "Configure standard U-Boot features (expert users)"
180 This option allows certain base U-Boot options and settings
181 to be disabled or tweaked. This is for specialized
182 environments which can tolerate a "non-standard" U-Boot.
183 Use this only if you really know what you are doing.
186 config SYS_MALLOC_CLEAR_ON_INIT
187 bool "Init with zeros the memory reserved for malloc (slow)"
190 This setting is enabled by default. The reserved malloc
191 memory is initialized with zeros, so first malloc calls
192 will return the pointer to the zeroed memory. But this
195 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
196 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
197 Then the boot time can be significantly reduced.
199 When disabling this, please check if malloc calls, maybe
200 should be replaced by calloc - if one expects zeroed memory.
203 bool "Enable debug information for tools"
205 Enable generation of debug information for tools such as mkimage.
206 This can be used for debugging purposes. With debug information
207 it is possible to set breakpoints on particular lines, single-step
208 debug through the source code, etc.
213 bool "64bit physical address support"
215 Say Y here to support 64bit physical memory address.
216 This can be used not only for 64bit SoCs, but also for
217 large physical address extension on 32bit SoCs.
220 bool "Build U-Boot as BIOS replacement"
223 This option allows to build a ROM version of U-Boot.
224 The build process generally requires several binary blobs
225 which are not shipped in the U-Boot source tree.
226 Please, see doc/README.x86 for details.
229 string "SPL image used in the combined SPL+U-Boot image"
230 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
231 default "spl/u-boot-spl.bin"
233 Select the SPL build target that shall be generated by the SPL
234 build process (default spl/u-boot-spl.bin). This image will be
235 used to generate a combined image with SPL and main U-Boot
236 proper as one single image.
239 string "Build target special images"
240 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
241 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
242 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
243 default "u-boot-elf.srec" if RCAR_GEN3
244 default "u-boot.itb" if SPL_LOAD_FIT && ARCH_SUNXI
245 default "u-boot.kwb" if KIRKWOOD
246 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
248 Some SoCs need special image types (e.g. U-Boot binary
249 with a special header) as build targets. By defining
250 CONFIG_BUILD_TARGET in the SoC / board header, this
251 special image will be automatically built upon calling
254 endmenu # General setup
258 config ANDROID_BOOT_IMAGE
259 bool "Enable support for Android Boot Images"
260 default y if FASTBOOT
262 This enables support for booting images which use the Android
266 bool "Support Flattened Image Tree"
270 This option allows you to boot the new uImage structure,
271 Flattened Image Tree. FIT is formally a FDT, which can include
272 images of various types (kernel, FDT blob, ramdisk, etc.)
273 in a single blob. To boot this new uImage structure,
274 pass the address of the blob to the "bootm" command.
275 FIT is very flexible, supporting compression, multiple images,
276 multiple configurations, verification through hashing and also
277 verified boot (secure boot using RSA).
281 config FIT_EXTERNAL_OFFSET
282 hex "FIT external data offset"
285 This specifies a data offset in fit image.
286 The offset is from data payload offset to the beginning of
287 fit image header. When specifies a offset, specific data
288 could be put in the hole between data payload and fit image
289 header, such as CSF data on i.MX platform.
291 config FIT_ENABLE_SHA256_SUPPORT
292 bool "Support SHA256 checksum of FIT image contents"
296 Enable this to support SHA256 checksum of FIT image contents. A
297 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
298 the image contents have not been corrupted. SHA256 is recommended
299 for use in secure applications since (as at 2016) there is no known
300 feasible attack that could produce a 'collision' with differing
301 input data. Use this for the highest security. Note that only the
302 SHA256 variant is supported: SHA512 and others are not currently
306 bool "Enable signature verification of FIT uImages"
311 This option enables signature verification of FIT uImages,
312 using a hash signed and verified using RSA. If
313 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
314 hashing is available using hardware, then the RSA library will use
315 it. See doc/uImage.FIT/signature.txt for more details.
317 WARNING: When relying on signed FIT images with a required signature
318 check the legacy image format is disabled by default, so that
319 unsigned images cannot be loaded. If a board needs the legacy image
320 format support in this case, enable it using
321 CONFIG_IMAGE_FORMAT_LEGACY.
323 config FIT_SIGNATURE_MAX_SIZE
324 hex "Max size of signed FIT structures"
325 depends on FIT_SIGNATURE
328 This option sets a max size in bytes for verified FIT uImages.
329 A sane value of 256MB protects corrupted DTB structures from overlapping
330 device memory. Assure this size does not extend past expected storage
333 config FIT_ENABLE_RSASSA_PSS_SUPPORT
334 bool "Support rsassa-pss signature scheme of FIT image contents"
335 depends on FIT_SIGNATURE
338 Enable this to support the pss padding algorithm as described
339 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
342 bool "Show verbose messages when FIT images fail"
344 Generally a system will have valid FIT images so debug messages
345 are a waste of code space. If you are debugging your images then
346 you can enable this option to get more verbose information about
349 config FIT_BEST_MATCH
350 bool "Select the best match for the kernel device tree"
352 When no configuration is explicitly selected, default to the
353 one whose fdt's compatibility field best matches that of
354 U-Boot itself. A match is considered "best" if it matches the
355 most specific compatibility entry of U-Boot's fdt's root node.
356 The order of entries in the configuration's fdt is ignored.
358 config FIT_IMAGE_POST_PROCESS
359 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
360 depends on TI_SECURE_DEVICE
362 Allows doing any sort of manipulation to blobs after they got extracted
363 from FIT images like stripping off headers or modifying the size of the
364 blob, verification, authentication, decryption etc. in a platform or
365 board specific way. In order to use this feature a platform or board-
366 specific implementation of board_fit_image_post_process() must be
367 provided. Also, anything done during this post-processing step would
368 need to be comprehended in how the images were prepared before being
369 injected into the FIT creation (i.e. the blobs would have been pre-
370 processed before being added to the FIT image).
375 bool "Support Flattened Image Tree within SPL"
380 bool "Support FIT printing within SPL"
383 Support printing the content of the fitImage in a verbose manner in SPL.
385 config SPL_FIT_SIGNATURE
386 bool "Enable signature verification of FIT firmware within SPL"
392 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
395 Normally with the SPL framework a legacy image is generated as part
396 of the build. This contains U-Boot along with information as to
397 where it should be loaded. This option instead enables generation
398 of a FIT (Flat Image Tree) which provides more flexibility. In
399 particular it can handle selecting from multiple device tree
400 and passing the correct one to U-Boot.
402 config SPL_LOAD_FIT_FULL
403 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
406 Normally with the SPL framework a legacy image is generated as part
407 of the build. This contains U-Boot along with information as to
408 where it should be loaded. This option instead enables generation
409 of a FIT (Flat Image Tree) which provides more flexibility. In
410 particular it can handle selecting from multiple device tree
411 and passing the correct one to U-Boot.
413 config SPL_FIT_IMAGE_POST_PROCESS
414 bool "Enable post-processing of FIT artifacts after loading by the SPL"
415 depends on SPL_LOAD_FIT
417 Allows doing any sort of manipulation to blobs after they got extracted
418 from the U-Boot FIT image like stripping off headers or modifying the
419 size of the blob, verification, authentication, decryption etc. in a
420 platform or board specific way. In order to use this feature a platform
421 or board-specific implementation of board_fit_image_post_process() must
422 be provided. Also, anything done during this post-processing step would
423 need to be comprehended in how the images were prepared before being
424 injected into the FIT creation (i.e. the blobs would have been pre-
425 processed before being added to the FIT image).
427 config SPL_FIT_SOURCE
428 string ".its source file for U-Boot FIT image"
431 Specifies a (platform specific) FIT source file to generate the
432 U-Boot FIT image. This could specify further image to load and/or
435 config SPL_FIT_GENERATOR
436 string ".its file generator script for U-Boot FIT image"
438 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
439 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
441 Specifies a (platform specific) script file to generate the FIT
442 source file used to build the U-Boot FIT image file. This gets
443 passed a list of supported device tree file stub names to
444 include in the generated image.
450 config IMAGE_FORMAT_LEGACY
451 bool "Enable support for the legacy image format"
452 default y if !FIT_SIGNATURE
454 This option enables the legacy image format. It is enabled by
455 default for backward compatibility, unless FIT_SIGNATURE is
456 set where it is disabled so that unsigned images cannot be
457 loaded. If a board needs the legacy image format support in this
458 case, enable it here.
460 config OF_BOARD_SETUP
461 bool "Set up board-specific details in device tree before boot"
464 This causes U-Boot to call ft_board_setup() before booting into
465 the Operating System. This function can set up various
466 board-specific information in the device tree for use by the OS.
467 The device tree is then passed to the OS.
469 config OF_SYSTEM_SETUP
470 bool "Set up system-specific details in device tree before boot"
473 This causes U-Boot to call ft_system_setup() before booting into
474 the Operating System. This function can set up various
475 system-specific information in the device tree for use by the OS.
476 The device tree is then passed to the OS.
478 config OF_STDOUT_VIA_ALIAS
479 bool "Update the device-tree stdout alias from U-Boot"
482 This uses U-Boot's serial alias from the aliases node to update
483 the device tree passed to the OS. The "linux,stdout-path" property
484 in the chosen node is set to point to the correct serial node.
485 This option currently references CONFIG_CONS_INDEX, which is
486 incorrect when used with device tree as this option does not
487 exist / should not be used.
489 config SYS_EXTRA_OPTIONS
490 string "Extra Options (DEPRECATED)"
492 The old configuration infrastructure (= mkconfig + boards.cfg)
493 provided the extra options field. If you have something like
494 "HAS_BAR,BAZ=64", the optional options
496 #define CONFIG_BAZ 64
497 will be defined in include/config.h.
498 This option was prepared for the smooth migration from the old
499 configuration to Kconfig. Since this option will be removed sometime,
500 new boards should not use this option.
503 depends on !NIOS2 && !XTENSA
505 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
506 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
507 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
508 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
511 The address in memory that U-Boot will be running from, initially.
516 depends on ARC || ARCH_SUNXI || MPC83xx
517 int "CPU clock frequency"
519 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
521 config ARCH_FIXUP_FDT_MEMORY
522 bool "Enable arch_fixup_memory_banks() call"
525 Enable FDT memory map syncup before OS boot. This feature can be
526 used for booting OS with different memory setup where the part of
527 the memory location should be used for different purpose.
529 endmenu # Boot images
533 source "common/Kconfig"
537 source "disk/Kconfig"
545 source "drivers/Kconfig"
551 source "test/Kconfig"