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
91 Select this to enable various options and commands which are suitable
92 for building u-boot for booting general purpose Linux distributions.
94 config ENV_VARS_UBOOT_CONFIG
95 bool "Add arch, board, vendor and soc variables to default environment"
97 Define this in order to add variables describing the
98 U-Boot build configuration to the default environment.
99 These will be named arch, cpu, board, vendor, and soc.
100 Enabling this option will cause the following to be defined:
108 int "Number of DRAM banks"
111 This defines the number of DRAM banks.
113 config SYS_BOOT_GET_CMDLINE
114 bool "Enable kernel command line setup"
116 Enables allocating and saving kernel cmdline in space between
117 "bootm_low" and "bootm_low" + BOOTMAPSZ.
119 config SYS_BOOT_GET_KBD
120 bool "Enable kernel board information setup"
122 Enables allocating and saving a kernel copy of the bd_info in
123 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
126 bool "Enable malloc() pool before relocation"
129 Before relocation, memory is very limited on many platforms. Still,
130 we can provide a small malloc() pool if needed. Driver model in
131 particular needs this to operate, so that it can allocate the
132 initial serial device and any others that are needed.
134 config SYS_MALLOC_F_LEN
135 hex "Size of malloc() pool before relocation"
136 depends on SYS_MALLOC_F
137 default 0x1000 if AM33XX
140 Before relocation, memory is very limited on many platforms. Still,
141 we can provide a small malloc() pool if needed. Driver model in
142 particular needs this to operate, so that it can allocate the
143 initial serial device and any others that are needed.
145 config SYS_MALLOC_LEN
146 hex "Define memory for Dynamic allocation"
147 depends on ARCH_ZYNQ || ARCH_VERSAL
149 This defines memory to be allocated for Dynamic allocation
150 TODO: Use for other architectures
152 config SPL_SYS_MALLOC_F_LEN
153 hex "Size of malloc() pool in SPL before relocation"
154 depends on SYS_MALLOC_F
155 default SYS_MALLOC_F_LEN
157 Before relocation, memory is very limited on many platforms. Still,
158 we can provide a small malloc() pool if needed. Driver model in
159 particular needs this to operate, so that it can allocate the
160 initial serial device and any others that are needed.
162 config TPL_SYS_MALLOC_F_LEN
163 hex "Size of malloc() pool in TPL before relocation"
164 depends on SYS_MALLOC_F
165 default SYS_MALLOC_F_LEN
167 Before relocation, memory is very limited on many platforms. Still,
168 we can provide a small malloc() pool if needed. Driver model in
169 particular needs this to operate, so that it can allocate the
170 initial serial device and any others that are needed.
173 bool "Configure standard U-Boot features (expert users)"
176 This option allows certain base U-Boot options and settings
177 to be disabled or tweaked. This is for specialized
178 environments which can tolerate a "non-standard" U-Boot.
179 Use this only if you really know what you are doing.
182 config SYS_MALLOC_CLEAR_ON_INIT
183 bool "Init with zeros the memory reserved for malloc (slow)"
186 This setting is enabled by default. The reserved malloc
187 memory is initialized with zeros, so first malloc calls
188 will return the pointer to the zeroed memory. But this
191 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
192 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
193 Then the boot time can be significantly reduced.
195 When disabling this, please check if malloc calls, maybe
196 should be replaced by calloc - if one expects zeroed memory.
199 bool "Enable debug information for tools"
201 Enable generation of debug information for tools such as mkimage.
202 This can be used for debugging purposes. With debug information
203 it is possible to set breakpoints on particular lines, single-step
204 debug through the source code, etc.
209 bool "64bit physical address support"
211 Say Y here to support 64bit physical memory address.
212 This can be used not only for 64bit SoCs, but also for
213 large physical address extention on 32bit SoCs.
216 bool "Build U-Boot as BIOS replacement"
219 This option allows to build a ROM version of U-Boot.
220 The build process generally requires several binary blobs
221 which are not shipped in the U-Boot source tree.
222 Please, see doc/README.x86 for details.
224 endmenu # General setup
228 config ANDROID_BOOT_IMAGE
229 bool "Enable support for Android Boot Images"
230 default y if FASTBOOT
232 This enables support for booting images which use the Android
236 bool "Support Flattened Image Tree"
240 This option allows you to boot the new uImage structure,
241 Flattened Image Tree. FIT is formally a FDT, which can include
242 images of various types (kernel, FDT blob, ramdisk, etc.)
243 in a single blob. To boot this new uImage structure,
244 pass the address of the blob to the "bootm" command.
245 FIT is very flexible, supporting compression, multiple images,
246 multiple configurations, verification through hashing and also
247 verified boot (secure boot using RSA).
251 config FIT_ENABLE_SHA256_SUPPORT
252 bool "Support SHA256 checksum of FIT image contents"
256 Enable this to support SHA256 checksum of FIT image contents. A
257 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
258 the image contents have not been corrupted. SHA256 is recommended
259 for use in secure applications since (as at 2016) there is no known
260 feasible attack that could produce a 'collision' with differing
261 input data. Use this for the highest security. Note that only the
262 SHA256 variant is supported: SHA512 and others are not currently
266 bool "Enable signature verification of FIT uImages"
271 This option enables signature verification of FIT uImages,
272 using a hash signed and verified using RSA. If
273 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
274 hashing is available using hardware, then the RSA library will use
275 it. See doc/uImage.FIT/signature.txt for more details.
277 WARNING: When relying on signed FIT images with a required signature
278 check the legacy image format is disabled by default, so that
279 unsigned images cannot be loaded. If a board needs the legacy image
280 format support in this case, enable it using
281 CONFIG_IMAGE_FORMAT_LEGACY.
283 config FIT_SIGNATURE_MAX_SIZE
284 hex "Max size of signed FIT structures"
285 depends on FIT_SIGNATURE
288 This option sets a max size in bytes for verified FIT uImages.
289 A sane value of 256MB protects corrupted DTB structures from overlapping
290 device memory. Assure this size does not extend past expected storage
293 config FIT_ENABLE_RSASSA_PSS_SUPPORT
294 bool "Support rsassa-pss signature scheme of FIT image contents"
295 depends on FIT_SIGNATURE
298 Enable this to support the pss padding algorithm as described
299 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
302 bool "Show verbose messages when FIT images fail"
304 Generally a system will have valid FIT images so debug messages
305 are a waste of code space. If you are debugging your images then
306 you can enable this option to get more verbose information about
309 config FIT_BEST_MATCH
310 bool "Select the best match for the kernel device tree"
312 When no configuration is explicitly selected, default to the
313 one whose fdt's compatibility field best matches that of
314 U-Boot itself. A match is considered "best" if it matches the
315 most specific compatibility entry of U-Boot's fdt's root node.
316 The order of entries in the configuration's fdt is ignored.
318 config FIT_IMAGE_POST_PROCESS
319 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
320 depends on TI_SECURE_DEVICE
322 Allows doing any sort of manipulation to blobs after they got extracted
323 from FIT images like stripping off headers or modifying the size of the
324 blob, verification, authentication, decryption etc. in a platform or
325 board specific way. In order to use this feature a platform or board-
326 specific implementation of board_fit_image_post_process() must be
327 provided. Also, anything done during this post-processing step would
328 need to be comprehended in how the images were prepared before being
329 injected into the FIT creation (i.e. the blobs would have been pre-
330 processed before being added to the FIT image).
335 bool "Support Flattened Image Tree within SPL"
340 bool "Support FIT printing within SPL"
343 Support printing the content of the fitImage in a verbose manner in SPL.
345 config SPL_FIT_SIGNATURE
346 bool "Enable signature verification of FIT firmware within SPL"
352 bool "Enable SPL loading U-Boot as a FIT"
355 Normally with the SPL framework a legacy image is generated as part
356 of the build. This contains U-Boot along with information as to
357 where it should be loaded. This option instead enables generation
358 of a FIT (Flat Image Tree) which provides more flexibility. In
359 particular it can handle selecting from multiple device tree
360 and passing the correct one to U-Boot.
362 config SPL_LOAD_FIT_FULL
363 bool "Enable SPL loading U-Boot as a FIT"
366 Normally with the SPL framework a legacy image is generated as part
367 of the build. This contains U-Boot along with information as to
368 where it should be loaded. This option instead enables generation
369 of a FIT (Flat Image Tree) which provides more flexibility. In
370 particular it can handle selecting from multiple device tree
371 and passing the correct one to U-Boot.
373 config SPL_FIT_IMAGE_POST_PROCESS
374 bool "Enable post-processing of FIT artifacts after loading by the SPL"
375 depends on SPL_LOAD_FIT
377 Allows doing any sort of manipulation to blobs after they got extracted
378 from the U-Boot FIT image like stripping off headers or modifying the
379 size of the blob, verification, authentication, decryption etc. in a
380 platform or board specific way. In order to use this feature a platform
381 or board-specific implementation of board_fit_image_post_process() must
382 be provided. Also, anything done during this post-processing step would
383 need to be comprehended in how the images were prepared before being
384 injected into the FIT creation (i.e. the blobs would have been pre-
385 processed before being added to the FIT image).
387 config SPL_FIT_SOURCE
388 string ".its source file for U-Boot FIT image"
391 Specifies a (platform specific) FIT source file to generate the
392 U-Boot FIT image. This could specify further image to load and/or
395 config SPL_FIT_GENERATOR
396 string ".its file generator script for U-Boot FIT image"
398 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
400 Specifies a (platform specific) script file to generate the FIT
401 source file used to build the U-Boot FIT image file. This gets
402 passed a list of supported device tree file stub names to
403 include in the generated image.
409 config IMAGE_FORMAT_LEGACY
410 bool "Enable support for the legacy image format"
411 default y if !FIT_SIGNATURE
413 This option enables the legacy image format. It is enabled by
414 default for backward compatibility, unless FIT_SIGNATURE is
415 set where it is disabled so that unsigned images cannot be
416 loaded. If a board needs the legacy image format support in this
417 case, enable it here.
419 config OF_BOARD_SETUP
420 bool "Set up board-specific details in device tree before boot"
423 This causes U-Boot to call ft_board_setup() before booting into
424 the Operating System. This function can set up various
425 board-specific information in the device tree for use by the OS.
426 The device tree is then passed to the OS.
428 config OF_SYSTEM_SETUP
429 bool "Set up system-specific details in device tree before boot"
432 This causes U-Boot to call ft_system_setup() before booting into
433 the Operating System. This function can set up various
434 system-specific information in the device tree for use by the OS.
435 The device tree is then passed to the OS.
437 config OF_STDOUT_VIA_ALIAS
438 bool "Update the device-tree stdout alias from U-Boot"
441 This uses U-Boot's serial alias from the aliases node to update
442 the device tree passed to the OS. The "linux,stdout-path" property
443 in the chosen node is set to point to the correct serial node.
444 This option currently references CONFIG_CONS_INDEX, which is
445 incorrect when used with device tree as this option does not
446 exist / should not be used.
448 config SYS_EXTRA_OPTIONS
449 string "Extra Options (DEPRECATED)"
451 The old configuration infrastructure (= mkconfig + boards.cfg)
452 provided the extra options field. If you have something like
453 "HAS_BAR,BAZ=64", the optional options
455 #define CONFIG_BAZ 64
456 will be defined in include/config.h.
457 This option was prepared for the smooth migration from the old
458 configuration to Kconfig. Since this option will be removed sometime,
459 new boards should not use this option.
462 depends on !NIOS2 && !XTENSA
464 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
465 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
466 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
467 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
470 The address in memory that U-Boot will be running from, initially.
475 depends on ARC || ARCH_SUNXI
476 int "CPU clock frequency"
478 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
480 config ARCH_FIXUP_FDT_MEMORY
481 bool "Enable arch_fixup_memory_banks() call"
484 Enable FDT memory map syncup before OS boot. This feature can be
485 used for booting OS with different memory setup where the part of
486 the memory location should be used for different purpose.
488 endmenu # Boot images
492 source "common/Kconfig"
496 source "disk/Kconfig"
504 source "drivers/Kconfig"
510 source "test/Kconfig"