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
18 string "Local version - append to U-Boot release"
20 Append an extra string to the end of your U-Boot version.
21 This will show up in your boot log, for example.
22 The string you set here will be appended after the contents of
23 any files with a filename matching localversion* in your
24 object and source tree, in that order. Your total string can
25 be a maximum of 64 characters.
27 config LOCALVERSION_AUTO
28 bool "Automatically append version information to the version string"
31 This will try to automatically determine if the current tree is a
32 release tree by looking for Git tags that belong to the current
35 A string of the format -gxxxxxxxx will be added to the localversion
36 if a Git-based tree is found. The string generated by this will be
37 appended after any matching localversion* files, and after the value
38 set in CONFIG_LOCALVERSION.
40 (The actual string used here is the first eight characters produced
41 by running the command:
43 $ git rev-parse --verify HEAD
45 which is done within the script "scripts/setlocalversion".)
47 config CC_OPTIMIZE_FOR_SIZE
48 bool "Optimize for size"
51 Enabling this option will pass "-Os" instead of "-O2" to gcc
52 resulting in a smaller U-Boot image.
54 This option is enabled by default for U-Boot.
56 config DISTRO_DEFAULTS
57 bool "Select defaults suitable for booting general purpose Linux distributions"
58 default y if ARCH_SUNXI || TEGRA
59 default y if ARCH_LS2080A
60 default y if ARCH_MESON
61 default y if ARCH_ROCKCHIP
63 select CMD_BOOTZ if ARM && !ARM64
64 select CMD_BOOTI if ARM64
76 Select this to enable various options and commands which are suitable
77 for building u-boot for booting general purpose Linux distributions.
80 bool "Enable malloc() pool before relocation"
83 Before relocation, memory is very limited on many platforms. Still,
84 we can provide a small malloc() pool if needed. Driver model in
85 particular needs this to operate, so that it can allocate the
86 initial serial device and any others that are needed.
88 config SYS_MALLOC_F_LEN
89 hex "Size of malloc() pool before relocation"
90 depends on SYS_MALLOC_F
93 Before relocation, memory is very limited on many platforms. Still,
94 we can provide a small malloc() pool if needed. Driver model in
95 particular needs this to operate, so that it can allocate the
96 initial serial device and any others that are needed.
99 bool "Configure standard U-Boot features (expert users)"
102 This option allows certain base U-Boot options and settings
103 to be disabled or tweaked. This is for specialized
104 environments which can tolerate a "non-standard" U-Boot.
105 Use this only if you really know what you are doing.
108 config SYS_MALLOC_CLEAR_ON_INIT
109 bool "Init with zeros the memory reserved for malloc (slow)"
112 This setting is enabled by default. The reserved malloc
113 memory is initialized with zeros, so first malloc calls
114 will return the pointer to the zeroed memory. But this
117 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
118 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
119 Then the boot time can be significantly reduced.
121 When disabling this, please check if malloc calls, maybe
122 should be replaced by calloc - if one expects zeroed memory.
125 bool "Enable debug information for tools"
127 Enable generation of debug information for tools such as mkimage.
128 This can be used for debugging purposes. With debug information
129 it is possible to set breakpoints on particular lines, single-step
130 debug through the source code, etc.
135 bool "64bit physical address support"
137 Say Y here to support 64bit physical memory address.
138 This can be used not only for 64bit SoCs, but also for
139 large physical address extention on 32bit SoCs.
141 endmenu # General setup
146 bool "Support Flattened Image Tree"
148 This option allows you to boot the new uImage structure,
149 Flattened Image Tree. FIT is formally a FDT, which can include
150 images of various types (kernel, FDT blob, ramdisk, etc.)
151 in a single blob. To boot this new uImage structure,
152 pass the address of the blob to the "bootm" command.
153 FIT is very flexible, supporting compression, multiple images,
154 multiple configurations, verification through hashing and also
155 verified boot (secure boot using RSA).
160 bool "Enable signature verification of FIT uImages"
164 This option enables signature verification of FIT uImages,
165 using a hash signed and verified using RSA. If
166 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
167 hashing is available using hardware, then the RSA library will use
168 it. See doc/uImage.FIT/signature.txt for more details.
170 WARNING: When relying on signed FIT images with a required signature
171 check the legacy image format is disabled by default, so that
172 unsigned images cannot be loaded. If a board needs the legacy image
173 format support in this case, enable it using
174 CONFIG_IMAGE_FORMAT_LEGACY.
177 bool "Show verbose messages when FIT images fail"
179 Generally a system will have valid FIT images so debug messages
180 are a waste of code space. If you are debugging your images then
181 you can enable this option to get more verbose information about
184 config FIT_BEST_MATCH
185 bool "Select the best match for the kernel device tree"
187 When no configuration is explicitly selected, default to the
188 one whose fdt's compatibility field best matches that of
189 U-Boot itself. A match is considered "best" if it matches the
190 most specific compatibility entry of U-Boot's fdt's root node.
191 The order of entries in the configuration's fdt is ignored.
193 config FIT_IMAGE_POST_PROCESS
194 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
195 depends on TI_SECURE_DEVICE
197 Allows doing any sort of manipulation to blobs after they got extracted
198 from FIT images like stripping off headers or modifying the size of the
199 blob, verification, authentication, decryption etc. in a platform or
200 board specific way. In order to use this feature a platform or board-
201 specific implementation of board_fit_image_post_process() must be
202 provided. Also, anything done during this post-processing step would
203 need to be comprehended in how the images were prepared before being
204 injected into the FIT creation (i.e. the blobs would have been pre-
205 processed before being added to the FIT image).
208 bool "Support Flattened Image Tree within SPL"
211 config SPL_FIT_SIGNATURE
212 bool "Enable signature verification of FIT firmware within SPL"
218 bool "Enable SPL loading U-Boot as a FIT"
220 Normally with the SPL framework a legacy image is generated as part
221 of the build. This contains U-Boot along with information as to
222 where it should be loaded. This option instead enables generation
223 of a FIT (Flat Image Tree) which provides more flexibility. In
224 particular it can handle selecting from multiple device tree
225 and passing the correct one to U-Boot.
227 config SPL_FIT_IMAGE_POST_PROCESS
228 bool "Enable post-processing of FIT artifacts after loading by the SPL"
229 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
231 Allows doing any sort of manipulation to blobs after they got extracted
232 from the U-Boot FIT image like stripping off headers or modifying the
233 size of the blob, verification, authentication, decryption etc. in a
234 platform or board specific way. In order to use this feature a platform
235 or board-specific implementation of board_fit_image_post_process() must
236 be provided. Also, anything done during this post-processing step would
237 need to be comprehended in how the images were prepared before being
238 injected into the FIT creation (i.e. the blobs would have been pre-
239 processed before being added to the FIT image).
243 config OF_BOARD_SETUP
244 bool "Set up board-specific details in device tree before boot"
247 This causes U-Boot to call ft_board_setup() before booting into
248 the Operating System. This function can set up various
249 board-specific information in the device tree for use by the OS.
250 The device tree is then passed to the OS.
252 config OF_SYSTEM_SETUP
253 bool "Set up system-specific details in device tree before boot"
256 This causes U-Boot to call ft_system_setup() before booting into
257 the Operating System. This function can set up various
258 system-specific information in the device tree for use by the OS.
259 The device tree is then passed to the OS.
261 config OF_STDOUT_VIA_ALIAS
262 bool "Update the device-tree stdout alias from U-Boot"
265 This uses U-Boot's serial alias from the aliases node to update
266 the device tree passed to the OS. The "linux,stdout-path" property
267 in the chosen node is set to point to the correct serial node.
268 This option currently references CONFIG_CONS_INDEX, which is
269 incorrect when used with device tree as this option does not
270 exist / should not be used.
272 config SYS_EXTRA_OPTIONS
273 string "Extra Options (DEPRECATED)"
275 The old configuration infrastructure (= mkconfig + boards.cfg)
276 provided the extra options field. If you have something like
277 "HAS_BAR,BAZ=64", the optional options
279 #define CONFIG_BAZ 64
280 will be defined in include/config.h.
281 This option was prepared for the smooth migration from the old
282 configuration to Kconfig. Since this option will be removed sometime,
283 new boards should not use this option.
286 depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
287 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
292 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
296 depends on ARC || ARCH_SUNXI
297 int "CPU clock frequency"
299 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
301 config ARCH_FIXUP_FDT_MEMORY
302 bool "Enable arch_fixup_memory_banks() call"
305 Enable FDT memory map syncup before OS boot. This feature can be
306 used for booting OS with different memory setup where the part of
307 the memory location should be used for different purpose.
309 endmenu # Boot images
311 source "common/Kconfig"
315 source "disk/Kconfig"
321 source "drivers/Kconfig"
327 source "test/Kconfig"