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