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