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