]> git.ipfire.org Git - people/ms/u-boot.git/blob - Kconfig
dt-bindings: Document the Broadcom STB wake-up timer node
[people/ms/u-boot.git] / Kconfig
1 #
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.
5 #
6 mainmenu "U-Boot $UBOOTVERSION Configuration"
7
8 config UBOOTVERSION
9 string
10 option env="UBOOTVERSION"
11
12 # Allow defaults in arch-specific code to override any given here
13 source "arch/Kconfig"
14
15 menu "General setup"
16
17 config 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
27 config 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
47 config 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
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
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
79 config 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
88 config 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
98 menuconfig EXPERT
99 bool "Configure standard U-Boot features (expert users)"
100 default y
101 help
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.
106
107 if EXPERT
108 config SYS_MALLOC_CLEAR_ON_INIT
109 bool "Init with zeros the memory reserved for malloc (slow)"
110 default y
111 help
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
115 slows the boot time.
116
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.
120 Warning:
121 When disabling this, please check if malloc calls, maybe
122 should be replaced by calloc - if one expects zeroed memory.
123
124 config TOOLS_DEBUG
125 bool "Enable debug information for tools"
126 help
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.
131
132 endif # EXPERT
133
134 config PHYS_64BIT
135 bool "64bit physical address support"
136 help
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.
140
141 endmenu # General setup
142
143 menu "Boot images"
144
145 config FIT
146 bool "Support Flattened Image Tree"
147 select MD5
148 select SHA1
149 help
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).
158
159 if FIT
160
161 config FIT_ENABLE_SHA256_SUPPORT
162 bool "Support SHA256 checksum of FIT image contents"
163 select SHA256
164 default y
165 help
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
173 supported in U-Boot.
174
175 config FIT_SIGNATURE
176 bool "Enable signature verification of FIT uImages"
177 depends on DM
178 select RSA
179 help
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.
185
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.
191
192 config FIT_VERBOSE
193 bool "Show verbose messages when FIT images fail"
194 help
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
198 failures.
199
200 config FIT_BEST_MATCH
201 bool "Select the best match for the kernel device tree"
202 help
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.
208
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
212 help
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).
222
223 if SPL
224
225 config SPL_FIT
226 bool "Support Flattened Image Tree within SPL"
227 depends on SPL
228 select SPL_OF_LIBFDT
229
230 config SPL_FIT_SIGNATURE
231 bool "Enable signature verification of FIT firmware within SPL"
232 depends on SPL_DM
233 select SPL_FIT
234 select SPL_RSA
235
236 config SPL_LOAD_FIT
237 bool "Enable SPL loading U-Boot as a FIT"
238 select SPL_FIT
239 help
240 Normally with the SPL framework a legacy image is generated as part
241 of the build. This contains U-Boot along with information as to
242 where it should be loaded. This option instead enables generation
243 of a FIT (Flat Image Tree) which provides more flexibility. In
244 particular it can handle selecting from multiple device tree
245 and passing the correct one to U-Boot.
246
247 config SPL_FIT_IMAGE_POST_PROCESS
248 bool "Enable post-processing of FIT artifacts after loading by the SPL"
249 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
250 help
251 Allows doing any sort of manipulation to blobs after they got extracted
252 from the U-Boot FIT image like stripping off headers or modifying the
253 size of the blob, verification, authentication, decryption etc. in a
254 platform or board specific way. In order to use this feature a platform
255 or board-specific implementation of board_fit_image_post_process() must
256 be provided. Also, anything done during this post-processing step would
257 need to be comprehended in how the images were prepared before being
258 injected into the FIT creation (i.e. the blobs would have been pre-
259 processed before being added to the FIT image).
260
261 config SPL_FIT_SOURCE
262 string ".its source file for U-Boot FIT image"
263 depends on SPL_FIT
264 help
265 Specifies a (platform specific) FIT source file to generate the
266 U-Boot FIT image. This could specify further image to load and/or
267 execute.
268
269 config SPL_FIT_GENERATOR
270 string ".its file generator script for U-Boot FIT image"
271 depends on SPL_FIT
272 default "board/sunxi/mksunxi_fit_atf.sh" if SPL_LOAD_FIT && ARCH_SUNXI
273 help
274 Specifies a (platform specific) script file to generate the FIT
275 source file used to build the U-Boot FIT image file. This gets
276 passed a list of supported device tree file stub names to
277 include in the generated image.
278
279 endif # SPL
280
281 endif # FIT
282
283 config OF_BOARD_SETUP
284 bool "Set up board-specific details in device tree before boot"
285 depends on OF_LIBFDT
286 help
287 This causes U-Boot to call ft_board_setup() before booting into
288 the Operating System. This function can set up various
289 board-specific information in the device tree for use by the OS.
290 The device tree is then passed to the OS.
291
292 config OF_SYSTEM_SETUP
293 bool "Set up system-specific details in device tree before boot"
294 depends on OF_LIBFDT
295 help
296 This causes U-Boot to call ft_system_setup() before booting into
297 the Operating System. This function can set up various
298 system-specific information in the device tree for use by the OS.
299 The device tree is then passed to the OS.
300
301 config OF_STDOUT_VIA_ALIAS
302 bool "Update the device-tree stdout alias from U-Boot"
303 depends on OF_LIBFDT
304 help
305 This uses U-Boot's serial alias from the aliases node to update
306 the device tree passed to the OS. The "linux,stdout-path" property
307 in the chosen node is set to point to the correct serial node.
308 This option currently references CONFIG_CONS_INDEX, which is
309 incorrect when used with device tree as this option does not
310 exist / should not be used.
311
312 config SYS_EXTRA_OPTIONS
313 string "Extra Options (DEPRECATED)"
314 help
315 The old configuration infrastructure (= mkconfig + boards.cfg)
316 provided the extra options field. If you have something like
317 "HAS_BAR,BAZ=64", the optional options
318 #define CONFIG_HAS
319 #define CONFIG_BAZ 64
320 will be defined in include/config.h.
321 This option was prepared for the smooth migration from the old
322 configuration to Kconfig. Since this option will be removed sometime,
323 new boards should not use this option.
324
325 config SYS_TEXT_BASE
326 depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
327 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
328 ARCH_ZYNQ || ARCH_KEYSTONE
329 depends on !EFI_APP
330 hex "Text Base"
331 help
332 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
333
334
335 config SYS_CLK_FREQ
336 depends on ARC || ARCH_SUNXI
337 int "CPU clock frequency"
338 help
339 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
340
341 config ARCH_FIXUP_FDT_MEMORY
342 bool "Enable arch_fixup_memory_banks() call"
343 default y
344 help
345 Enable FDT memory map syncup before OS boot. This feature can be
346 used for booting OS with different memory setup where the part of
347 the memory location should be used for different purpose.
348
349 endmenu # Boot images
350
351 source "api/Kconfig"
352
353 source "common/Kconfig"
354
355 source "cmd/Kconfig"
356
357 source "disk/Kconfig"
358
359 source "dts/Kconfig"
360
361 source "net/Kconfig"
362
363 source "drivers/Kconfig"
364
365 source "fs/Kconfig"
366
367 source "lib/Kconfig"
368
369 source "test/Kconfig"
370
371 source "scripts/Kconfig"