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 n
61 select CMD_BOOTZ if ARM && !ARM64
62 select CMD_BOOTI if ARM64
63 select CMD_DHCP
64 select CMD_PXE
65 select CMD_EXT2
66 select CMD_EXT4
67 select CMD_FAT
68 select CMD_FS_GENERIC
69 select CMD_MII
70 select CMD_PING
71 select HUSH_PARSER
72 help
73 Select this to enable various options and commands which are suitable
74 for building u-boot for booting general purpose Linux distributions.
75
76config SYS_MALLOC_F
77 bool "Enable malloc() pool before relocation"
78 default y if DM
79 help
80 Before relocation, memory is very limited on many platforms. Still,
81 we can provide a small malloc() pool if needed. Driver model in
82 particular needs this to operate, so that it can allocate the
83 initial serial device and any others that are needed.
84
85config SYS_MALLOC_F_LEN
86 hex "Size of malloc() pool before relocation"
87 depends on SYS_MALLOC_F
88 default 0x400
89 help
90 Before relocation, memory is very limited on many platforms. Still,
91 we can provide a small malloc() pool if needed. Driver model in
92 particular needs this to operate, so that it can allocate the
93 initial serial device and any others that are needed.
94
95config SYS_MALLOC_LEN
96 hex "Define memory for Dynamic allocation"
97 depends on ARCH_ZYNQ
98 help
99 This defines memory to be allocated for Dynamic allocation
100 TODO: Use for other architectures
101
102menuconfig EXPERT
103 bool "Configure standard U-Boot features (expert users)"
104 default y
105 help
106 This option allows certain base U-Boot options and settings
107 to be disabled or tweaked. This is for specialized
108 environments which can tolerate a "non-standard" U-Boot.
109 Use this only if you really know what you are doing.
110
111if EXPERT
112 config SYS_MALLOC_CLEAR_ON_INIT
113 bool "Init with zeros the memory reserved for malloc (slow)"
114 default y
115 help
116 This setting is enabled by default. The reserved malloc
117 memory is initialized with zeros, so first malloc calls
118 will return the pointer to the zeroed memory. But this
119 slows the boot time.
120
121 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
122 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
123 Then the boot time can be significantly reduced.
124 Warning:
125 When disabling this, please check if malloc calls, maybe
126 should be replaced by calloc - if one expects zeroed memory.
127
128config TOOLS_DEBUG
129 bool "Enable debug information for tools"
130 help
131 Enable generation of debug information for tools such as mkimage.
132 This can be used for debugging purposes. With debug information
133 it is possible to set breakpoints on particular lines, single-step
134 debug through the source code, etc.
135
136endif
137
138config PHYS_64BIT
139 bool "64bit physical address support"
140 help
141 Say Y here to support 64bit physical memory address.
142 This can be used not only for 64bit SoCs, but also for
143 large physical address extention on 32bit SoCs.
144
145endmenu
146
147menu "Boot images"
148
149config FIT
150 bool "Support Flattened Image Tree"
151 help
152 This option allows to boot the new uImage structrure,
153 Flattened Image Tree. FIT is formally a FDT, which can include
154 images of various types (kernel, FDT blob, ramdisk, etc.)
155 in a single blob. To boot this new uImage structure,
156 pass the address of the blob to the "bootm" command.
157 FIT is very flexible, supporting compression, multiple images,
158 multiple configurations, verification through hashing and also
159 verified boot (secure boot using RSA). This option enables that
160 feature.
161
162config SPL_FIT
163 bool "Support Flattened Image Tree within SPL"
164 depends on FIT
165 depends on SPL
166
167config FIT_VERBOSE
168 bool "Display verbose messages on FIT boot"
169 depends on FIT
170
171config FIT_SIGNATURE
172 bool "Enable signature verification of FIT uImages"
173 depends on FIT
174 depends on DM
175 select RSA
176 help
177 This option enables signature verification of FIT uImages,
178 using a hash signed and verified using RSA. If
179 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
180 hashing is available using hardware, then then RSA library will use
181 it. See doc/uImage.FIT/signature.txt for more details.
182
183 WARNING: When relying on signed FIT images with a required signature
184 check the legacy image format is disabled by default, so that
185 unsigned images cannot be loaded. If a board needs the legacy image
186 format support in this case, enable it using
187 CONFIG_IMAGE_FORMAT_LEGACY.
188
189config SPL_FIT_SIGNATURE
190 bool "Enable signature verification of FIT firmware within SPL"
191 depends on SPL_FIT
192 depends on SPL_DM
193 select SPL_RSA
194
195config FIT_BEST_MATCH
196 bool "Select the best match for the kernel device tree"
197 depends on FIT
198 help
199 When no configuration is explicitly selected, default to the
200 one whose fdt's compatibility field best matches that of
201 U-Boot itself. A match is considered "best" if it matches the
202 most specific compatibility entry of U-Boot's fdt's root node.
203 The order of entries in the configuration's fdt is ignored.
204
205config FIT_VERBOSE
206 bool "Show verbose messages when FIT images fails"
207 depends on FIT
208 help
209 Generally a system will have valid FIT images so debug messages
210 are a waste of code space. If you are debugging your images then
211 you can enable this option to get more verbose information about
212 failures.
213
214config OF_BOARD_SETUP
215 bool "Set up board-specific details in device tree before boot"
216 depends on OF_LIBFDT
217 help
218 This causes U-Boot to call ft_board_setup() before booting into
219 the Operating System. This function can set up various
220 board-specific information in the device tree for use by the OS.
221 The device tree is then passed to the OS.
222
223config OF_SYSTEM_SETUP
224 bool "Set up system-specific details in device tree before boot"
225 depends on OF_LIBFDT
226 help
227 This causes U-Boot to call ft_system_setup() before booting into
228 the Operating System. This function can set up various
229 system-specific information in the device tree for use by the OS.
230 The device tree is then passed to the OS.
231
232config OF_STDOUT_VIA_ALIAS
233 bool "Update the device-tree stdout alias from U-Boot"
234 depends on OF_LIBFDT
235 help
236 This uses U-Boot's serial alias from the aliases node to update
237 the device tree passed to the OS. The "linux,stdout-path" property
238 in the chosen node is set to point to the correct serial node.
239 This option currently references CONFIG_CONS_INDEX, which is
240 incorrect when used with device tree as this option does not
241 exist / should not be used.
242
243config SYS_EXTRA_OPTIONS
244 string "Extra Options (DEPRECATED)"
245 help
246 The old configuration infrastructure (= mkconfig + boards.cfg)
247 provided the extra options field. If you have something like
248 "HAS_BAR,BAZ=64", the optional options
249 #define CONFIG_HAS
250 #define CONFIG_BAZ 64
251 will be defined in include/config.h.
252 This option was prepared for the smooth migration from the old
253 configuration to Kconfig. Since this option will be removed sometime,
254 new boards should not use this option.
255
256config SYS_TEXT_BASE
257 depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
258 ARCH_ZYNQ || (M68K && !TARGET_ASTRO_MCF5373L) || \
259 MICROBLAZE || MIPS
260 depends on !EFI_APP
261 hex "Text Base"
262 help
263 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
264
265config SPL_LOAD_FIT
266 bool "Enable SPL loading U-Boot as a FIT"
267 depends on FIT
268 help
269 Normally with the SPL framework a legacy image is generated as part
270 of the build. This contains U-Boot along with information as to
271 where it should be loaded. This option instead enables generation
272 of a FIT (Flat Image Tree) which provides more flexibility. In
273 particular it can handle selecting from multiple device tree
274 and passing the correct one to U-Boot.
275
276config SPL_FIT_IMAGE_POST_PROCESS
277 bool "Enable post-processing of FIT artifacts after loading by the SPL"
278 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
279 help
280 Allows doing any sort of manipulation to blobs after they got extracted
281 from the U-Boot FIT image like stripping off headers or modifying the
282 size of the blob, verification, authentication, decryption etc. in a
283 platform or board specific way. In order to use this feature a platform
284 or board-specific implementation of board_fit_image_post_process() must
285 be provided. Also, anything done during this post-processing step would
286 need to be comprehended in how the images were prepared before being
287 injected into the FIT creation (i.e. the blobs would have been pre-
288 processed before being added to the FIT image).
289
290config FIT_IMAGE_POST_PROCESS
291 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
292 depends on FIT && TI_SECURE_DEVICE
293 help
294 Allows doing any sort of manipulation to blobs after they got extracted
295 from FIT images like stripping off headers or modifying the size of the
296 blob, verification, authentication, decryption etc. in a platform or
297 board specific way. In order to use this feature a platform or board-
298 specific implementation of board_fit_image_post_process() must be
299 provided. Also, anything done during this post-processing step would
300 need to be comprehended in how the images were prepared before being
301 injected into the FIT creation (i.e. the blobs would have been pre-
302 processed before being added to the FIT image).
303
304config SYS_CLK_FREQ
305 depends on ARC || ARCH_SUNXI
306 int "CPU clock frequency"
307 help
308 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
309
310config ARCH_FIXUP_FDT_MEMORY
311 bool "Enable arch_fixup_memory_banks() call"
312 default y
313 help
314 Enable FDT memory map syncup before OS boot. This feature can be
315 used for booting OS with different memory setup where the part of
316 the memory location should be used for different purpose.
317
318endmenu
319
320source "common/Kconfig"
321
322source "cmd/Kconfig"
323
324source "dts/Kconfig"
325
326source "net/Kconfig"
327
328source "drivers/Kconfig"
329
330source "fs/Kconfig"
331
332source "lib/Kconfig"
333
334source "test/Kconfig"
335
