]> git.ipfire.org Git - thirdparty/u-boot.git/blob - Kconfig
709912e1340129db922ea414a0653f332b397bbb
[thirdparty/u-boot.git] / Kconfig
1 #
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.
5 #
6 mainmenu "U-Boot $UBOOTVERSION Configuration"
7
8 config UBOOTVERSION
9 string
10 option env="UBOOTVERSION"
11
12 # Allow defaults in arch-specific code to override any given here
13 source "arch/Kconfig"
14
15 menu "General setup"
16
17 config BROKEN
18 bool
19 help
20 This option cannot be enabled. It is used as dependency
21 for broken and incomplete features.
22
23 config LOCALVERSION
24 string "Local version - append to U-Boot release"
25 help
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.
32
33 config LOCALVERSION_AUTO
34 bool "Automatically append version information to the version string"
35 default y
36 help
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
39 top of tree revision.
40
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.
45
46 (The actual string used here is the first eight characters produced
47 by running the command:
48
49 $ git rev-parse --verify HEAD
50
51 which is done within the script "scripts/setlocalversion".)
52
53 config CC_OPTIMIZE_FOR_SIZE
54 bool "Optimize for size"
55 default y
56 help
57 Enabling this option will pass "-Os" instead of "-O2" to gcc
58 resulting in a smaller U-Boot image.
59
60 This option is enabled by default for U-Boot.
61
62 config CC_COVERAGE
63 bool "Enable code coverage analysis"
64 depends on SANDBOX
65 help
66 Enabling this option will pass "--coverage" to gcc to compile
67 and link code instrumented for coverage analysis.
68
69 config DISTRO_DEFAULTS
70 bool "Select defaults suitable for booting general purpose Linux distributions"
71 select AUTO_COMPLETE
72 select CMDLINE_EDITING
73 select CMD_BOOTI if ARM64
74 select CMD_BOOTZ if ARM && !ARM64
75 select CMD_DHCP if CMD_NET
76 select CMD_ENV_EXISTS
77 select CMD_EXT2
78 select CMD_EXT4
79 select CMD_FAT
80 select CMD_FS_GENERIC
81 select CMD_PART if PARTITIONS
82 select CMD_PING if CMD_NET
83 select CMD_PXE if NET
84 select ENV_VARS_UBOOT_CONFIG
85 select HUSH_PARSER
86 select SUPPORT_RAW_INITRD
87 select SYS_LONGHELP
88 imply CMD_MII if NET
89 imply USB_STORAGE
90 imply USE_BOOTCOMMAND
91 help
92 Select this to enable various options and commands which are suitable
93 for building u-boot for booting general purpose Linux distributions.
94
95 config ENV_VARS_UBOOT_CONFIG
96 bool "Add arch, board, vendor and soc variables to default environment"
97 help
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:
102 - CONFIG_SYS_ARCH
103 - CONFIG_SYS_CPU
104 - CONFIG_SYS_BOARD
105 - CONFIG_SYS_VENDOR
106 - CONFIG_SYS_SOC
107
108 config NR_DRAM_BANKS
109 int "Number of DRAM banks"
110 default 4
111 help
112 This defines the number of DRAM banks.
113
114 config SYS_BOOT_GET_CMDLINE
115 bool "Enable kernel command line setup"
116 help
117 Enables allocating and saving kernel cmdline in space between
118 "bootm_low" and "bootm_low" + BOOTMAPSZ.
119
120 config SYS_BOOT_GET_KBD
121 bool "Enable kernel board information setup"
122 help
123 Enables allocating and saving a kernel copy of the bd_info in
124 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
125
126 config SYS_MALLOC_F
127 bool "Enable malloc() pool before relocation"
128 default y if DM
129
130 help
131 Before relocation, memory is very limited on many platforms. Still,
132 we can provide a small malloc() pool if needed. Driver model in
133 particular needs this to operate, so that it can allocate the
134 initial serial device and any others that are needed.
135
136 config SYS_MALLOC_F_LEN
137 hex "Size of malloc() pool before relocation"
138 depends on SYS_MALLOC_F
139 default 0x1000 if AM33XX
140 default 0x2800 if SANDBOX
141 default 0x400
142 help
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.
147
148 config SYS_MALLOC_LEN
149 hex "Define memory for Dynamic allocation"
150 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP
151 help
152 This defines memory to be allocated for Dynamic allocation
153 TODO: Use for other architectures
154
155 config SPL_SYS_MALLOC_F_LEN
156 hex "Size of malloc() pool in SPL before relocation"
157 depends on SYS_MALLOC_F
158 default 0x2800 if RCAR_GEN3
159 default SYS_MALLOC_F_LEN
160 help
161 Before relocation, memory is very limited on many platforms. Still,
162 we can provide a small malloc() pool if needed. Driver model in
163 particular needs this to operate, so that it can allocate the
164 initial serial device and any others that are needed.
165
166 config TPL_SYS_MALLOC_F_LEN
167 hex "Size of malloc() pool in TPL before relocation"
168 depends on SYS_MALLOC_F
169 default SYS_MALLOC_F_LEN
170 help
171 Before relocation, memory is very limited on many platforms. Still,
172 we can provide a small malloc() pool if needed. Driver model in
173 particular needs this to operate, so that it can allocate the
174 initial serial device and any others that are needed.
175
176 config SPL_SIZE_LIMIT
177 int "Maximum size of SPL image"
178 depends on SPL
179 default 0
180 help
181 Specifies the maximum length of the U-Boot SPL image.
182 If this value is zero, it is ignored.
183
184 menuconfig EXPERT
185 bool "Configure standard U-Boot features (expert users)"
186 default y
187 help
188 This option allows certain base U-Boot options and settings
189 to be disabled or tweaked. This is for specialized
190 environments which can tolerate a "non-standard" U-Boot.
191 Use this only if you really know what you are doing.
192
193 if EXPERT
194 config SYS_MALLOC_CLEAR_ON_INIT
195 bool "Init with zeros the memory reserved for malloc (slow)"
196 default y
197 help
198 This setting is enabled by default. The reserved malloc
199 memory is initialized with zeros, so first malloc calls
200 will return the pointer to the zeroed memory. But this
201 slows the boot time.
202
203 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
204 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
205 Then the boot time can be significantly reduced.
206 Warning:
207 When disabling this, please check if malloc calls, maybe
208 should be replaced by calloc - if one expects zeroed memory.
209
210 config TOOLS_DEBUG
211 bool "Enable debug information for tools"
212 help
213 Enable generation of debug information for tools such as mkimage.
214 This can be used for debugging purposes. With debug information
215 it is possible to set breakpoints on particular lines, single-step
216 debug through the source code, etc.
217
218 endif # EXPERT
219
220 config PHYS_64BIT
221 bool "64bit physical address support"
222 help
223 Say Y here to support 64bit physical memory address.
224 This can be used not only for 64bit SoCs, but also for
225 large physical address extension on 32bit SoCs.
226
227 config BUILD_ROM
228 bool "Build U-Boot as BIOS replacement"
229 depends on X86
230 help
231 This option allows to build a ROM version of U-Boot.
232 The build process generally requires several binary blobs
233 which are not shipped in the U-Boot source tree.
234 Please, see doc/README.x86 for details.
235
236 config SPL_IMAGE
237 string "SPL image used in the combined SPL+U-Boot image"
238 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
239 default "spl/u-boot-spl.bin"
240 help
241 Select the SPL build target that shall be generated by the SPL
242 build process (default spl/u-boot-spl.bin). This image will be
243 used to generate a combined image with SPL and main U-Boot
244 proper as one single image.
245
246 config BUILD_TARGET
247 string "Build target special images"
248 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
249 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
250 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
251 default "u-boot-elf.srec" if RCAR_GEN3
252 default "u-boot.itb" if SPL_LOAD_FIT && ARCH_SUNXI
253 default "u-boot.kwb" if KIRKWOOD
254 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
255 help
256 Some SoCs need special image types (e.g. U-Boot binary
257 with a special header) as build targets. By defining
258 CONFIG_BUILD_TARGET in the SoC / board header, this
259 special image will be automatically built upon calling
260 make / buildman.
261
262 endmenu # General setup
263
264 menu "Boot images"
265
266 config ANDROID_BOOT_IMAGE
267 bool "Enable support for Android Boot Images"
268 default y if FASTBOOT
269 help
270 This enables support for booting images which use the Android
271 image format header.
272
273 config FIT
274 bool "Support Flattened Image Tree"
275 select MD5
276 select SHA1
277 help
278 This option allows you to boot the new uImage structure,
279 Flattened Image Tree. FIT is formally a FDT, which can include
280 images of various types (kernel, FDT blob, ramdisk, etc.)
281 in a single blob. To boot this new uImage structure,
282 pass the address of the blob to the "bootm" command.
283 FIT is very flexible, supporting compression, multiple images,
284 multiple configurations, verification through hashing and also
285 verified boot (secure boot using RSA).
286
287 if FIT
288
289 config FIT_EXTERNAL_OFFSET
290 hex "FIT external data offset"
291 default 0x0
292 help
293 This specifies a data offset in fit image.
294 The offset is from data payload offset to the beginning of
295 fit image header. When specifies a offset, specific data
296 could be put in the hole between data payload and fit image
297 header, such as CSF data on i.MX platform.
298
299 config FIT_ENABLE_SHA256_SUPPORT
300 bool "Support SHA256 checksum of FIT image contents"
301 default y
302 select SHA256
303 help
304 Enable this to support SHA256 checksum of FIT image contents. A
305 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
306 the image contents have not been corrupted. SHA256 is recommended
307 for use in secure applications since (as at 2016) there is no known
308 feasible attack that could produce a 'collision' with differing
309 input data. Use this for the highest security. Note that only the
310 SHA256 variant is supported: SHA512 and others are not currently
311 supported in U-Boot.
312
313 config FIT_SIGNATURE
314 bool "Enable signature verification of FIT uImages"
315 depends on DM
316 select HASH
317 select RSA
318 help
319 This option enables signature verification of FIT uImages,
320 using a hash signed and verified using RSA. If
321 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
322 hashing is available using hardware, then the RSA library will use
323 it. See doc/uImage.FIT/signature.txt for more details.
324
325 WARNING: When relying on signed FIT images with a required signature
326 check the legacy image format is disabled by default, so that
327 unsigned images cannot be loaded. If a board needs the legacy image
328 format support in this case, enable it using
329 CONFIG_IMAGE_FORMAT_LEGACY.
330
331 config FIT_SIGNATURE_MAX_SIZE
332 hex "Max size of signed FIT structures"
333 depends on FIT_SIGNATURE
334 default 0x10000000
335 help
336 This option sets a max size in bytes for verified FIT uImages.
337 A sane value of 256MB protects corrupted DTB structures from overlapping
338 device memory. Assure this size does not extend past expected storage
339 space.
340
341 config FIT_ENABLE_RSASSA_PSS_SUPPORT
342 bool "Support rsassa-pss signature scheme of FIT image contents"
343 depends on FIT_SIGNATURE
344 default n
345 help
346 Enable this to support the pss padding algorithm as described
347 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
348
349 config FIT_VERBOSE
350 bool "Show verbose messages when FIT images fail"
351 help
352 Generally a system will have valid FIT images so debug messages
353 are a waste of code space. If you are debugging your images then
354 you can enable this option to get more verbose information about
355 failures.
356
357 config FIT_BEST_MATCH
358 bool "Select the best match for the kernel device tree"
359 help
360 When no configuration is explicitly selected, default to the
361 one whose fdt's compatibility field best matches that of
362 U-Boot itself. A match is considered "best" if it matches the
363 most specific compatibility entry of U-Boot's fdt's root node.
364 The order of entries in the configuration's fdt is ignored.
365
366 config FIT_IMAGE_POST_PROCESS
367 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
368 depends on TI_SECURE_DEVICE
369 help
370 Allows doing any sort of manipulation to blobs after they got extracted
371 from FIT images like stripping off headers or modifying the size of the
372 blob, verification, authentication, decryption etc. in a platform or
373 board specific way. In order to use this feature a platform or board-
374 specific implementation of board_fit_image_post_process() must be
375 provided. Also, anything done during this post-processing step would
376 need to be comprehended in how the images were prepared before being
377 injected into the FIT creation (i.e. the blobs would have been pre-
378 processed before being added to the FIT image).
379
380 if SPL
381
382 config SPL_FIT
383 bool "Support Flattened Image Tree within SPL"
384 depends on SPL
385 select SPL_OF_LIBFDT
386
387 config SPL_FIT_PRINT
388 bool "Support FIT printing within SPL"
389 depends on SPL_FIT
390 help
391 Support printing the content of the fitImage in a verbose manner in SPL.
392
393 config SPL_FIT_SIGNATURE
394 bool "Enable signature verification of FIT firmware within SPL"
395 depends on SPL_DM
396 select SPL_FIT
397 select SPL_RSA
398
399 config SPL_LOAD_FIT
400 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
401 select SPL_FIT
402 help
403 Normally with the SPL framework a legacy image is generated as part
404 of the build. This contains U-Boot along with information as to
405 where it should be loaded. This option instead enables generation
406 of a FIT (Flat Image Tree) which provides more flexibility. In
407 particular it can handle selecting from multiple device tree
408 and passing the correct one to U-Boot.
409
410 config SPL_LOAD_FIT_FULL
411 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
412 select SPL_FIT
413 help
414 Normally with the SPL framework a legacy image is generated as part
415 of the build. This contains U-Boot along with information as to
416 where it should be loaded. This option instead enables generation
417 of a FIT (Flat Image Tree) which provides more flexibility. In
418 particular it can handle selecting from multiple device tree
419 and passing the correct one to U-Boot.
420
421 config SPL_FIT_IMAGE_POST_PROCESS
422 bool "Enable post-processing of FIT artifacts after loading by the SPL"
423 depends on SPL_LOAD_FIT
424 help
425 Allows doing any sort of manipulation to blobs after they got extracted
426 from the U-Boot FIT image like stripping off headers or modifying the
427 size of the blob, verification, authentication, decryption etc. in a
428 platform or board specific way. In order to use this feature a platform
429 or board-specific implementation of board_fit_image_post_process() must
430 be provided. Also, anything done during this post-processing step would
431 need to be comprehended in how the images were prepared before being
432 injected into the FIT creation (i.e. the blobs would have been pre-
433 processed before being added to the FIT image).
434
435 config SPL_FIT_SOURCE
436 string ".its source file for U-Boot FIT image"
437 depends on SPL_FIT
438 help
439 Specifies a (platform specific) FIT source file to generate the
440 U-Boot FIT image. This could specify further image to load and/or
441 execute.
442
443 config SPL_FIT_GENERATOR
444 string ".its file generator script for U-Boot FIT image"
445 depends on SPL_FIT
446 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
447 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
448 help
449 Specifies a (platform specific) script file to generate the FIT
450 source file used to build the U-Boot FIT image file. This gets
451 passed a list of supported device tree file stub names to
452 include in the generated image.
453
454 endif # SPL
455
456 endif # FIT
457
458 config IMAGE_FORMAT_LEGACY
459 bool "Enable support for the legacy image format"
460 default y if !FIT_SIGNATURE
461 help
462 This option enables the legacy image format. It is enabled by
463 default for backward compatibility, unless FIT_SIGNATURE is
464 set where it is disabled so that unsigned images cannot be
465 loaded. If a board needs the legacy image format support in this
466 case, enable it here.
467
468 config OF_BOARD_SETUP
469 bool "Set up board-specific details in device tree before boot"
470 depends on OF_LIBFDT
471 help
472 This causes U-Boot to call ft_board_setup() before booting into
473 the Operating System. This function can set up various
474 board-specific information in the device tree for use by the OS.
475 The device tree is then passed to the OS.
476
477 config OF_SYSTEM_SETUP
478 bool "Set up system-specific details in device tree before boot"
479 depends on OF_LIBFDT
480 help
481 This causes U-Boot to call ft_system_setup() before booting into
482 the Operating System. This function can set up various
483 system-specific information in the device tree for use by the OS.
484 The device tree is then passed to the OS.
485
486 config OF_STDOUT_VIA_ALIAS
487 bool "Update the device-tree stdout alias from U-Boot"
488 depends on OF_LIBFDT
489 help
490 This uses U-Boot's serial alias from the aliases node to update
491 the device tree passed to the OS. The "linux,stdout-path" property
492 in the chosen node is set to point to the correct serial node.
493 This option currently references CONFIG_CONS_INDEX, which is
494 incorrect when used with device tree as this option does not
495 exist / should not be used.
496
497 config SYS_EXTRA_OPTIONS
498 string "Extra Options (DEPRECATED)"
499 help
500 The old configuration infrastructure (= mkconfig + boards.cfg)
501 provided the extra options field. If you have something like
502 "HAS_BAR,BAZ=64", the optional options
503 #define CONFIG_HAS
504 #define CONFIG_BAZ 64
505 will be defined in include/config.h.
506 This option was prepared for the smooth migration from the old
507 configuration to Kconfig. Since this option will be removed sometime,
508 new boards should not use this option.
509
510 config SYS_TEXT_BASE
511 depends on !NIOS2 && !XTENSA
512 depends on !EFI_APP
513 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
514 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
515 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
516 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
517 hex "Text Base"
518 help
519 The address in memory that U-Boot will be running from, initially.
520
521
522
523 config SYS_CLK_FREQ
524 depends on ARC || ARCH_SUNXI || MPC83xx
525 int "CPU clock frequency"
526 help
527 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
528
529 config ARCH_FIXUP_FDT_MEMORY
530 bool "Enable arch_fixup_memory_banks() call"
531 default y
532 help
533 Enable FDT memory map syncup before OS boot. This feature can be
534 used for booting OS with different memory setup where the part of
535 the memory location should be used for different purpose.
536
537 endmenu # Boot images
538
539 source "api/Kconfig"
540
541 source "common/Kconfig"
542
543 source "cmd/Kconfig"
544
545 source "disk/Kconfig"
546
547 source "dts/Kconfig"
548
549 source "env/Kconfig"
550
551 source "net/Kconfig"
552
553 source "drivers/Kconfig"
554
555 source "fs/Kconfig"
556
557 source "lib/Kconfig"
558
559 source "test/Kconfig"