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"
71 default y if ARCH_SUNXI || TEGRA
72 default y if ARCH_LS2080A
73 default y if ARCH_MESON
74 default y if ARCH_ROCKCHIP
77 select CMD_BOOTZ if ARM && !ARM64
78 select CMD_BOOTI if ARM64
79 select CMD_DHCP if NET && CMD_NET
80 select CMD_PXE if NET && CMD_NET
86 select CMD_PING if NET
87 select CMD_PART if PARTITIONS
89 select BOOTP_BOOTPATH if NET && CMD_NET
90 select BOOTP_DNS if NET && CMD_NET
91 select BOOTP_GATEWAY if NET && CMD_NET
92 select BOOTP_HOSTNAME if NET && CMD_NET
93 select BOOTP_PXE if NET && CMD_NET
94 select BOOTP_SUBNETMASK if NET && CMD_NET
95 select CMDLINE_EDITING
98 select SUPPORT_RAW_INITRD
99 select ENV_VARS_UBOOT_CONFIG
101 Select this to enable various options and commands which are suitable
102 for building u-boot for booting general purpose Linux distributions.
104 config ENV_VARS_UBOOT_CONFIG
105 bool "Add arch, board, vendor and soc variables to default environment"
107 Define this in order to add variables describing the
108 U-Boot build configuration to the default environment.
109 These will be named arch, cpu, board, vendor, and soc.
110 Enabling this option will cause the following to be defined:
117 config SYS_BOOT_GET_CMDLINE
118 bool "Enable kernel command line setup"
120 Enables allocating and saving kernel cmdline in space between
121 "bootm_low" and "bootm_low" + BOOTMAPSZ.
123 config SYS_BOOT_GET_KBD
124 bool "Enable kernel board information setup"
126 Enables allocating and saving a kernel copy of the bd_info in
127 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
130 bool "Enable malloc() pool before relocation"
133 Before relocation, memory is very limited on many platforms. Still,
134 we can provide a small malloc() pool if needed. Driver model in
135 particular needs this to operate, so that it can allocate the
136 initial serial device and any others that are needed.
138 config SYS_MALLOC_F_LEN
139 hex "Size of malloc() pool before relocation"
140 depends on SYS_MALLOC_F
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 SPL_SYS_MALLOC_F_LEN
149 hex "Size of malloc() pool in SPL before relocation"
150 depends on SYS_MALLOC_F
151 default SYS_MALLOC_F_LEN
153 Before relocation, memory is very limited on many platforms. Still,
154 we can provide a small malloc() pool if needed. Driver model in
155 particular needs this to operate, so that it can allocate the
156 initial serial device and any others that are needed.
158 config TPL_SYS_MALLOC_F_LEN
159 hex "Size of malloc() pool in TPL before relocation"
160 depends on SYS_MALLOC_F
161 default SYS_MALLOC_F_LEN
163 Before relocation, memory is very limited on many platforms. Still,
164 we can provide a small malloc() pool if needed. Driver model in
165 particular needs this to operate, so that it can allocate the
166 initial serial device and any others that are needed.
169 bool "Configure standard U-Boot features (expert users)"
172 This option allows certain base U-Boot options and settings
173 to be disabled or tweaked. This is for specialized
174 environments which can tolerate a "non-standard" U-Boot.
175 Use this only if you really know what you are doing.
178 config SYS_MALLOC_CLEAR_ON_INIT
179 bool "Init with zeros the memory reserved for malloc (slow)"
182 This setting is enabled by default. The reserved malloc
183 memory is initialized with zeros, so first malloc calls
184 will return the pointer to the zeroed memory. But this
187 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
188 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
189 Then the boot time can be significantly reduced.
191 When disabling this, please check if malloc calls, maybe
192 should be replaced by calloc - if one expects zeroed memory.
195 bool "Enable debug information for tools"
197 Enable generation of debug information for tools such as mkimage.
198 This can be used for debugging purposes. With debug information
199 it is possible to set breakpoints on particular lines, single-step
200 debug through the source code, etc.
205 bool "64bit physical address support"
207 Say Y here to support 64bit physical memory address.
208 This can be used not only for 64bit SoCs, but also for
209 large physical address extention on 32bit SoCs.
212 bool "Build U-Boot as BIOS replacement"
215 This option allows to build a ROM version of U-Boot.
216 The build process generally requires several binary blobs
217 which are not shipped in the U-Boot source tree.
218 Please, see doc/README.x86 for details.
220 endmenu # General setup
224 config ANDROID_BOOT_IMAGE
225 bool "Enable support for Android Boot Images"
226 default y if FASTBOOT
228 This enables support for booting images which use the Android
232 bool "Support Flattened Image Tree"
236 This option allows you to boot the new uImage structure,
237 Flattened Image Tree. FIT is formally a FDT, which can include
238 images of various types (kernel, FDT blob, ramdisk, etc.)
239 in a single blob. To boot this new uImage structure,
240 pass the address of the blob to the "bootm" command.
241 FIT is very flexible, supporting compression, multiple images,
242 multiple configurations, verification through hashing and also
243 verified boot (secure boot using RSA).
247 config FIT_ENABLE_SHA256_SUPPORT
248 bool "Support SHA256 checksum of FIT image contents"
252 Enable this to support SHA256 checksum of FIT image contents. A
253 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
254 the image contents have not been corrupted. SHA256 is recommended
255 for use in secure applications since (as at 2016) there is no known
256 feasible attack that could produce a 'collision' with differing
257 input data. Use this for the highest security. Note that only the
258 SHA256 variant is supported: SHA512 and others are not currently
262 bool "Enable signature verification of FIT uImages"
266 This option enables signature verification of FIT uImages,
267 using a hash signed and verified using RSA. If
268 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
269 hashing is available using hardware, then the RSA library will use
270 it. See doc/uImage.FIT/signature.txt for more details.
272 WARNING: When relying on signed FIT images with a required signature
273 check the legacy image format is disabled by default, so that
274 unsigned images cannot be loaded. If a board needs the legacy image
275 format support in this case, enable it using
276 CONFIG_IMAGE_FORMAT_LEGACY.
279 bool "Show verbose messages when FIT images fail"
281 Generally a system will have valid FIT images so debug messages
282 are a waste of code space. If you are debugging your images then
283 you can enable this option to get more verbose information about
286 config FIT_BEST_MATCH
287 bool "Select the best match for the kernel device tree"
289 When no configuration is explicitly selected, default to the
290 one whose fdt's compatibility field best matches that of
291 U-Boot itself. A match is considered "best" if it matches the
292 most specific compatibility entry of U-Boot's fdt's root node.
293 The order of entries in the configuration's fdt is ignored.
295 config FIT_IMAGE_POST_PROCESS
296 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
297 depends on TI_SECURE_DEVICE
299 Allows doing any sort of manipulation to blobs after they got extracted
300 from FIT images like stripping off headers or modifying the size of the
301 blob, verification, authentication, decryption etc. in a platform or
302 board specific way. In order to use this feature a platform or board-
303 specific implementation of board_fit_image_post_process() must be
304 provided. Also, anything done during this post-processing step would
305 need to be comprehended in how the images were prepared before being
306 injected into the FIT creation (i.e. the blobs would have been pre-
307 processed before being added to the FIT image).
312 bool "Support Flattened Image Tree within SPL"
316 config SPL_FIT_SIGNATURE
317 bool "Enable signature verification of FIT firmware within SPL"
323 bool "Enable SPL loading U-Boot as a FIT"
326 Normally with the SPL framework a legacy image is generated as part
327 of the build. This contains U-Boot along with information as to
328 where it should be loaded. This option instead enables generation
329 of a FIT (Flat Image Tree) which provides more flexibility. In
330 particular it can handle selecting from multiple device tree
331 and passing the correct one to U-Boot.
333 config SPL_FIT_IMAGE_POST_PROCESS
334 bool "Enable post-processing of FIT artifacts after loading by the SPL"
335 depends on SPL_LOAD_FIT
337 Allows doing any sort of manipulation to blobs after they got extracted
338 from the U-Boot FIT image like stripping off headers or modifying the
339 size of the blob, verification, authentication, decryption etc. in a
340 platform or board specific way. In order to use this feature a platform
341 or board-specific implementation of board_fit_image_post_process() must
342 be provided. Also, anything done during this post-processing step would
343 need to be comprehended in how the images were prepared before being
344 injected into the FIT creation (i.e. the blobs would have been pre-
345 processed before being added to the FIT image).
347 config SPL_FIT_SOURCE
348 string ".its source file for U-Boot FIT image"
351 Specifies a (platform specific) FIT source file to generate the
352 U-Boot FIT image. This could specify further image to load and/or
355 config SPL_FIT_GENERATOR
356 string ".its file generator script for U-Boot FIT image"
358 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
360 Specifies a (platform specific) script file to generate the FIT
361 source file used to build the U-Boot FIT image file. This gets
362 passed a list of supported device tree file stub names to
363 include in the generated image.
369 config OF_BOARD_SETUP
370 bool "Set up board-specific details in device tree before boot"
373 This causes U-Boot to call ft_board_setup() before booting into
374 the Operating System. This function can set up various
375 board-specific information in the device tree for use by the OS.
376 The device tree is then passed to the OS.
378 config OF_SYSTEM_SETUP
379 bool "Set up system-specific details in device tree before boot"
382 This causes U-Boot to call ft_system_setup() before booting into
383 the Operating System. This function can set up various
384 system-specific information in the device tree for use by the OS.
385 The device tree is then passed to the OS.
387 config OF_STDOUT_VIA_ALIAS
388 bool "Update the device-tree stdout alias from U-Boot"
391 This uses U-Boot's serial alias from the aliases node to update
392 the device tree passed to the OS. The "linux,stdout-path" property
393 in the chosen node is set to point to the correct serial node.
394 This option currently references CONFIG_CONS_INDEX, which is
395 incorrect when used with device tree as this option does not
396 exist / should not be used.
398 config SYS_EXTRA_OPTIONS
399 string "Extra Options (DEPRECATED)"
401 The old configuration infrastructure (= mkconfig + boards.cfg)
402 provided the extra options field. If you have something like
403 "HAS_BAR,BAZ=64", the optional options
405 #define CONFIG_BAZ 64
406 will be defined in include/config.h.
407 This option was prepared for the smooth migration from the old
408 configuration to Kconfig. Since this option will be removed sometime,
409 new boards should not use this option.
412 depends on !NIOS2 && !XTENSA
414 default 0x80800000 if ARCH_OMAP2PLUS
415 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
416 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
417 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
420 The address in memory that U-Boot will be running from, initially.
425 depends on ARC || ARCH_SUNXI
426 int "CPU clock frequency"
428 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
430 config ARCH_FIXUP_FDT_MEMORY
431 bool "Enable arch_fixup_memory_banks() call"
434 Enable FDT memory map syncup before OS boot. This feature can be
435 used for booting OS with different memory setup where the part of
436 the memory location should be used for different purpose.
438 endmenu # Boot images
442 source "common/Kconfig"
446 source "disk/Kconfig"
454 source "drivers/Kconfig"
460 source "test/Kconfig"
projects / u-boot / blob