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
75 Select this to enable various options and commands which are suitable
76 for building u-boot for booting general purpose Linux distributions.
79 bool "Enable malloc() pool before relocation"
82 Before relocation, memory is very limited on many platforms. Still,
83 we can provide a small malloc() pool if needed. Driver model in
84 particular needs this to operate, so that it can allocate the
85 initial serial device and any others that are needed.
87 config SYS_MALLOC_F_LEN
88 hex "Size of malloc() pool before relocation"
89 depends on SYS_MALLOC_F
92 Before relocation, memory is very limited on many platforms. Still,
93 we can provide a small malloc() pool if needed. Driver model in
94 particular needs this to operate, so that it can allocate the
95 initial serial device and any others that are needed.
98 bool "Configure standard U-Boot features (expert users)"
101 This option allows certain base U-Boot options and settings
102 to be disabled or tweaked. This is for specialized
103 environments which can tolerate a "non-standard" U-Boot.
104 Use this only if you really know what you are doing.
107 config SYS_MALLOC_CLEAR_ON_INIT
108 bool "Init with zeros the memory reserved for malloc (slow)"
111 This setting is enabled by default. The reserved malloc
112 memory is initialized with zeros, so first malloc calls
113 will return the pointer to the zeroed memory. But this
116 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
117 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
118 Then the boot time can be significantly reduced.
120 When disabling this, please check if malloc calls, maybe
121 should be replaced by calloc - if one expects zeroed memory.
124 bool "Enable debug information for tools"
126 Enable generation of debug information for tools such as mkimage.
127 This can be used for debugging purposes. With debug information
128 it is possible to set breakpoints on particular lines, single-step
129 debug through the source code, etc.
134 bool "64bit physical address support"
136 Say Y here to support 64bit physical memory address.
137 This can be used not only for 64bit SoCs, but also for
138 large physical address extention on 32bit SoCs.
140 endmenu # General setup
145 bool "Support Flattened Image Tree"
147 This option allows you to boot the new uImage structure,
148 Flattened Image Tree. FIT is formally a FDT, which can include
149 images of various types (kernel, FDT blob, ramdisk, etc.)
150 in a single blob. To boot this new uImage structure,
151 pass the address of the blob to the "bootm" command.
152 FIT is very flexible, supporting compression, multiple images,
153 multiple configurations, verification through hashing and also
154 verified boot (secure boot using RSA).
159 bool "Enable signature verification of FIT uImages"
163 This option enables signature verification of FIT uImages,
164 using a hash signed and verified using RSA. If
165 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
166 hashing is available using hardware, then the RSA library will use
167 it. See doc/uImage.FIT/signature.txt for more details.
169 WARNING: When relying on signed FIT images with a required signature
170 check the legacy image format is disabled by default, so that
171 unsigned images cannot be loaded. If a board needs the legacy image
172 format support in this case, enable it using
173 CONFIG_IMAGE_FORMAT_LEGACY.
176 bool "Show verbose messages when FIT images fail"
178 Generally a system will have valid FIT images so debug messages
179 are a waste of code space. If you are debugging your images then
180 you can enable this option to get more verbose information about
183 config FIT_BEST_MATCH
184 bool "Select the best match for the kernel device tree"
186 When no configuration is explicitly selected, default to the
187 one whose fdt's compatibility field best matches that of
188 U-Boot itself. A match is considered "best" if it matches the
189 most specific compatibility entry of U-Boot's fdt's root node.
190 The order of entries in the configuration's fdt is ignored.
192 config FIT_IMAGE_POST_PROCESS
193 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
194 depends on TI_SECURE_DEVICE
196 Allows doing any sort of manipulation to blobs after they got extracted
197 from FIT images like stripping off headers or modifying the size of the
198 blob, verification, authentication, decryption etc. in a platform or
199 board specific way. In order to use this feature a platform or board-
200 specific implementation of board_fit_image_post_process() must be
201 provided. Also, anything done during this post-processing step would
202 need to be comprehended in how the images were prepared before being
203 injected into the FIT creation (i.e. the blobs would have been pre-
204 processed before being added to the FIT image).
207 bool "Support Flattened Image Tree within SPL"
210 config SPL_FIT_SIGNATURE
211 bool "Enable signature verification of FIT firmware within SPL"
217 bool "Enable SPL loading U-Boot as a FIT"
219 Normally with the SPL framework a legacy image is generated as part
220 of the build. This contains U-Boot along with information as to
221 where it should be loaded. This option instead enables generation
222 of a FIT (Flat Image Tree) which provides more flexibility. In
223 particular it can handle selecting from multiple device tree
224 and passing the correct one to U-Boot.
226 config SPL_FIT_IMAGE_POST_PROCESS
227 bool "Enable post-processing of FIT artifacts after loading by the SPL"
228 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
230 Allows doing any sort of manipulation to blobs after they got extracted
231 from the U-Boot FIT image like stripping off headers or modifying the
232 size of the blob, verification, authentication, decryption etc. in a
233 platform or board specific way. In order to use this feature a platform
234 or board-specific implementation of board_fit_image_post_process() must
235 be provided. Also, anything done during this post-processing step would
236 need to be comprehended in how the images were prepared before being
237 injected into the FIT creation (i.e. the blobs would have been pre-
238 processed before being added to the FIT image).
242 config OF_BOARD_SETUP
243 bool "Set up board-specific details in device tree before boot"
246 This causes U-Boot to call ft_board_setup() before booting into
247 the Operating System. This function can set up various
248 board-specific information in the device tree for use by the OS.
249 The device tree is then passed to the OS.
251 config OF_SYSTEM_SETUP
252 bool "Set up system-specific details in device tree before boot"
255 This causes U-Boot to call ft_system_setup() before booting into
256 the Operating System. This function can set up various
257 system-specific information in the device tree for use by the OS.
258 The device tree is then passed to the OS.
260 config OF_STDOUT_VIA_ALIAS
261 bool "Update the device-tree stdout alias from U-Boot"
264 This uses U-Boot's serial alias from the aliases node to update
265 the device tree passed to the OS. The "linux,stdout-path" property
266 in the chosen node is set to point to the correct serial node.
267 This option currently references CONFIG_CONS_INDEX, which is
268 incorrect when used with device tree as this option does not
269 exist / should not be used.
271 config SYS_EXTRA_OPTIONS
272 string "Extra Options (DEPRECATED)"
274 The old configuration infrastructure (= mkconfig + boards.cfg)
275 provided the extra options field. If you have something like
276 "HAS_BAR,BAZ=64", the optional options
278 #define CONFIG_BAZ 64
279 will be defined in include/config.h.
280 This option was prepared for the smooth migration from the old
281 configuration to Kconfig. Since this option will be removed sometime,
282 new boards should not use this option.
285 depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
286 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
291 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
295 depends on ARC || ARCH_SUNXI
296 int "CPU clock frequency"
298 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
300 config ARCH_FIXUP_FDT_MEMORY
301 bool "Enable arch_fixup_memory_banks() call"
304 Enable FDT memory map syncup before OS boot. This feature can be
305 used for booting OS with different memory setup where the part of
306 the memory location should be used for different purpose.
308 endmenu # Boot images
310 source "common/Kconfig"
318 source "drivers/Kconfig"
324 source "test/Kconfig"