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.
62 config DISTRO_DEFAULTS
63 bool "Select defaults suitable for booting general purpose Linux distributions"
64 default y if ARCH_SUNXI || TEGRA
65 default y if ARCH_LS2080A
66 default y if ARCH_MESON
67 default y if ARCH_ROCKCHIP
70 select CMD_BOOTZ if ARM && !ARM64
71 select CMD_BOOTI if ARM64
72 select CMD_DHCP if NET
79 select CMD_PING if NET
80 select CMD_PART if PARTITIONS
82 select BOOTP_BOOTPATH if NET
83 select BOOTP_DNS if NET
84 select BOOTP_GATEWAY if NET
85 select BOOTP_HOSTNAME if NET
86 select BOOTP_PXE if NET
87 select BOOTP_SUBNETMASK if NET
88 select CMDLINE_EDITING
91 select SUPPORT_RAW_INITRD
92 select ENV_VARS_UBOOT_CONFIG
94 Select this to enable various options and commands which are suitable
95 for building u-boot for booting general purpose Linux distributions.
97 config ENV_VARS_UBOOT_CONFIG
98 bool "Add arch, board, vendor and soc variables to default environment"
100 Define this in order to add variables describing the
101 U-Boot build configuration to the default environment.
102 These will be named arch, cpu, board, vendor, and soc.
103 Enabling this option will cause the following to be defined:
110 config SYS_BOOT_GET_CMDLINE
111 bool "Enable kernel command line setup"
113 Enables allocating and saving kernel cmdline in space between
114 "bootm_low" and "bootm_low" + BOOTMAPSZ.
116 config SYS_BOOT_GET_KBD
117 bool "Enable kernel board information setup"
119 Enables allocating and saving a kernel copy of the bd_info in
120 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
123 bool "Enable malloc() pool before relocation"
126 Before relocation, memory is very limited on many platforms. Still,
127 we can provide a small malloc() pool if needed. Driver model in
128 particular needs this to operate, so that it can allocate the
129 initial serial device and any others that are needed.
131 config SYS_MALLOC_F_LEN
132 hex "Size of malloc() pool before relocation"
133 depends on SYS_MALLOC_F
136 Before relocation, memory is very limited on many platforms. Still,
137 we can provide a small malloc() pool if needed. Driver model in
138 particular needs this to operate, so that it can allocate the
139 initial serial device and any others that are needed.
141 config SPL_SYS_MALLOC_F_LEN
142 hex "Size of malloc() pool in SPL before relocation"
143 depends on SYS_MALLOC_F
144 default SYS_MALLOC_F_LEN
146 Before relocation, memory is very limited on many platforms. Still,
147 we can provide a small malloc() pool if needed. Driver model in
148 particular needs this to operate, so that it can allocate the
149 initial serial device and any others that are needed.
151 config TPL_SYS_MALLOC_F_LEN
152 hex "Size of malloc() pool in TPL before relocation"
153 depends on SYS_MALLOC_F
154 default SYS_MALLOC_F_LEN
156 Before relocation, memory is very limited on many platforms. Still,
157 we can provide a small malloc() pool if needed. Driver model in
158 particular needs this to operate, so that it can allocate the
159 initial serial device and any others that are needed.
162 bool "Configure standard U-Boot features (expert users)"
165 This option allows certain base U-Boot options and settings
166 to be disabled or tweaked. This is for specialized
167 environments which can tolerate a "non-standard" U-Boot.
168 Use this only if you really know what you are doing.
171 config SYS_MALLOC_CLEAR_ON_INIT
172 bool "Init with zeros the memory reserved for malloc (slow)"
175 This setting is enabled by default. The reserved malloc
176 memory is initialized with zeros, so first malloc calls
177 will return the pointer to the zeroed memory. But this
180 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
181 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
182 Then the boot time can be significantly reduced.
184 When disabling this, please check if malloc calls, maybe
185 should be replaced by calloc - if one expects zeroed memory.
188 bool "Enable debug information for tools"
190 Enable generation of debug information for tools such as mkimage.
191 This can be used for debugging purposes. With debug information
192 it is possible to set breakpoints on particular lines, single-step
193 debug through the source code, etc.
198 bool "64bit physical address support"
200 Say Y here to support 64bit physical memory address.
201 This can be used not only for 64bit SoCs, but also for
202 large physical address extention on 32bit SoCs.
205 bool "Build U-Boot as BIOS replacement"
208 This option allows to build a ROM version of U-Boot.
209 The build process generally requires several binary blobs
210 which are not shipped in the U-Boot source tree.
211 Please, see doc/README.x86 for details.
213 endmenu # General setup
217 config ANDROID_BOOT_IMAGE
218 bool "Enable support for Android Boot Images"
219 default y if FASTBOOT
221 This enables support for booting images which use the Android
225 bool "Support Flattened Image Tree"
229 This option allows you to boot the new uImage structure,
230 Flattened Image Tree. FIT is formally a FDT, which can include
231 images of various types (kernel, FDT blob, ramdisk, etc.)
232 in a single blob. To boot this new uImage structure,
233 pass the address of the blob to the "bootm" command.
234 FIT is very flexible, supporting compression, multiple images,
235 multiple configurations, verification through hashing and also
236 verified boot (secure boot using RSA).
240 config FIT_ENABLE_SHA256_SUPPORT
241 bool "Support SHA256 checksum of FIT image contents"
245 Enable this to support SHA256 checksum of FIT image contents. A
246 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
247 the image contents have not been corrupted. SHA256 is recommended
248 for use in secure applications since (as at 2016) there is no known
249 feasible attack that could produce a 'collision' with differing
250 input data. Use this for the highest security. Note that only the
251 SHA256 variant is supported: SHA512 and others are not currently
255 bool "Enable signature verification of FIT uImages"
259 This option enables signature verification of FIT uImages,
260 using a hash signed and verified using RSA. If
261 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
262 hashing is available using hardware, then the RSA library will use
263 it. See doc/uImage.FIT/signature.txt for more details.
265 WARNING: When relying on signed FIT images with a required signature
266 check the legacy image format is disabled by default, so that
267 unsigned images cannot be loaded. If a board needs the legacy image
268 format support in this case, enable it using
269 CONFIG_IMAGE_FORMAT_LEGACY.
272 bool "Show verbose messages when FIT images fail"
274 Generally a system will have valid FIT images so debug messages
275 are a waste of code space. If you are debugging your images then
276 you can enable this option to get more verbose information about
279 config FIT_BEST_MATCH
280 bool "Select the best match for the kernel device tree"
282 When no configuration is explicitly selected, default to the
283 one whose fdt's compatibility field best matches that of
284 U-Boot itself. A match is considered "best" if it matches the
285 most specific compatibility entry of U-Boot's fdt's root node.
286 The order of entries in the configuration's fdt is ignored.
288 config FIT_IMAGE_POST_PROCESS
289 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
290 depends on TI_SECURE_DEVICE
292 Allows doing any sort of manipulation to blobs after they got extracted
293 from FIT images like stripping off headers or modifying the size of the
294 blob, verification, authentication, decryption etc. in a platform or
295 board specific way. In order to use this feature a platform or board-
296 specific implementation of board_fit_image_post_process() must be
297 provided. Also, anything done during this post-processing step would
298 need to be comprehended in how the images were prepared before being
299 injected into the FIT creation (i.e. the blobs would have been pre-
300 processed before being added to the FIT image).
305 bool "Support Flattened Image Tree within SPL"
309 config SPL_FIT_SIGNATURE
310 bool "Enable signature verification of FIT firmware within SPL"
316 bool "Enable SPL loading U-Boot as a FIT"
319 Normally with the SPL framework a legacy image is generated as part
320 of the build. This contains U-Boot along with information as to
321 where it should be loaded. This option instead enables generation
322 of a FIT (Flat Image Tree) which provides more flexibility. In
323 particular it can handle selecting from multiple device tree
324 and passing the correct one to U-Boot.
326 config SPL_FIT_IMAGE_POST_PROCESS
327 bool "Enable post-processing of FIT artifacts after loading by the SPL"
328 depends on SPL_LOAD_FIT
330 Allows doing any sort of manipulation to blobs after they got extracted
331 from the U-Boot FIT image like stripping off headers or modifying the
332 size of the blob, verification, authentication, decryption etc. in a
333 platform or board specific way. In order to use this feature a platform
334 or board-specific implementation of board_fit_image_post_process() must
335 be provided. Also, anything done during this post-processing step would
336 need to be comprehended in how the images were prepared before being
337 injected into the FIT creation (i.e. the blobs would have been pre-
338 processed before being added to the FIT image).
340 config SPL_FIT_SOURCE
341 string ".its source file for U-Boot FIT image"
344 Specifies a (platform specific) FIT source file to generate the
345 U-Boot FIT image. This could specify further image to load and/or
348 config SPL_FIT_GENERATOR
349 string ".its file generator script for U-Boot FIT image"
351 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
353 Specifies a (platform specific) script file to generate the FIT
354 source file used to build the U-Boot FIT image file. This gets
355 passed a list of supported device tree file stub names to
356 include in the generated image.
362 config OF_BOARD_SETUP
363 bool "Set up board-specific details in device tree before boot"
366 This causes U-Boot to call ft_board_setup() before booting into
367 the Operating System. This function can set up various
368 board-specific information in the device tree for use by the OS.
369 The device tree is then passed to the OS.
371 config OF_SYSTEM_SETUP
372 bool "Set up system-specific details in device tree before boot"
375 This causes U-Boot to call ft_system_setup() before booting into
376 the Operating System. This function can set up various
377 system-specific information in the device tree for use by the OS.
378 The device tree is then passed to the OS.
380 config OF_STDOUT_VIA_ALIAS
381 bool "Update the device-tree stdout alias from U-Boot"
384 This uses U-Boot's serial alias from the aliases node to update
385 the device tree passed to the OS. The "linux,stdout-path" property
386 in the chosen node is set to point to the correct serial node.
387 This option currently references CONFIG_CONS_INDEX, which is
388 incorrect when used with device tree as this option does not
389 exist / should not be used.
391 config SYS_EXTRA_OPTIONS
392 string "Extra Options (DEPRECATED)"
394 The old configuration infrastructure (= mkconfig + boards.cfg)
395 provided the extra options field. If you have something like
396 "HAS_BAR,BAZ=64", the optional options
398 #define CONFIG_BAZ 64
399 will be defined in include/config.h.
400 This option was prepared for the smooth migration from the old
401 configuration to Kconfig. Since this option will be removed sometime,
402 new boards should not use this option.
405 depends on !NIOS2 && !XTENSA
407 default 0x80800000 if ARCH_OMAP2PLUS
410 The address in memory that U-Boot will be running from, initially.
415 depends on ARC || ARCH_SUNXI
416 int "CPU clock frequency"
418 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
420 config ARCH_FIXUP_FDT_MEMORY
421 bool "Enable arch_fixup_memory_banks() call"
424 Enable FDT memory map syncup before OS boot. This feature can be
425 used for booting OS with different memory setup where the part of
426 the memory location should be used for different purpose.
428 endmenu # Boot images
432 source "common/Kconfig"
436 source "disk/Kconfig"
444 source "drivers/Kconfig"
450 source "test/Kconfig"
projects / u-boot / blob