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"
130 Before relocation, memory is very limited on many platforms. Still,
131 we can provide a small malloc() pool if needed. Driver model in
132 particular needs this to operate, so that it can allocate the
133 initial serial device and any others that are needed.
135 config SYS_MALLOC_F_LEN
136 hex "Size of malloc() pool before relocation"
137 depends on SYS_MALLOC_F
138 default 0x1000 if AM33XX
141 Before relocation, memory is very limited on many platforms. Still,
142 we can provide a small malloc() pool if needed. Driver model in
143 particular needs this to operate, so that it can allocate the
144 initial serial device and any others that are needed.
146 config SYS_MALLOC_LEN
147 hex "Define memory for Dynamic allocation"
148 depends on ARCH_ZYNQ || ARCH_VERSAL
150 This defines memory to be allocated for Dynamic allocation
151 TODO: Use for other architectures
153 config SPL_SYS_MALLOC_F_LEN
154 hex "Size of malloc() pool in SPL before relocation"
155 depends on SYS_MALLOC_F
156 default SYS_MALLOC_F_LEN
158 Before relocation, memory is very limited on many platforms. Still,
159 we can provide a small malloc() pool if needed. Driver model in
160 particular needs this to operate, so that it can allocate the
161 initial serial device and any others that are needed.
163 config TPL_SYS_MALLOC_F_LEN
164 hex "Size of malloc() pool in TPL before relocation"
165 depends on SYS_MALLOC_F
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.
174 bool "Configure standard U-Boot features (expert users)"
177 This option allows certain base U-Boot options and settings
178 to be disabled or tweaked. This is for specialized
179 environments which can tolerate a "non-standard" U-Boot.
180 Use this only if you really know what you are doing.
183 config SYS_MALLOC_CLEAR_ON_INIT
184 bool "Init with zeros the memory reserved for malloc (slow)"
187 This setting is enabled by default. The reserved malloc
188 memory is initialized with zeros, so first malloc calls
189 will return the pointer to the zeroed memory. But this
192 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
193 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
194 Then the boot time can be significantly reduced.
196 When disabling this, please check if malloc calls, maybe
197 should be replaced by calloc - if one expects zeroed memory.
200 bool "Enable debug information for tools"
202 Enable generation of debug information for tools such as mkimage.
203 This can be used for debugging purposes. With debug information
204 it is possible to set breakpoints on particular lines, single-step
205 debug through the source code, etc.
210 bool "64bit physical address support"
212 Say Y here to support 64bit physical memory address.
213 This can be used not only for 64bit SoCs, but also for
214 large physical address extention on 32bit SoCs.
217 bool "Build U-Boot as BIOS replacement"
220 This option allows to build a ROM version of U-Boot.
221 The build process generally requires several binary blobs
222 which are not shipped in the U-Boot source tree.
223 Please, see doc/README.x86 for details.
225 endmenu # General setup
229 config ANDROID_BOOT_IMAGE
230 bool "Enable support for Android Boot Images"
231 default y if FASTBOOT
233 This enables support for booting images which use the Android
237 bool "Support Flattened Image Tree"
241 This option allows you to boot the new uImage structure,
242 Flattened Image Tree. FIT is formally a FDT, which can include
243 images of various types (kernel, FDT blob, ramdisk, etc.)
244 in a single blob. To boot this new uImage structure,
245 pass the address of the blob to the "bootm" command.
246 FIT is very flexible, supporting compression, multiple images,
247 multiple configurations, verification through hashing and also
248 verified boot (secure boot using RSA).
252 config FIT_EXTERNAL_OFFSET
256 This specifies a data offset in fit image.
257 The offset is from data payload offset to the beginning of
258 fit image header. When specifies a offset, specific data
259 could be put in the hole between data payload and fit image
260 header, such as CSF data on i.MX platform.
262 config FIT_ENABLE_SHA256_SUPPORT
263 bool "Support SHA256 checksum of FIT image contents"
267 Enable this to support SHA256 checksum of FIT image contents. A
268 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
269 the image contents have not been corrupted. SHA256 is recommended
270 for use in secure applications since (as at 2016) there is no known
271 feasible attack that could produce a 'collision' with differing
272 input data. Use this for the highest security. Note that only the
273 SHA256 variant is supported: SHA512 and others are not currently
277 bool "Enable signature verification of FIT uImages"
282 This option enables signature verification of FIT uImages,
283 using a hash signed and verified using RSA. If
284 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
285 hashing is available using hardware, then the RSA library will use
286 it. See doc/uImage.FIT/signature.txt for more details.
288 WARNING: When relying on signed FIT images with a required signature
289 check the legacy image format is disabled by default, so that
290 unsigned images cannot be loaded. If a board needs the legacy image
291 format support in this case, enable it using
292 CONFIG_IMAGE_FORMAT_LEGACY.
294 config FIT_SIGNATURE_MAX_SIZE
295 hex "Max size of signed FIT structures"
296 depends on FIT_SIGNATURE
299 This option sets a max size in bytes for verified FIT uImages.
300 A sane value of 256MB protects corrupted DTB structures from overlapping
301 device memory. Assure this size does not extend past expected storage
304 config FIT_ENABLE_RSASSA_PSS_SUPPORT
305 bool "Support rsassa-pss signature scheme of FIT image contents"
306 depends on FIT_SIGNATURE
309 Enable this to support the pss padding algorithm as described
310 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
313 bool "Show verbose messages when FIT images fail"
315 Generally a system will have valid FIT images so debug messages
316 are a waste of code space. If you are debugging your images then
317 you can enable this option to get more verbose information about
320 config FIT_BEST_MATCH
321 bool "Select the best match for the kernel device tree"
323 When no configuration is explicitly selected, default to the
324 one whose fdt's compatibility field best matches that of
325 U-Boot itself. A match is considered "best" if it matches the
326 most specific compatibility entry of U-Boot's fdt's root node.
327 The order of entries in the configuration's fdt is ignored.
329 config FIT_IMAGE_POST_PROCESS
330 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
331 depends on TI_SECURE_DEVICE
333 Allows doing any sort of manipulation to blobs after they got extracted
334 from FIT images like stripping off headers or modifying the size of the
335 blob, verification, authentication, decryption etc. in a platform or
336 board specific way. In order to use this feature a platform or board-
337 specific implementation of board_fit_image_post_process() must be
338 provided. Also, anything done during this post-processing step would
339 need to be comprehended in how the images were prepared before being
340 injected into the FIT creation (i.e. the blobs would have been pre-
341 processed before being added to the FIT image).
346 bool "Support Flattened Image Tree within SPL"
351 bool "Support FIT printing within SPL"
354 Support printing the content of the fitImage in a verbose manner in SPL.
356 config SPL_FIT_SIGNATURE
357 bool "Enable signature verification of FIT firmware within SPL"
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_LOAD_FIT_FULL
374 bool "Enable SPL loading U-Boot as a FIT"
377 Normally with the SPL framework a legacy image is generated as part
378 of the build. This contains U-Boot along with information as to
379 where it should be loaded. This option instead enables generation
380 of a FIT (Flat Image Tree) which provides more flexibility. In
381 particular it can handle selecting from multiple device tree
382 and passing the correct one to U-Boot.
384 config SPL_FIT_IMAGE_POST_PROCESS
385 bool "Enable post-processing of FIT artifacts after loading by the SPL"
386 depends on SPL_LOAD_FIT
388 Allows doing any sort of manipulation to blobs after they got extracted
389 from the U-Boot FIT image like stripping off headers or modifying the
390 size of the blob, verification, authentication, decryption etc. in a
391 platform or board specific way. In order to use this feature a platform
392 or board-specific implementation of board_fit_image_post_process() must
393 be provided. Also, anything done during this post-processing step would
394 need to be comprehended in how the images were prepared before being
395 injected into the FIT creation (i.e. the blobs would have been pre-
396 processed before being added to the FIT image).
398 config SPL_FIT_SOURCE
399 string ".its source file for U-Boot FIT image"
402 Specifies a (platform specific) FIT source file to generate the
403 U-Boot FIT image. This could specify further image to load and/or
406 config SPL_FIT_GENERATOR
407 string ".its file generator script for U-Boot FIT image"
409 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
411 Specifies a (platform specific) script file to generate the FIT
412 source file used to build the U-Boot FIT image file. This gets
413 passed a list of supported device tree file stub names to
414 include in the generated image.
420 config IMAGE_FORMAT_LEGACY
421 bool "Enable support for the legacy image format"
422 default y if !FIT_SIGNATURE
424 This option enables the legacy image format. It is enabled by
425 default for backward compatibility, unless FIT_SIGNATURE is
426 set where it is disabled so that unsigned images cannot be
427 loaded. If a board needs the legacy image format support in this
428 case, enable it here.
430 config OF_BOARD_SETUP
431 bool "Set up board-specific details in device tree before boot"
434 This causes U-Boot to call ft_board_setup() before booting into
435 the Operating System. This function can set up various
436 board-specific information in the device tree for use by the OS.
437 The device tree is then passed to the OS.
439 config OF_SYSTEM_SETUP
440 bool "Set up system-specific details in device tree before boot"
443 This causes U-Boot to call ft_system_setup() before booting into
444 the Operating System. This function can set up various
445 system-specific information in the device tree for use by the OS.
446 The device tree is then passed to the OS.
448 config OF_STDOUT_VIA_ALIAS
449 bool "Update the device-tree stdout alias from U-Boot"
452 This uses U-Boot's serial alias from the aliases node to update
453 the device tree passed to the OS. The "linux,stdout-path" property
454 in the chosen node is set to point to the correct serial node.
455 This option currently references CONFIG_CONS_INDEX, which is
456 incorrect when used with device tree as this option does not
457 exist / should not be used.
459 config SYS_EXTRA_OPTIONS
460 string "Extra Options (DEPRECATED)"
462 The old configuration infrastructure (= mkconfig + boards.cfg)
463 provided the extra options field. If you have something like
464 "HAS_BAR,BAZ=64", the optional options
466 #define CONFIG_BAZ 64
467 will be defined in include/config.h.
468 This option was prepared for the smooth migration from the old
469 configuration to Kconfig. Since this option will be removed sometime,
470 new boards should not use this option.
473 depends on !NIOS2 && !XTENSA
475 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
476 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
477 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
478 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
481 The address in memory that U-Boot will be running from, initially.
486 depends on ARC || ARCH_SUNXI
487 int "CPU clock frequency"
489 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
491 config ARCH_FIXUP_FDT_MEMORY
492 bool "Enable arch_fixup_memory_banks() call"
495 Enable FDT memory map syncup before OS boot. This feature can be
496 used for booting OS with different memory setup where the part of
497 the memory location should be used for different purpose.
499 endmenu # Boot images
503 source "common/Kconfig"
507 source "disk/Kconfig"
515 source "drivers/Kconfig"
521 source "test/Kconfig"