1
2
3
4
5
6mainmenu "U-Boot $UBOOTVERSION Configuration"
7
8config UBOOTVERSION
9 string
10 option env="UBOOTVERSION"
11
12
13source "arch/Kconfig"
14
15menu "General setup"
16
17config LOCALVERSION
18 string "Local version - append to U-Boot release"
19 help
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.
26
27config LOCALVERSION_AUTO
28 bool "Automatically append version information to the version string"
29 default y
30 help
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
33 top of tree revision.
34
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.
39
40 (The actual string used here is the first eight characters produced
41 by running the command:
42
43 $ git rev-parse --verify HEAD
44
45 which is done within the script "scripts/setlocalversion".)
46
47config CC_OPTIMIZE_FOR_SIZE
48 bool "Optimize for size"
49 default y
50 help
51 Enabling this option will pass "-Os" instead of "-O2" to gcc
52 resulting in a smaller U-Boot image.
53
54 This option is enabled by default for U-Boot.
55
56config 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
62 default n
63 select CMD_BOOTZ if ARM && !ARM64
64 select CMD_BOOTI if ARM64
65 select CMD_DHCP
66 select CMD_PXE
67 select CMD_EXT2
68 select CMD_EXT4
69 select CMD_FAT
70 select CMD_FS_GENERIC
71 select CMD_MII
72 select CMD_PING
73 select CMD_PART
74 select HUSH_PARSER
75 help
76 Select this to enable various options and commands which are suitable
77 for building u-boot for booting general purpose Linux distributions.
78
79config SYS_MALLOC_F
80 bool "Enable malloc() pool before relocation"
81 default y if DM
82 help
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.
87
88config SYS_MALLOC_F_LEN
89 hex "Size of malloc() pool before relocation"
90 depends on SYS_MALLOC_F
91 default 0x400
92 help
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.
97
98config SPL_SYS_MALLOC_F_LEN
99 hex "Size of malloc() pool in SPL before relocation"
100 depends on SYS_MALLOC_F
101 default SYS_MALLOC_F_LEN
102 help
103 Before relocation, memory is very limited on many platforms. Still,
104 we can provide a small malloc() pool if needed. Driver model in
105 particular needs this to operate, so that it can allocate the
106 initial serial device and any others that are needed.
107
108config TPL_SYS_MALLOC_F_LEN
109 hex "Size of malloc() pool in TPL before relocation"
110 depends on SYS_MALLOC_F
111 default SYS_MALLOC_F_LEN
112 help
113 Before relocation, memory is very limited on many platforms. Still,
114 we can provide a small malloc() pool if needed. Driver model in
115 particular needs this to operate, so that it can allocate the
116 initial serial device and any others that are needed.
117
118menuconfig EXPERT
119 bool "Configure standard U-Boot features (expert users)"
120 default y
121 help
122 This option allows certain base U-Boot options and settings
123 to be disabled or tweaked. This is for specialized
124 environments which can tolerate a "non-standard" U-Boot.
125 Use this only if you really know what you are doing.
126
127if EXPERT
128 config SYS_MALLOC_CLEAR_ON_INIT
129 bool "Init with zeros the memory reserved for malloc (slow)"
130 default y
131 help
132 This setting is enabled by default. The reserved malloc
133 memory is initialized with zeros, so first malloc calls
134 will return the pointer to the zeroed memory. But this
135 slows the boot time.
136
137 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
138 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
139 Then the boot time can be significantly reduced.
140 Warning:
141 When disabling this, please check if malloc calls, maybe
142 should be replaced by calloc - if one expects zeroed memory.
143
144config TOOLS_DEBUG
145 bool "Enable debug information for tools"
146 help
147 Enable generation of debug information for tools such as mkimage.
148 This can be used for debugging purposes. With debug information
149 it is possible to set breakpoints on particular lines, single-step
150 debug through the source code, etc.
151
152endif
153
154config PHYS_64BIT
155 bool "64bit physical address support"
156 help
157 Say Y here to support 64bit physical memory address.
158 This can be used not only for 64bit SoCs, but also for
159 large physical address extention on 32bit SoCs.
160
161endmenu
162
163menu "Boot images"
164
165config ANDROID_BOOT_IMAGE
166 bool "Enable support for Android Boot Images"
167 default y if FASTBOOT
168 help
169 This enables support for booting images which use the Android
170 image format header.
171
172config FIT
173 bool "Support Flattened Image Tree"
174 select MD5
175 select SHA1
176 help
177 This option allows you to boot the new uImage structure,
178 Flattened Image Tree. FIT is formally a FDT, which can include
179 images of various types (kernel, FDT blob, ramdisk, etc.)
180 in a single blob. To boot this new uImage structure,
181 pass the address of the blob to the "bootm" command.
182 FIT is very flexible, supporting compression, multiple images,
183 multiple configurations, verification through hashing and also
184 verified boot (secure boot using RSA).
185
186if FIT
187
188config FIT_ENABLE_SHA256_SUPPORT
189 bool "Support SHA256 checksum of FIT image contents"
190 select SHA256
191 default y
192 help
193 Enable this to support SHA256 checksum of FIT image contents. A
194 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
195 the image contents have not been corrupted. SHA256 is recommended
196 for use in secure applications since (as at 2016) there is no known
197 feasible attack that could produce a 'collision' with differing
198 input data. Use this for the highest security. Note that only the
199 SHA256 variant is supported: SHA512 and others are not currently
200 supported in U-Boot.
201
202config FIT_SIGNATURE
203 bool "Enable signature verification of FIT uImages"
204 depends on DM
205 select RSA
206 help
207 This option enables signature verification of FIT uImages,
208 using a hash signed and verified using RSA. If
209 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
210 hashing is available using hardware, then the RSA library will use
211 it. See doc/uImage.FIT/signature.txt for more details.
212
213 WARNING: When relying on signed FIT images with a required signature
214 check the legacy image format is disabled by default, so that
215 unsigned images cannot be loaded. If a board needs the legacy image
216 format support in this case, enable it using
217 CONFIG_IMAGE_FORMAT_LEGACY.
218
219config FIT_VERBOSE
220 bool "Show verbose messages when FIT images fail"
221 help
222 Generally a system will have valid FIT images so debug messages
223 are a waste of code space. If you are debugging your images then
224 you can enable this option to get more verbose information about
225 failures.
226
227config FIT_BEST_MATCH
228 bool "Select the best match for the kernel device tree"
229 help
230 When no configuration is explicitly selected, default to the
231 one whose fdt's compatibility field best matches that of
232 U-Boot itself. A match is considered "best" if it matches the
233 most specific compatibility entry of U-Boot's fdt's root node.
234 The order of entries in the configuration's fdt is ignored.
235
236config FIT_IMAGE_POST_PROCESS
237 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
238 depends on TI_SECURE_DEVICE
239 help
240 Allows doing any sort of manipulation to blobs after they got extracted
241 from FIT images like stripping off headers or modifying the size of the
242 blob, verification, authentication, decryption etc. in a platform or
243 board specific way. In order to use this feature a platform or board-
244 specific implementation of board_fit_image_post_process() must be
245 provided. Also, anything done during this post-processing step would
246 need to be comprehended in how the images were prepared before being
247 injected into the FIT creation (i.e. the blobs would have been pre-
248 processed before being added to the FIT image).
249
250if SPL
251
252config SPL_FIT
253 bool "Support Flattened Image Tree within SPL"
254 depends on SPL
255 select SPL_OF_LIBFDT
256
257config SPL_FIT_SIGNATURE
258 bool "Enable signature verification of FIT firmware within SPL"
259 depends on SPL_DM
260 select SPL_FIT
261 select SPL_RSA
262
263config SPL_LOAD_FIT
264 bool "Enable SPL loading U-Boot as a FIT"
265 select SPL_FIT
266 help
267 Normally with the SPL framework a legacy image is generated as part
268 of the build. This contains U-Boot along with information as to
269 where it should be loaded. This option instead enables generation
270 of a FIT (Flat Image Tree) which provides more flexibility. In
271 particular it can handle selecting from multiple device tree
272 and passing the correct one to U-Boot.
273
274config SPL_FIT_IMAGE_POST_PROCESS
275 bool "Enable post-processing of FIT artifacts after loading by the SPL"
276 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
277 help
278 Allows doing any sort of manipulation to blobs after they got extracted
279 from the U-Boot FIT image like stripping off headers or modifying the
280 size of the blob, verification, authentication, decryption etc. in a
281 platform or board specific way. In order to use this feature a platform
282 or board-specific implementation of board_fit_image_post_process() must
283 be provided. Also, anything done during this post-processing step would
284 need to be comprehended in how the images were prepared before being
285 injected into the FIT creation (i.e. the blobs would have been pre-
286 processed before being added to the FIT image).
287
288config SPL_FIT_SOURCE
289 string ".its source file for U-Boot FIT image"
290 depends on SPL_FIT
291 help
292 Specifies a (platform specific) FIT source file to generate the
293 U-Boot FIT image. This could specify further image to load and/or
294 execute.
295
296config SPL_FIT_GENERATOR
297 string ".its file generator script for U-Boot FIT image"
298 depends on SPL_FIT
299 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
300 help
301 Specifies a (platform specific) script file to generate the FIT
302 source file used to build the U-Boot FIT image file. This gets
303 passed a list of supported device tree file stub names to
304 include in the generated image.
305
306endif
307
308endif
309
310config OF_BOARD_SETUP
311 bool "Set up board-specific details in device tree before boot"
312 depends on OF_LIBFDT
313 help
314 This causes U-Boot to call ft_board_setup() before booting into
315 the Operating System. This function can set up various
316 board-specific information in the device tree for use by the OS.
317 The device tree is then passed to the OS.
318
319config OF_SYSTEM_SETUP
320 bool "Set up system-specific details in device tree before boot"
321 depends on OF_LIBFDT
322 help
323 This causes U-Boot to call ft_system_setup() before booting into
324 the Operating System. This function can set up various
325 system-specific information in the device tree for use by the OS.
326 The device tree is then passed to the OS.
327
328config OF_STDOUT_VIA_ALIAS
329 bool "Update the device-tree stdout alias from U-Boot"
330 depends on OF_LIBFDT
331 help
332 This uses U-Boot's serial alias from the aliases node to update
333 the device tree passed to the OS. The "linux,stdout-path" property
334 in the chosen node is set to point to the correct serial node.
335 This option currently references CONFIG_CONS_INDEX, which is
336 incorrect when used with device tree as this option does not
337 exist / should not be used.
338
339config SYS_EXTRA_OPTIONS
340 string "Extra Options (DEPRECATED)"
341 help
342 The old configuration infrastructure (= mkconfig + boards.cfg)
343 provided the extra options field. If you have something like
344 "HAS_BAR,BAZ=64", the optional options
345 #define CONFIG_HAS
346 #define CONFIG_BAZ 64
347 will be defined in include/config.h.
348 This option was prepared for the smooth migration from the old
349 configuration to Kconfig. Since this option will be removed sometime,
350 new boards should not use this option.
351
352config SYS_TEXT_BASE
353 depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
354 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
355 ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS
356 depends on !EFI_APP
357 hex "Text Base"
358 help
359 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
360
361 default 0x80800000 if ARCH_OMAP2PLUS
362
363
364config SYS_CLK_FREQ
365 depends on ARC || ARCH_SUNXI
366 int "CPU clock frequency"
367 help
368 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
369
370config ARCH_FIXUP_FDT_MEMORY
371 bool "Enable arch_fixup_memory_banks() call"
372 default y
373 help
374 Enable FDT memory map syncup before OS boot. This feature can be
375 used for booting OS with different memory setup where the part of
376 the memory location should be used for different purpose.
377
378endmenu
379
380source "api/Kconfig"
381
382source "common/Kconfig"
383
384source "cmd/Kconfig"
385
386source "disk/Kconfig"
387
388source "dts/Kconfig"
389
390source "env/Kconfig"
391
392source "net/Kconfig"
393
394source "drivers/Kconfig"
395
396source "fs/Kconfig"
397
398source "lib/Kconfig"
399
400source "test/Kconfig"
401
402source "scripts/Kconfig"
403
