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.
6 mainmenu "U-Boot $UBOOTVERSION Configuration"
10 option env="UBOOTVERSION"
12 # Allow defaults in arch-specific code to override any given here
18 string "Local version - append to U-Boot release"
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.
27 config LOCALVERSION_AUTO
28 bool "Automatically append version information to the version string"
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
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.
40 (The actual string used here is the first eight characters produced
41 by running the command:
43 $ git rev-parse --verify HEAD
45 which is done within the script "scripts/setlocalversion".)
47 config CC_OPTIMIZE_FOR_SIZE
48 bool "Optimize for size"
51 Enabling this option will pass "-Os" instead of "-O2" to gcc
52 resulting in a smaller U-Boot image.
54 This option is enabled by default for U-Boot.
56 config DISTRO_DEFAULTS
57 bool "Select defaults suitable for booting general purpose Linux distributions"
58 default y if ARCH_SUNXI
59 default y if ARCH_LS2080A
61 select CMD_BOOTZ if ARM && !ARM64
62 select CMD_BOOTI if ARM64
72 Select this to enable various options and commands which are suitable
73 for building u-boot for booting general purpose Linux distributions.
76 bool "Enable malloc() pool before relocation"
79 Before relocation, memory is very limited on many platforms. Still,
80 we can provide a small malloc() pool if needed. Driver model in
81 particular needs this to operate, so that it can allocate the
82 initial serial device and any others that are needed.
84 config SYS_MALLOC_F_LEN
85 hex "Size of malloc() pool before relocation"
86 depends on SYS_MALLOC_F
89 Before relocation, memory is very limited on many platforms. Still,
90 we can provide a small malloc() pool if needed. Driver model in
91 particular needs this to operate, so that it can allocate the
92 initial serial device and any others that are needed.
95 bool "Configure standard U-Boot features (expert users)"
98 This option allows certain base U-Boot options and settings
99 to be disabled or tweaked. This is for specialized
100 environments which can tolerate a "non-standard" U-Boot.
101 Use this only if you really know what you are doing.
104 config SYS_MALLOC_CLEAR_ON_INIT
105 bool "Init with zeros the memory reserved for malloc (slow)"
108 This setting is enabled by default. The reserved malloc
109 memory is initialized with zeros, so first malloc calls
110 will return the pointer to the zeroed memory. But this
113 It is recommended to disable it, when CONFIG_SYS_MALLOC_LEN
114 value, has more than few MiB, e.g. when uses bzip2 or bmp logo.
115 Then the boot time can be significantly reduced.
117 When disabling this, please check if malloc calls, maybe
118 should be replaced by calloc - if one expects zeroed memory.
121 bool "Enable debug information for tools"
123 Enable generation of debug information for tools such as mkimage.
124 This can be used for debugging purposes. With debug information
125 it is possible to set breakpoints on particular lines, single-step
126 debug through the source code, etc.
131 bool "64bit physical address support"
133 Say Y here to support 64bit physical memory address.
134 This can be used not only for 64bit SoCs, but also for
135 large physical address extention on 32bit SoCs.
137 endmenu # General setup
142 bool "Support Flattened Image Tree"
144 This option allows to boot the new uImage structrure,
145 Flattened Image Tree. FIT is formally a FDT, which can include
146 images of various types (kernel, FDT blob, ramdisk, etc.)
147 in a single blob. To boot this new uImage structure,
148 pass the address of the blob to the "bootm" command.
149 FIT is very flexible, supporting compression, multiple images,
150 multiple configurations, verification through hashing and also
151 verified boot (secure boot using RSA). This option enables that
155 bool "Support Flattened Image Tree within SPL"
160 bool "Display verbose messages on FIT boot"
164 bool "Enable signature verification of FIT uImages"
169 This option enables signature verification of FIT uImages,
170 using a hash signed and verified using RSA. If
171 CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
172 hashing is available using hardware, then then RSA library will use
173 it. See doc/uImage.FIT/signature.txt for more details.
175 WARNING: When relying on signed FIT images with a required signature
176 check the legacy image format is disabled by default, so that
177 unsigned images cannot be loaded. If a board needs the legacy image
178 format support in this case, enable it using
179 CONFIG_IMAGE_FORMAT_LEGACY.
181 config SPL_FIT_SIGNATURE
182 bool "Enable signature verification of FIT firmware within SPL"
187 config FIT_BEST_MATCH
188 bool "Select the best match for the kernel device tree"
191 When no configuration is explicitly selected, default to the
192 one whose fdt's compatibility field best matches that of
193 U-Boot itself. A match is considered "best" if it matches the
194 most specific compatibility entry of U-Boot's fdt's root node.
195 The order of entries in the configuration's fdt is ignored.
198 bool "Show verbose messages when FIT images fails"
201 Generally a system will have valid FIT images so debug messages
202 are a waste of code space. If you are debugging your images then
203 you can enable this option to get more verbose information about
206 config OF_BOARD_SETUP
207 bool "Set up board-specific details in device tree before boot"
210 This causes U-Boot to call ft_board_setup() before booting into
211 the Operating System. This function can set up various
212 board-specific information in the device tree for use by the OS.
213 The device tree is then passed to the OS.
215 config OF_SYSTEM_SETUP
216 bool "Set up system-specific details in device tree before boot"
219 This causes U-Boot to call ft_system_setup() before booting into
220 the Operating System. This function can set up various
221 system-specific information in the device tree for use by the OS.
222 The device tree is then passed to the OS.
224 config OF_STDOUT_VIA_ALIAS
225 bool "Update the device-tree stdout alias from U-Boot"
228 This uses U-Boot's serial alias from the aliases node to update
229 the device tree passed to the OS. The "linux,stdout-path" property
230 in the chosen node is set to point to the correct serial node.
231 This option currently references CONFIG_CONS_INDEX, which is
232 incorrect when used with device tree as this option does not
233 exist / should not be used.
235 config SYS_EXTRA_OPTIONS
236 string "Extra Options (DEPRECATED)"
238 The old configuration infrastructure (= mkconfig + boards.cfg)
239 provided the extra options field. If you have something like
240 "HAS_BAR,BAZ=64", the optional options
242 #define CONFIG_BAZ 64
243 will be defined in include/config.h.
244 This option was prepared for the smooth migration from the old
245 configuration to Kconfig. Since this option will be removed sometime,
246 new boards should not use this option.
249 depends on SPARC || ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
250 (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS
254 TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
257 bool "Enable SPL loading U-Boot as a FIT"
260 Normally with the SPL framework a legacy image is generated as part
261 of the build. This contains U-Boot along with information as to
262 where it should be loaded. This option instead enables generation
263 of a FIT (Flat Image Tree) which provides more flexibility. In
264 particular it can handle selecting from multiple device tree
265 and passing the correct one to U-Boot.
267 config SPL_FIT_IMAGE_POST_PROCESS
268 bool "Enable post-processing of FIT artifacts after loading by the SPL"
269 depends on SPL_LOAD_FIT && TI_SECURE_DEVICE
271 Allows doing any sort of manipulation to blobs after they got extracted
272 from the U-Boot FIT image like stripping off headers or modifying the
273 size of the blob, verification, authentication, decryption etc. in a
274 platform or board specific way. In order to use this feature a platform
275 or board-specific implementation of board_fit_image_post_process() must
276 be provided. Also, anything done during this post-processing step would
277 need to be comprehended in how the images were prepared before being
278 injected into the FIT creation (i.e. the blobs would have been pre-
279 processed before being added to the FIT image).
281 config FIT_IMAGE_POST_PROCESS
282 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
283 depends on FIT && TI_SECURE_DEVICE
285 Allows doing any sort of manipulation to blobs after they got extracted
286 from FIT images like stripping off headers or modifying the size of the
287 blob, verification, authentication, decryption etc. in a platform or
288 board specific way. In order to use this feature a platform or board-
289 specific implementation of board_fit_image_post_process() must be
290 provided. Also, anything done during this post-processing step would
291 need to be comprehended in how the images were prepared before being
292 injected into the FIT creation (i.e. the blobs would have been pre-
293 processed before being added to the FIT image).
296 depends on ARC || ARCH_SUNXI
297 int "CPU clock frequency"
299 TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
301 config ARCH_FIXUP_FDT
302 bool "Enable arch_fixup_fdt() call"
303 depends on ARM || MIPS
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.
310 endmenu # Boot images
312 source "common/Kconfig"
320 source "drivers/Kconfig"
326 source "test/Kconfig"