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"
150 This option allows you to boot the new uImage structure,
151 Flattened Image Tree. FIT is formally a FDT, which can include
152 images of various types (kernel, FDT blob, ramdisk, etc.)
153 in a single blob. To boot this new uImage structure,
154 pass the address of the blob to the "bootm" command.
155 FIT is very flexible, supporting compression, multiple images,
156 multiple configurations, verification through hashing and also
157 verified boot (secure boot using RSA).
161 config FIT_ENABLE_SHA256_SUPPORT
162 bool "Support SHA256 checksum of FIT image contents"
166 Enable this to support SHA256 checksum of FIT image contents. A
167 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
168 the image contents have not been corrupted. SHA256 is recommended
169 for use in secure applications since (as at 2016) there is no known
170 feasible attack that could produce a 'collision' with differing
171 input data. Use this for the highest security. Note that only the
172 SHA256 variant is supported: SHA512 and others are not currently
176 bool "Enable signature verification of FIT uImages"
180 This option enables signature verification of FIT uImages,
181 using a hash signed and verified using RSA. If
182 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
183 hashing is available using hardware, then the RSA library will use
184 it. See doc/uImage.FIT/signature.txt for more details.
186 WARNING: When relying on signed FIT images with a required signature
187 check the legacy image format is disabled by default, so that
188 unsigned images cannot be loaded. If a board needs the legacy image
189 format support in this case, enable it using
190 CONFIG_IMAGE_FORMAT_LEGACY.
193 bool "Show verbose messages when FIT images fail"
195 Generally a system will have valid FIT images so debug messages
196 are a waste of code space. If you are debugging your images then
197 you can enable this option to get more verbose information about
200 config FIT_BEST_MATCH
201 bool "Select the best match for the kernel device tree"
203 When no configuration is explicitly selected, default to the
204 one whose fdt's compatibility field best matches that of
205 U-Boot itself. A match is considered "best" if it matches the
206 most specific compatibility entry of U-Boot's fdt's root node.
207 The order of entries in the configuration's fdt is ignored.
209 config FIT_IMAGE_POST_PROCESS
210 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
211 depends on TI_SECURE_DEVICE
213 Allows doing any sort of manipulation to blobs after they got extracted
214 from FIT images like stripping off headers or modifying the size of the
215 blob, verification, authentication, decryption etc. in a platform or
216 board specific way. In order to use this feature a platform or board-
217 specific implementation of board_fit_image_post_process() must be
218 provided. Also, anything done during this post-processing step would
219 need to be comprehended in how the images were prepared before being
220 injected into the FIT creation (i.e. the blobs would have been pre-
221 processed before being added to the FIT image).
224 bool "Support Flattened Image Tree within SPL"
227 config SPL_FIT_SIGNATURE
228 bool "Enable signature verification of FIT firmware within SPL"
234 bool "Enable SPL loading U-Boot as a FIT"
236 Normally with the SPL framework a legacy image is generated as part
237 of the build. This contains U-Boot along with information as to
238 where it should be loaded. This option instead enables generation
239 of a FIT (Flat Image Tree) which provides more flexibility. In
240 particular it can handle selecting from multiple device tree
241 and passing the correct one to U-Boot.
243 config SPL_FIT_IMAGE_POST_PROCESS
244 bool "Enable post-processing of FIT artifacts after loading by the SPL"
245 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
247 Allows doing any sort of manipulation to blobs after they got extracted
248 from the U-Boot FIT image like stripping off headers or modifying the
249 size of the blob, verification, authentication, decryption etc. in a
250 platform or board specific way. In order to use this feature a platform
251 or board-specific implementation of board_fit_image_post_process() must
252 be provided. Also, anything done during this post-processing step would
253 need to be comprehended in how the images were prepared before being
254 injected into the FIT creation (i.e. the blobs would have been pre-
255 processed before being added to the FIT image).
259 config OF_BOARD_SETUP
260 bool "Set up board-specific details in device tree before boot"
263 This causes U-Boot to call ft_board_setup() before booting into
264 the Operating System. This function can set up various
265 board-specific information in the device tree for use by the OS.
266 The device tree is then passed to the OS.
268 config OF_SYSTEM_SETUP
269 bool "Set up system-specific details in device tree before boot"
272 This causes U-Boot to call ft_system_setup() before booting into
273 the Operating System. This function can set up various
274 system-specific information in the device tree for use by the OS.
275 The device tree is then passed to the OS.
277 config OF_STDOUT_VIA_ALIAS
278 bool "Update the device-tree stdout alias from U-Boot"
281 This uses U-Boot's serial alias from the aliases node to update
282 the device tree passed to the OS. The "linux,stdout-path" property
283 in the chosen node is set to point to the correct serial node.
284 This option currently references CONFIG_CONS_INDEX, which is
285 incorrect when used with device tree as this option does not
286 exist / should not be used.
288 config SYS_EXTRA_OPTIONS
289 string "Extra Options (DEPRECATED)"
291 The old configuration infrastructure (= mkconfig + boards.cfg)
292 provided the extra options field. If you have something like
293 "HAS_BAR,BAZ=64", the optional options
295 #define CONFIG_BAZ 64
296 will be defined in include/config.h.
297 This option was prepared for the smooth migration from the old
298 configuration to Kconfig. Since this option will be removed sometime,
299 new boards should not use this option.
302 depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
303 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
304 ARCH_ZYNQ || ARCH_KEYSTONE
308 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
312 depends on ARC || ARCH_SUNXI
313 int "CPU clock frequency"
315 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
317 config ARCH_FIXUP_FDT_MEMORY
318 bool "Enable arch_fixup_memory_banks() call"
321 Enable FDT memory map syncup before OS boot. This feature can be
322 used for booting OS with different memory setup where the part of
323 the memory location should be used for different purpose.
325 endmenu # Boot images
329 source "common/Kconfig"
333 source "disk/Kconfig"
339 source "drivers/Kconfig"
345 source "test/Kconfig"
347 source "scripts/Kconfig"