Lines Matching +full:os +full:- +full:code +full:- +full:offset
3 # see the file Documentation/kbuild/kconfig-language.txt in the
6 mainmenu "U-Boot $UBOOTVERSION Configuration"
12 # Allow defaults in arch-specific code to override any given here
24 string "Local version - append to U-Boot release"
26 Append an extra string to the end of your U-Boot version.
41 A string of the format -gxxxxxxxx will be added to the localversion
42 if a Git-based tree is found. The string generated by this will be
49 $ git rev-parse --verify HEAD
57 Enabling this option will pass "-Os" instead of "-O2" to gcc
58 resulting in a smaller U-Boot image.
60 This option is enabled by default for U-Boot.
63 bool "Enable code coverage analysis"
66 Enabling this option will pass "--coverage" to gcc to compile
67 and link code instrumented for coverage analysis.
93 for building u-boot for booting general purpose Linux distributions.
99 U-Boot build configuration to the default environment.
102 - CONFIG_SYS_ARCH
103 - CONFIG_SYS_CPU
104 - CONFIG_SYS_BOARD
105 - CONFIG_SYS_VENDOR
106 - CONFIG_SYS_SOC
176 bool "Configure standard U-Boot features (expert users)"
179 This option allows certain base U-Boot options and settings
181 environments which can tolerate a "non-standard" U-Boot.
199 should be replaced by calloc - if one expects zeroed memory.
206 it is possible to set breakpoints on particular lines, single-step
207 debug through the source code, etc.
219 bool "Build U-Boot as BIOS replacement"
222 This option allows to build a ROM version of U-Boot.
224 which are not shipped in the U-Boot source tree.
229 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_ARRIA10
230 default "u-boot-with-spl.sfp" if TARGET_SOCFPGA_GEN5
231 default "u-boot-spl.kwb" if ARCH_MVEBU && SPL
232 default "u-boot-elf.srec" if RCAR_GEN3
233 default "u-boot.itb" if SPL_LOAD_FIT && ARCH_SUNXI
234 default "u-boot.kwb" if KIRKWOOD
236 Some SoCs need special image types (e.g. U-Boot binary
273 This specifies a data offset in fit image.
274 The offset is from data payload offset to the beginning of
275 fit image header. When specifies a offset, specific data
285 SHA256 checksum is a 256-bit (32-byte) hash value used to check that
294 SHA384 checksum is a 384-bit (48-byte) hash value used to check that
304 SHA512 checksum is a 512-bit (64-byte) hash value used to check that
336 bool "Support rsassa-pss signature scheme of FIT image contents"
347 are a waste of code space. If you are debugging your images then
356 U-Boot itself. A match is considered "best" if it matches the
357 most specific compatibility entry of U-Boot's fdt's root node.
361 bool "Enable post-processing of FIT artifacts after loading by U-Boot"
367 board specific way. In order to use this feature a platform or board-
369 provided. Also, anything done during this post-processing step would
371 injected into the FIT creation (i.e. the blobs would have been pre-
396 bool "Enable SPL loading U-Boot as a FIT"
400 of the build. This contains U-Boot along with information as to
404 and passing the correct one to U-Boot.
407 bool "Enable SPL loading U-Boot as a FIT"
411 of the build. This contains U-Boot along with information as to
415 and passing the correct one to U-Boot.
418 bool "Enable post-processing of FIT artifacts after loading by the SPL"
422 from the U-Boot FIT image like stripping off headers or modifying the
425 or board-specific implementation of board_fit_image_post_process() must
426 be provided. Also, anything done during this post-processing step would
428 injected into the FIT creation (i.e. the blobs would have been pre-
432 string ".its source file for U-Boot FIT image"
436 U-Boot FIT image. This could specify further image to load and/or
440 string ".its file generator script for U-Boot FIT image"
445 source file used to build the U-Boot FIT image file. This gets
464 bool "Set up board-specific details in device tree before boot"
467 This causes U-Boot to call ft_board_setup() before booting into
469 board-specific information in the device tree for use by the OS.
470 The device tree is then passed to the OS.
473 bool "Set up system-specific details in device tree before boot"
476 This causes U-Boot to call ft_system_setup() before booting into
478 system-specific information in the device tree for use by the OS.
479 The device tree is then passed to the OS.
482 bool "Update the device-tree stdout alias from U-Boot"
485 This uses U-Boot's serial alias from the aliases node to update
486 the device tree passed to the OS. The "linux,stdout-path" property
514 The address in memory that U-Boot will be running from, initially.
528 Enable FDT memory map syncup before OS boot. This feature can be
529 used for booting OS with different memory setup where the part of