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"
8 comment "Compiler: $(CC_VERSION_TEXT)"
10 source "scripts/Kconfig.include"
12 # Allow defaults in arch-specific code to override any given here
13 source "arch/Kconfig"
15 menu "General setup"
17 config BROKEN
18 bool
19 help
20 This option cannot be enabled. It is used as dependency
21 for broken and incomplete features.
23 config DEPRECATED
24 bool
25 help
26 This option cannot be enabled. It it used as a dependency for
27 code that relies on deprecated features that will be removed and
28 the conversion deadline has passed.
30 config LOCALVERSION
31 string "Local version - append to U-Boot release"
32 help
33 Append an extra string to the end of your U-Boot version.
34 This will show up in your boot log, for example.
35 The string you set here will be appended after the contents of
36 any files with a filename matching localversion* in your
37 object and source tree, in that order. Your total string can
38 be a maximum of 64 characters.
40 config LOCALVERSION_AUTO
41 bool "Automatically append version information to the version string"
42 default y
43 help
44 This will try to automatically determine if the current tree is a
45 release tree by looking for Git tags that belong to the current
46 top of tree revision.
48 A string of the format -gxxxxxxxx will be added to the localversion
49 if a Git-based tree is found. The string generated by this will be
50 appended after any matching localversion* files, and after the value
51 set in CONFIG_LOCALVERSION.
53 (The actual string used here is the first eight characters produced
54 by running the command:
56 $ git rev-parse --verify HEAD
58 which is done within the script "scripts/setlocalversion".)
60 config CC_OPTIMIZE_FOR_SIZE
61 bool "Optimize for size"
62 default y
63 help
64 Enabling this option will pass "-Os" instead of "-O2" to gcc
65 resulting in a smaller U-Boot image.
67 This option is enabled by default for U-Boot.
69 config OPTIMIZE_INLINING
70 bool "Allow compiler to uninline functions marked 'inline' in full U-Boot"
71 default n
72 help
73 This option determines if U-Boot forces gcc to inline the functions
74 developers have marked 'inline'. Doing so takes away freedom from gcc to
75 do what it thinks is best, which is desirable in some cases for size
76 reasons.
78 config SPL_OPTIMIZE_INLINING
79 bool "Allow compiler to uninline functions marked 'inline' in SPL"
80 depends on SPL
81 default n
82 help
83 This option determines if U-Boot forces gcc to inline the functions
84 developers have marked 'inline'. Doing so takes away freedom from gcc to
85 do what it thinks is best, which is desirable in some cases for size
86 reasons.
88 config TPL_OPTIMIZE_INLINING
89 bool "Allow compiler to uninline functions marked 'inline' in TPL"
90 depends on TPL
91 default n
92 help
93 This option determines if U-Boot forces gcc to inline the functions
94 developers have marked 'inline'. Doing so takes away freedom from gcc to
95 do what it thinks is best, which is desirable in some cases for size
96 reasons.
98 config CC_COVERAGE
99 bool "Enable code coverage analysis"
100 depends on SANDBOX
101 help
102 Enabling this option will pass "--coverage" to gcc to compile
103 and link code instrumented for coverage analysis.
105 config CC_HAS_ASM_INLINE
106 def_bool $(success,echo 'void foo(void) { asm inline (""); }' | $(CC) -x c - -c -o /dev/null)
108 config DISTRO_DEFAULTS
109 bool "Select defaults suitable for booting general purpose Linux distributions"
110 select AUTO_COMPLETE
111 select CMDLINE_EDITING
112 select CMD_BOOTI if ARM64
113 select CMD_BOOTZ if ARM && !ARM64
114 select CMD_DHCP if CMD_NET
115 select CMD_ENV_EXISTS
116 select CMD_EXT2
117 select CMD_EXT4
118 select CMD_FAT
119 select CMD_FS_GENERIC
120 select CMD_PART if PARTITIONS
121 select CMD_PING if CMD_NET
122 select CMD_PXE if NET
123 select CMD_SYSBOOT
124 select ENV_VARS_UBOOT_CONFIG
125 select HUSH_PARSER
126 select SUPPORT_RAW_INITRD
127 select SYS_LONGHELP
128 imply CMD_MII if NET
129 imply USB_STORAGE
130 imply USE_BOOTCOMMAND
131 help
132 Select this to enable various options and commands which are suitable
133 for building u-boot for booting general purpose Linux distributions.
135 config ENV_VARS_UBOOT_CONFIG
136 bool "Add arch, board, vendor and soc variables to default environment"
137 help
138 Define this in order to add variables describing the
139 U-Boot build configuration to the default environment.
140 These will be named arch, cpu, board, vendor, and soc.
141 Enabling this option will cause the following to be defined:
142 - CONFIG_SYS_ARCH
143 - CONFIG_SYS_CPU
144 - CONFIG_SYS_BOARD
145 - CONFIG_SYS_VENDOR
146 - CONFIG_SYS_SOC
148 config NR_DRAM_BANKS
149 int "Number of DRAM banks"
150 default 1 if ARCH_SUNXI || ARCH_OWL
151 default 4
152 help
153 This defines the number of DRAM banks.
155 config SYS_BOOT_GET_CMDLINE
156 bool "Enable kernel command line setup"
157 help
158 Enables allocating and saving kernel cmdline in space between
159 "bootm_low" and "bootm_low" + BOOTMAPSZ.
161 config SYS_BOOT_GET_KBD
162 bool "Enable kernel board information setup"
163 help
164 Enables allocating and saving a kernel copy of the bd_info in
165 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
167 config SYS_MALLOC_F
168 bool "Enable malloc() pool before relocation"
169 default y if DM
171 help
172 Before relocation, memory is very limited on many platforms. Still,
173 we can provide a small malloc() pool if needed. Driver model in
174 particular needs this to operate, so that it can allocate the
175 initial serial device and any others that are needed.
177 config SYS_MALLOC_F_LEN
178 hex "Size of malloc() pool before relocation"
179 depends on SYS_MALLOC_F
180 default 0x1000 if AM33XX
181 default 0x2800 if SANDBOX
182 default 0x2000 if (ARCH_IMX8 || ARCH_IMX8M || ARCH_MX7 || \
183 ARCH_MX7ULP || ARCH_MX6 || ARCH_MX5 || \
184 ARCH_LS1012A || ARCH_LS1021A || ARCH_LS1043A || \
185 ARCH_LS1046A || ARCH_QEMU)
186 default 0x400
187 help
188 Before relocation, memory is very limited on many platforms. Still,
189 we can provide a small malloc() pool if needed. Driver model in
190 particular needs this to operate, so that it can allocate the
191 initial serial device and any others that are needed.
193 config SYS_MALLOC_LEN
194 hex "Define memory for Dynamic allocation"
195 depends on ARCH_ZYNQ || ARCH_VERSAL || ARCH_STM32MP || ARCH_ROCKCHIP
196 default 0x2000000 if ARCH_ROCKCHIP
197 help
198 This defines memory to be allocated for Dynamic allocation
199 TODO: Use for other architectures
201 config SPL_SYS_MALLOC_F_LEN
202 hex "Size of malloc() pool in SPL before relocation"
203 depends on SYS_MALLOC_F && SPL
204 default 0x2800 if RCAR_GEN3
205 default SYS_MALLOC_F_LEN
206 help
207 Before relocation, memory is very limited on many platforms. Still,
208 we can provide a small malloc() pool if needed. Driver model in
209 particular needs this to operate, so that it can allocate the
210 initial serial device and any others that are needed.
212 config TPL_SYS_MALLOC_F_LEN
213 hex "Size of malloc() pool in TPL before relocation"
214 depends on SYS_MALLOC_F && TPL
215 default SYS_MALLOC_F_LEN
216 help
217 Before relocation, memory is very limited on many platforms. Still,
218 we can provide a small malloc() pool if needed. Driver model in
219 particular needs this to operate, so that it can allocate the
220 initial serial device and any others that are needed.
222 menuconfig EXPERT
223 bool "Configure standard U-Boot features (expert users)"
224 default y
225 help
226 This option allows certain base U-Boot options and settings
227 to be disabled or tweaked. This is for specialized
228 environments which can tolerate a "non-standard" U-Boot.
229 Use this only if you really know what you are doing.
231 if EXPERT
232 config SYS_MALLOC_CLEAR_ON_INIT
233 bool "Init with zeros the memory reserved for malloc (slow)"
234 default y
235 help
236 This setting is enabled by default. The reserved malloc
237 memory is initialized with zeros, so first malloc calls
238 will return the pointer to the zeroed memory. But this
239 slows the boot time.
241 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
242 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
243 Then the boot time can be significantly reduced.
244 Warning:
245 When disabling this, please check if malloc calls, maybe
246 should be replaced by calloc - if one expects zeroed memory.
248 config SYS_MALLOC_DEFAULT_TO_INIT
249 bool "Default malloc to init while reserving the memory for it"
250 default n
251 help
252 It may happen that one needs to move the dynamic allocation
253 from one to another memory range, eg. when moving the malloc
254 from the limited static to a potentially large dynamic (DDR)
255 memory.
257 If so then on top of setting the updated memory aside one
258 needs to bring the malloc init.
260 If such a scenario is sought choose yes.
262 config TOOLS_DEBUG
263 bool "Enable debug information for tools"
264 help
265 Enable generation of debug information for tools such as mkimage.
266 This can be used for debugging purposes. With debug information
267 it is possible to set breakpoints on particular lines, single-step
268 debug through the source code, etc.
270 endif # EXPERT
272 config PHYS_64BIT
273 bool "64bit physical address support"
274 help
275 Say Y here to support 64bit physical memory address.
276 This can be used not only for 64bit SoCs, but also for
277 large physical address extension on 32bit SoCs.
279 config HAS_ROM
280 bool
281 select BINMAN
282 help
283 Enables building of a u-boot.rom target. This collects U-Boot and
284 any necessary binary blobs.
286 config ROM_NEEDS_BLOBS
287 bool
288 depends on HAS_ROM
289 help
290 Enable this if building the u-boot.rom target needs binary blobs, and
291 so cannot be done normally. In this case, pass BUILD_ROM=1 to make
292 to tell U-Boot to build the ROM.
294 config BUILD_ROM
295 bool "Build U-Boot as BIOS replacement"
296 depends on HAS_ROM
297 default y if !ROM_NEEDS_BLOBS
298 help
299 This option allows to build a ROM version of U-Boot.
300 The build process generally requires several binary blobs
301 which are not shipped in the U-Boot source tree.
302 Please, see doc/arch/x86.rst for details.
304 config SPL_IMAGE
305 string "SPL image used in the combined SPL+U-Boot image"
306 default "spl/boot.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
307 default "spl/u-boot-spl.bin"
308 depends on SPL
309 help
310 Select the SPL build target that shall be generated by the SPL
311 build process (default spl/u-boot-spl.bin). This image will be
312 used to generate a combined image with SPL and main U-Boot
313 proper as one single image.
315 config BUILD_TARGET
316 string "Build target special images"
317 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
318 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
319 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
320 default "u-boot-elf.srec" if RCAR_GEN3
321 default "u-boot.itb" if SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
322 ARCH_SUNXI || RISCV || ARCH_ZYNQMP)
323 default "u-boot.kwb" if ARCH_KIRKWOOD
324 default "u-boot-with-spl.bin" if ARCH_AT91 && SPL_NAND_SUPPORT
325 default "u-boot-with-spl.imx" if ARCH_MX6 && SPL
326 help
327 Some SoCs need special image types (e.g. U-Boot binary
328 with a special header) as build targets. By defining
329 CONFIG_BUILD_TARGET in the SoC / board header, this
330 special image will be automatically built upon calling
331 make / buildman.
333 config SYS_CUSTOM_LDSCRIPT
334 bool "Use a custom location for the U-Boot linker script"
335 help
336 Normally when linking U-Boot we will look in the board directory,
337 the CPU directory and finally the "cpu" directory of the architecture
338 for the ile "u-boot.lds" and use that as our linker. However, in
339 some cases we need to provide a different linker script. To do so,
340 enable this option and then provide the location under
341 CONFIG_SYS_LDSCRIPT.
343 config SYS_LDSCRIPT
344 depends on SYS_CUSTOM_LDSCRIPT
345 string "Custom ldscript location"
346 help
347 Path within the source tree to the linker script to use for the
348 main U-Boot binary.
350 config ERR_PTR_OFFSET
351 hex
352 default 0x0
353 help
354 Some U-Boot pointers have redundant information, so we can use a
355 scheme where we can return either an error code or a pointer with the
356 same return value. The default implementation just casts the pointer
357 to a number, however, this may fail on platforms where the end of the
358 address range is used for valid pointers (e.g. 0xffffff00 is a valid
359 heap pointer in socfpga SPL).
360 For such platforms, this value provides an upper range of those error
361 pointer values - up to 'MAX_ERRNO' bytes below this value must be
362 unused/invalid addresses.
364 config PLATFORM_ELFENTRY
365 string
366 default "__start" if MIPS
367 default "_start"
369 endmenu # General setup
371 menu "Boot images"
373 config ANDROID_BOOT_IMAGE
374 bool "Enable support for Android Boot Images"
375 default y if FASTBOOT
376 help
377 This enables support for booting images which use the Android
378 image format header.
380 config FIT
381 bool "Support Flattened Image Tree"
382 select MD5
383 select SHA1
384 help
385 This option allows you to boot the new uImage structure,
386 Flattened Image Tree. FIT is formally a FDT, which can include
387 images of various types (kernel, FDT blob, ramdisk, etc.)
388 in a single blob. To boot this new uImage structure,
389 pass the address of the blob to the "bootm" command.
390 FIT is very flexible, supporting compression, multiple images,
391 multiple configurations, verification through hashing and also
392 verified boot (secure boot using RSA).
394 if FIT
396 config FIT_EXTERNAL_OFFSET
397 hex "FIT external data offset"
398 default 0x0
399 help
400 This specifies a data offset in fit image.
401 The offset is from data payload offset to the beginning of
402 fit image header. When specifies a offset, specific data
403 could be put in the hole between data payload and fit image
404 header, such as CSF data on i.MX platform.
406 config FIT_ENABLE_SHA256_SUPPORT
407 bool "Support SHA256 checksum of FIT image contents"
408 default y
409 select SHA256
410 help
411 Enable this to support SHA256 checksum of FIT image contents. A
412 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
413 the image contents have not been corrupted.
415 config FIT_ENABLE_SHA384_SUPPORT
416 bool "Support SHA384 checksum of FIT image contents"
417 default n
418 select SHA384
419 help
420 Enable this to support SHA384 checksum of FIT image contents. A
421 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
422 the image contents have not been corrupted. Use this for the highest
423 security.
425 config FIT_ENABLE_SHA512_SUPPORT
426 bool "Support SHA512 checksum of FIT image contents"
427 default n
428 select SHA512
429 help
430 Enable this to support SHA512 checksum of FIT image contents. A
431 SHA512 checksum is a 512-bit (64-byte) hash value used to check that
432 the image contents have not been corrupted.
434 config FIT_SIGNATURE
435 bool "Enable signature verification of FIT uImages"
436 depends on DM
437 select HASH
438 select RSA
439 select RSA_VERIFY
440 select IMAGE_SIGN_INFO
441 help
442 This option enables signature verification of FIT uImages,
443 using a hash signed and verified using RSA. If
444 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
445 hashing is available using hardware, then the RSA library will use
446 it. See doc/uImage.FIT/signature.txt for more details.
448 WARNING: When relying on signed FIT images with a required signature
449 check the legacy image format is disabled by default, so that
450 unsigned images cannot be loaded. If a board needs the legacy image
451 format support in this case, enable it using
452 CONFIG_LEGACY_IMAGE_FORMAT.
454 config FIT_SIGNATURE_MAX_SIZE
455 hex "Max size of signed FIT structures"
456 depends on FIT_SIGNATURE
457 default 0x10000000
458 help
459 This option sets a max size in bytes for verified FIT uImages.
460 A sane value of 256MB protects corrupted DTB structures from overlapping
461 device memory. Assure this size does not extend past expected storage
462 space.
464 config FIT_ENABLE_RSASSA_PSS_SUPPORT
465 bool "Support rsassa-pss signature scheme of FIT image contents"
466 depends on FIT_SIGNATURE
467 default n
468 help
469 Enable this to support the pss padding algorithm as described
470 in the rfc8017 (https://tools.ietf.org/html/rfc8017).
472 config FIT_CIPHER
473 bool "Enable ciphering data in a FIT uImages"
474 depends on DM
475 select AES
476 help
477 Enable the feature of data ciphering/unciphering in the tool mkimage
478 and in the u-boot support of the FIT image.
480 config FIT_VERBOSE
481 bool "Show verbose messages when FIT images fail"
482 help
483 Generally a system will have valid FIT images so debug messages
484 are a waste of code space. If you are debugging your images then
485 you can enable this option to get more verbose information about
486 failures.
488 config FIT_BEST_MATCH
489 bool "Select the best match for the kernel device tree"
490 help
491 When no configuration is explicitly selected, default to the
492 one whose fdt's compatibility field best matches that of
493 U-Boot itself. A match is considered "best" if it matches the
494 most specific compatibility entry of U-Boot's fdt's root node.
495 The order of entries in the configuration's fdt is ignored.
497 config FIT_IMAGE_POST_PROCESS
498 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
499 depends on TI_SECURE_DEVICE
500 help
501 Allows doing any sort of manipulation to blobs after they got extracted
502 from FIT images like stripping off headers or modifying the size of the
503 blob, verification, authentication, decryption etc. in a platform or
504 board specific way. In order to use this feature a platform or board-
505 specific implementation of board_fit_image_post_process() must be
506 provided. Also, anything done during this post-processing step would
507 need to be comprehended in how the images were prepared before being
508 injected into the FIT creation (i.e. the blobs would have been pre-
509 processed before being added to the FIT image).
511 if SPL
513 config SPL_FIT
514 bool "Support Flattened Image Tree within SPL"
515 depends on SPL
516 select SPL_OF_LIBFDT
518 config SPL_FIT_PRINT
519 bool "Support FIT printing within SPL"
520 depends on SPL_FIT
521 help
522 Support printing the content of the fitImage in a verbose manner in SPL.
524 config SPL_FIT_SIGNATURE
525 bool "Enable signature verification of FIT firmware within SPL"
526 depends on SPL_DM
527 select SPL_FIT
528 select SPL_CRYPTO_SUPPORT
529 select SPL_HASH_SUPPORT
530 select SPL_RSA
531 select SPL_RSA_VERIFY
532 select SPL_IMAGE_SIGN_INFO
534 config SPL_LOAD_FIT
535 bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
536 select SPL_FIT
537 help
538 Normally with the SPL framework a legacy image is generated as part
539 of the build. This contains U-Boot along with information as to
540 where it should be loaded. This option instead enables generation
541 of a FIT (Flat Image Tree) which provides more flexibility. In
542 particular it can handle selecting from multiple device tree
543 and passing the correct one to U-Boot.
545 config SPL_LOAD_FIT_ADDRESS
546 hex "load address of fit image"
547 depends on SPL_LOAD_FIT
548 default 0x0
549 help
550 Specify the load address of the fit image that will be loaded
551 by SPL.
553 config SPL_LOAD_FIT_APPLY_OVERLAY
554 bool "Enable SPL applying DT overlays from FIT"
555 depends on SPL_LOAD_FIT
556 select OF_LIBFDT_OVERLAY
557 help
558 The device tree is loaded from the FIT image. Allow the SPL is to
559 also load device-tree overlays from the FIT image an apply them
560 over the device tree.
562 config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
563 depends on SPL_LOAD_FIT_APPLY_OVERLAY
564 default 0x10000
565 hex "size of temporary buffer used to load the overlays"
566 help
567 The size of the area where the overlays will be loaded and
568 uncompress. Must be at least as large as biggest overlay
569 (uncompressed)
571 config SPL_LOAD_FIT_FULL
572 bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
573 select SPL_FIT
574 help
575 Normally with the SPL framework a legacy image is generated as part
576 of the build. This contains U-Boot along with information as to
577 where it should be loaded. This option instead enables generation
578 of a FIT (Flat Image Tree) which provides more flexibility. In
579 particular it can handle selecting from multiple device tree
580 and passing the correct one to U-Boot.
582 config SPL_FIT_IMAGE_POST_PROCESS
583 bool "Enable post-processing of FIT artifacts after loading by the SPL"
584 depends on SPL_LOAD_FIT
585 help
586 Allows doing any sort of manipulation to blobs after they got extracted
587 from the U-Boot FIT image like stripping off headers or modifying the
588 size of the blob, verification, authentication, decryption etc. in a
589 platform or board specific way. In order to use this feature a platform
590 or board-specific implementation of board_fit_image_post_process() must
591 be provided. Also, anything done during this post-processing step would
592 need to be comprehended in how the images were prepared before being
593 injected into the FIT creation (i.e. the blobs would have been pre-
594 processed before being added to the FIT image).
596 config SPL_FIT_SOURCE
597 string ".its source file for U-Boot FIT image"
598 depends on SPL_FIT
599 help
600 Specifies a (platform specific) FIT source file to generate the
601 U-Boot FIT image. This could specify further image to load and/or
602 execute.
604 config SPL_FIT_GENERATOR
605 string ".its file generator script for U-Boot FIT image"
606 depends on SPL_FIT
607 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
608 default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
609 default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
610 default "arch/riscv/lib/mkimage_fit_opensbi.sh" if SPL_LOAD_FIT && RISCV
611 help
612 Specifies a (platform specific) script file to generate the FIT
613 source file used to build the U-Boot FIT image file. This gets
614 passed a list of supported device tree file stub names to
615 include in the generated image.
617 endif # SPL
619 endif # FIT
621 config LEGACY_IMAGE_FORMAT
622 bool "Enable support for the legacy image format"
623 default y if !FIT_SIGNATURE
624 help
625 This option enables the legacy image format. It is enabled by
626 default for backward compatibility, unless FIT_SIGNATURE is
627 set where it is disabled so that unsigned images cannot be
628 loaded. If a board needs the legacy image format support in this
629 case, enable it here.
631 config OF_BOARD_SETUP
632 bool "Set up board-specific details in device tree before boot"
633 depends on OF_LIBFDT
634 help
635 This causes U-Boot to call ft_board_setup() before booting into
636 the Operating System. This function can set up various
637 board-specific information in the device tree for use by the OS.
638 The device tree is then passed to the OS.
640 config OF_SYSTEM_SETUP
641 bool "Set up system-specific details in device tree before boot"
642 depends on OF_LIBFDT
643 help
644 This causes U-Boot to call ft_system_setup() before booting into
645 the Operating System. This function can set up various
646 system-specific information in the device tree for use by the OS.
647 The device tree is then passed to the OS.
649 config OF_STDOUT_VIA_ALIAS
650 bool "Update the device-tree stdout alias from U-Boot"
651 depends on OF_LIBFDT
652 help
653 This uses U-Boot's serial alias from the aliases node to update
654 the device tree passed to the OS. The "linux,stdout-path" property
655 in the chosen node is set to point to the correct serial node.
656 This option currently references CONFIG_CONS_INDEX, which is
657 incorrect when used with device tree as this option does not
658 exist / should not be used.
660 config SYS_EXTRA_OPTIONS
661 string "Extra Options (DEPRECATED)"
662 help
663 The old configuration infrastructure (= mkconfig + boards.cfg)
664 provided the extra options field. If you have something like
665 "HAS_BAR,BAZ=64", the optional options
666 #define CONFIG_HAS
667 #define CONFIG_BAZ 64
668 will be defined in include/config.h.
669 This option was prepared for the smooth migration from the old
670 configuration to Kconfig. Since this option will be removed sometime,
671 new boards should not use this option.
673 config HAVE_SYS_TEXT_BASE
674 bool
675 depends on !NIOS2 && !XTENSA
676 depends on !EFI_APP
677 default y
679 config SYS_TEXT_BASE
680 depends on HAVE_SYS_TEXT_BASE
681 default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
682 default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
683 default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
684 default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
685 hex "Text Base"
686 help
687 The address in memory that U-Boot will be running from, initially.
689 config SYS_CLK_FREQ
690 depends on ARC || ARCH_SUNXI || MPC83xx
691 int "CPU clock frequency"
692 help
693 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
695 config ARCH_FIXUP_FDT_MEMORY
696 bool "Enable arch_fixup_memory_banks() call"
697 default y
698 help
699 Enable FDT memory map syncup before OS boot. This feature can be
700 used for booting OS with different memory setup where the part of
701 the memory location should be used for different purpose.
703 endmenu # Boot images
705 source "api/Kconfig"
707 source "common/Kconfig"
709 source "cmd/Kconfig"
711 source "disk/Kconfig"
713 source "dts/Kconfig"
715 source "env/Kconfig"
717 source "net/Kconfig"
719 source "drivers/Kconfig"
721 source "fs/Kconfig"
723 source "lib/Kconfig"
725 source "test/Kconfig"