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