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
150 Before relocation, memory is very limited on many platforms. Still,
151 we can provide a small malloc() pool if needed. Driver model in
152 particular needs this to operate, so that it can allocate the
153 initial serial device and any others that are needed.
155 config SYS_MALLOC_LEN
156 hex "Define memory for Dynamic allocation"
157 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP
159 This defines memory to be allocated for Dynamic allocation
160 TODO: Use for other architectures
162 config SPL_SYS_MALLOC_F_LEN
163 hex "Size of malloc() pool in SPL before relocation"
164 depends on SYS_MALLOC_F
165 default 0x2800 if RCAR_GEN3
166 default SYS_MALLOC_F_LEN
168 Before relocation, memory is very limited on many platforms. Still,
169 we can provide a small malloc() pool if needed. Driver model in
170 particular needs this to operate, so that it can allocate the
171 initial serial device and any others that are needed.
173 config TPL_SYS_MALLOC_F_LEN
174 hex "Size of malloc() pool in TPL before relocation"
175 depends on SYS_MALLOC_F
176 default SYS_MALLOC_F_LEN
178 Before relocation, memory is very limited on many platforms. Still,
179 we can provide a small malloc() pool if needed. Driver model in
180 particular needs this to operate, so that it can allocate the
181 initial serial device and any others that are needed.
184 bool "Configure standard U-Boot features (expert users)"
187 This option allows certain base U-Boot options and settings
188 to be disabled or tweaked. This is for specialized
189 environments which can tolerate a "non-standard" U-Boot.
190 Use this only if you really know what you are doing.
193 config SYS_MALLOC_CLEAR_ON_INIT
194 bool "Init with zeros the memory reserved for malloc (slow)"
197 This setting is enabled by default. The reserved malloc
198 memory is initialized with zeros, so first malloc calls
199 will return the pointer to the zeroed memory. But this
202 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
203 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
204 Then the boot time can be significantly reduced.
206 When disabling this, please check if malloc calls, maybe
207 should be replaced by calloc - if one expects zeroed memory.
210 bool "Enable debug information for tools"
212 Enable generation of debug information for tools such as mkimage.
213 This can be used for debugging purposes. With debug information
214 it is possible to set breakpoints on particular lines, single-step
215 debug through the source code, etc.
220 bool "64bit physical address support"
222 Say Y here to support 64bit physical memory address.
223 This can be used not only for 64bit SoCs, but also for
224 large physical address extension on 32bit SoCs.
227 bool "Build U-Boot as BIOS replacement"
230 This option allows to build a ROM version of U-Boot.
231 The build process generally requires several binary blobs
232 which are not shipped in the U-Boot source tree.
233 Please, see doc/README.x86 for details.
236 string "SPL image used in the combined SPL+U-Boot image"
237 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
238 default "spl/u-boot-spl.bin"
240 Select the SPL build target that shall be generated by the SPL
241 build process (default spl/u-boot-spl.bin). This image will be
242 used to generate a combined image with SPL and main U-Boot
243 proper as one single image.
246 string "Build target special images"
247 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
248 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
249 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
250 default "u-boot-elf.srec" if RCAR_GEN3
251 default "u-boot.itb" if SPL_LOAD_FIT && ARCH_SUNXI
252 default "u-boot.kwb" if KIRKWOOD
253 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
255 Some SoCs need special image types (e.g. U-Boot binary
256 with a special header) as build targets. By defining
257 CONFIG_BUILD_TARGET in the SoC / board header, this
258 special image will be automatically built upon calling
261 endmenu # General setup
265 config ANDROID_BOOT_IMAGE
266 bool "Enable support for Android Boot Images"
267 default y if FASTBOOT
269 This enables support for booting images which use the Android
273 bool "Support Flattened Image Tree"
277 This option allows you to boot the new uImage structure,
278 Flattened Image Tree. FIT is formally a FDT, which can include
279 images of various types (kernel, FDT blob, ramdisk, etc.)
280 in a single blob. To boot this new uImage structure,
281 pass the address of the blob to the "bootm" command.
282 FIT is very flexible, supporting compression, multiple images,
283 multiple configurations, verification through hashing and also
284 verified boot (secure boot using RSA).
288 config FIT_EXTERNAL_OFFSET
289 hex "FIT external data offset"
292 This specifies a data offset in fit image.
293 The offset is from data payload offset to the beginning of
294 fit image header. When specifies a offset, specific data
295 could be put in the hole between data payload and fit image
296 header, such as CSF data on i.MX platform.
298 config FIT_ENABLE_SHA256_SUPPORT
299 bool "Support SHA256 checksum of FIT image contents"
303 Enable this to support SHA256 checksum of FIT image contents. A
304 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
305 the image contents have not been corrupted. SHA256 is recommended
306 for use in secure applications since (as at 2016) there is no known
307 feasible attack that could produce a 'collision' with differing
308 input data. Use this for the highest security. Note that only the
309 SHA256 variant is supported: SHA512 and others are not currently
313 bool "Enable signature verification of FIT uImages"
318 This option enables signature verification of FIT uImages,
319 using a hash signed and verified using RSA. If
320 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
321 hashing is available using hardware, then the RSA library will use
322 it. See doc/uImage.FIT/signature.txt for more details.
324 WARNING: When relying on signed FIT images with a required signature
325 check the legacy image format is disabled by default, so that
326 unsigned images cannot be loaded. If a board needs the legacy image
327 format support in this case, enable it using
328 CONFIG_IMAGE_FORMAT_LEGACY.
330 config FIT_SIGNATURE_MAX_SIZE
331 hex "Max size of signed FIT structures"
332 depends on FIT_SIGNATURE
335 This option sets a max size in bytes for verified FIT uImages.
336 A sane value of 256MB protects corrupted DTB structures from overlapping
337 device memory. Assure this size does not extend past expected storage
340 config FIT_ENABLE_RSASSA_PSS_SUPPORT
341 bool "Support rsassa-pss signature scheme of FIT image contents"
342 depends on FIT_SIGNATURE
345 Enable this to support the pss padding algorithm as described
346 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
349 bool "Show verbose messages when FIT images fail"
351 Generally a system will have valid FIT images so debug messages
352 are a waste of code space. If you are debugging your images then
353 you can enable this option to get more verbose information about
356 config FIT_BEST_MATCH
357 bool "Select the best match for the kernel device tree"
359 When no configuration is explicitly selected, default to the
360 one whose fdt's compatibility field best matches that of
361 U-Boot itself. A match is considered "best" if it matches the
362 most specific compatibility entry of U-Boot's fdt's root node.
363 The order of entries in the configuration's fdt is ignored.
365 config FIT_IMAGE_POST_PROCESS
366 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
367 depends on TI_SECURE_DEVICE
369 Allows doing any sort of manipulation to blobs after they got extracted
370 from FIT images like stripping off headers or modifying the size of the
371 blob, verification, authentication, decryption etc. in a platform or
372 board specific way. In order to use this feature a platform or board-
373 specific implementation of board_fit_image_post_process() must be
374 provided. Also, anything done during this post-processing step would
375 need to be comprehended in how the images were prepared before being
376 injected into the FIT creation (i.e. the blobs would have been pre-
377 processed before being added to the FIT image).
382 bool "Support Flattened Image Tree within SPL"
387 bool "Support FIT printing within SPL"
390 Support printing the content of the fitImage in a verbose manner in SPL.
392 config SPL_FIT_SIGNATURE
393 bool "Enable signature verification of FIT firmware within SPL"
399 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
402 Normally with the SPL framework a legacy image is generated as part
403 of the build. This contains U-Boot along with information as to
404 where it should be loaded. This option instead enables generation
405 of a FIT (Flat Image Tree) which provides more flexibility. In
406 particular it can handle selecting from multiple device tree
407 and passing the correct one to U-Boot.
409 config SPL_LOAD_FIT_FULL
410 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
413 Normally with the SPL framework a legacy image is generated as part
414 of the build. This contains U-Boot along with information as to
415 where it should be loaded. This option instead enables generation
416 of a FIT (Flat Image Tree) which provides more flexibility. In
417 particular it can handle selecting from multiple device tree
418 and passing the correct one to U-Boot.
420 config SPL_FIT_IMAGE_POST_PROCESS
421 bool "Enable post-processing of FIT artifacts after loading by the SPL"
422 depends on SPL_LOAD_FIT
424 Allows doing any sort of manipulation to blobs after they got extracted
425 from the U-Boot FIT image like stripping off headers or modifying the
426 size of the blob, verification, authentication, decryption etc. in a
427 platform or board specific way. In order to use this feature a platform
428 or board-specific implementation of board_fit_image_post_process() must
429 be provided. Also, anything done during this post-processing step would
430 need to be comprehended in how the images were prepared before being
431 injected into the FIT creation (i.e. the blobs would have been pre-
432 processed before being added to the FIT image).
434 config SPL_FIT_SOURCE
435 string ".its source file for U-Boot FIT image"
438 Specifies a (platform specific) FIT source file to generate the
439 U-Boot FIT image. This could specify further image to load and/or
442 config SPL_FIT_GENERATOR
443 string ".its file generator script for U-Boot FIT image"
445 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
446 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
448 Specifies a (platform specific) script file to generate the FIT
449 source file used to build the U-Boot FIT image file. This gets
450 passed a list of supported device tree file stub names to
451 include in the generated image.
457 config IMAGE_FORMAT_LEGACY
458 bool "Enable support for the legacy image format"
459 default y if !FIT_SIGNATURE
461 This option enables the legacy image format. It is enabled by
462 default for backward compatibility, unless FIT_SIGNATURE is
463 set where it is disabled so that unsigned images cannot be
464 loaded. If a board needs the legacy image format support in this
465 case, enable it here.
467 config OF_BOARD_SETUP
468 bool "Set up board-specific details in device tree before boot"
471 This causes U-Boot to call ft_board_setup() before booting into
472 the Operating System. This function can set up various
473 board-specific information in the device tree for use by the OS.
474 The device tree is then passed to the OS.
476 config OF_SYSTEM_SETUP
477 bool "Set up system-specific details in device tree before boot"
480 This causes U-Boot to call ft_system_setup() before booting into
481 the Operating System. This function can set up various
482 system-specific information in the device tree for use by the OS.
483 The device tree is then passed to the OS.
485 config OF_STDOUT_VIA_ALIAS
486 bool "Update the device-tree stdout alias from U-Boot"
489 This uses U-Boot's serial alias from the aliases node to update
490 the device tree passed to the OS. The "linux,stdout-path" property
491 in the chosen node is set to point to the correct serial node.
492 This option currently references CONFIG_CONS_INDEX, which is
493 incorrect when used with device tree as this option does not
494 exist / should not be used.
496 config SYS_EXTRA_OPTIONS
497 string "Extra Options (DEPRECATED)"
499 The old configuration infrastructure (= mkconfig + boards.cfg)
500 provided the extra options field. If you have something like
501 "HAS_BAR,BAZ=64", the optional options
503 #define CONFIG_BAZ 64
504 will be defined in include/config.h.
505 This option was prepared for the smooth migration from the old
506 configuration to Kconfig. Since this option will be removed sometime,
507 new boards should not use this option.
510 depends on !NIOS2 && !XTENSA
512 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
513 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
514 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
515 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
518 The address in memory that U-Boot will be running from, initially.
523 depends on ARC || ARCH_SUNXI || MPC83xx
524 int "CPU clock frequency"
526 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
528 config ARCH_FIXUP_FDT_MEMORY
529 bool "Enable arch_fixup_memory_banks() call"
532 Enable FDT memory map syncup before OS boot. This feature can be
533 used for booting OS with different memory setup where the part of
534 the memory location should be used for different purpose.
536 endmenu # Boot images
540 source "common/Kconfig"
544 source "disk/Kconfig"
552 source "drivers/Kconfig"
558 source "test/Kconfig"