Lines Matching +full:build +full:- +full:without +full:- +full:default +full:- +full:devices
17 If you want to build SPL as well as the normal image, say Y.
22 default y
25 supports MMC, NAND and YMODEM and other methods loading of U-Boot
29 bool "Pass hand-off information from SPL to U-Boot proper"
32 It is useful to be able to pass information from SPL to U-Boot
33 proper to preserve state that is known in SPL and is needed in U-Boot.
34 Enable this to locate the handoff information in U-Boot proper, early
35 in boot. It is available in gd->handoff. The state state is set up
44 This option can minilize the SPL size to compatible with AST2600-A0
48 bool "Pass hand-off information from SPL to U-Boot proper"
50 default y
53 used to pass information like the size of SDRAM from SPL to U-Boot
59 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
61 The SPL stage will usually require a different linker-script
63 U-Boot stage. Set this to the path of the linker-script to
67 bool "Call board-specific initialization in SPL"
69 If this option is enabled, U-Boot will call the function
77 ROM for loading the next boot-stage after performing basic setup
81 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
90 use proper U-Boot for normal boot flow and hence needs those
95 default n if (ARCH_MX6 && (SPL_MMC_SUPPORT || SPL_SATA_SUPPORT))
96 default y if !TI_SECURE_DEVICE
104 default y if !TI_SECURE_DEVICE
118 are correct, without further integrity checks.
127 usage as the *_simple malloc functions do not re-use free-ed mem.
136 usage as the *_simple malloc functions do not re-use free-ed mem.
145 location for the SPL stack. U-Boot SPL switches to this after
151 default 0x82000000 if ARCH_OMAP2PLUS
159 default 0x100000
176 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
177 default y
184 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
185 default y
192 bool "Display a board-specific message in SPL"
194 If this option is enabled, U-Boot will call the function
196 banner ("U-Boot SPL ..."). This function should be provided by
201 default y
214 default y if ARCH_SUNXI || ARCH_DAVINCI || ARCH_UNIPHIER || \
220 Use sector number for specifying U-Boot location on MMC/SD in
224 hex "Address on the MMC to load U-Boot from"
226 default 0x50 if ARCH_SUNXI
227 default 0x75 if ARCH_DAVINCI
228 default 0x8a if ARCH_MX6 || ARCH_MX7
229 default 0x100 if ARCH_UNIPHIER
230 default 0x140 if ARCH_MVEBU
231 default 0x200 if ARCH_SOCFPGA || ARCH_AT91
232 default 0x300 if ARCH_ZYNQ || ARCH_KEYSTONE || OMAP34XX || OMAP44XX || \
234 default 0x4000 if ARCH_ROCKCHIP
236 Address on the MMC to load U-Boot from, when the MMC is being used
242 Use a partition for loading U-Boot when using MMC/SD in raw mode.
245 hex "Partition to use to load U-Boot from"
247 default 1
249 Partition on the MMC to load U-Boot from when the MMC is being
256 Use partition type for specifying U-Boot partition on MMC/SD in
257 raw mode. U-Boot will be loaded from the first partition of this
261 hex "Partition Type on the MMC to load U-Boot from"
264 Partition Type on the MMC to load U-Boot from, when the MMC is being
269 default y if SPL_LEGACY_IMAGE_SUPPORT
272 This is a 32-bit checksum value that can be used to verify images.
282 checksum is a 128-bit hash value used to check that the image
284 secure as it is possible (with a brute-force attack) to adjust the
295 checksum is a 160-bit (20-byte) hash value used to check that the
298 due to the expanding computing power available to brute-force
307 checksum is a 256-bit (32-byte) hash value used to check that the
317 checksum is a 384-bit (48-byte) hash value used to check that the
328 checksum is a 512-bit (64-byte) hash value used to check that the
334 default y if MACH_SUN50I || MACH_SUN50I_H5 || MACH_SUN50I_H6
335 default y if ARCH_IMX8M
341 first image to be treated as having a U-Boot style calling
353 may improve boot performance. Enable this option to build the
354 drivers in drivers/cpu as part of an SPL build.
361 this option to build the drivers in drivers/crypto as part of an
362 SPL build.
371 this option to build system-specific drivers for hash acceleration
372 as part of an SPL build.
381 this option to build system-specific drivers for hash acceleration
382 as part of an SPL build.
387 Enable DMA (direct-memory-access) drivers in SPL. These drivers
388 can be used to handle memory-to-peripheral data transfer without
389 the CPU moving the data. Enable this option to build the drivers
390 in drivers/dma as part of an SPL build.
397 option to build the drivers in drivers/misc as part of an SPL
398 build, for those that support building in SPL (not all drivers do).
403 Enable environment support in SPL. The U-Boot environment provides
405 control many aspects of U-Boot's operation. Normally this is not
408 on EXT2 and FAT, where SPL boots directly into Linux without
409 starting U-Boot first. Enabling this option will make env_get()
417 Enable save environment support in SPL after setenv. By default
424 to default mode using setenv and save the environment.
431 drivers in SPL. This permits SPL to load U-Boot over an Ethernet
432 link rather than from an on-board peripheral. Environment support
440 U-Boot (or Linux in Falcon mode) to be loaded from an EXT
449 permits U-Boot (or Linux in Falcon mode) to be loaded from a FAT
463 Enable support for FPGAs in SPL. Field-programmable Gate Arrays
464 provide software-configurable hardware which is typically used to
474 Enable support for GPIOs (General-purpose Input/Output) in SPL.
475 GPIOs allow U-Boot to read the state of an input line (high or
478 input. GPIOs can be useful in SPL to enable a 'sign-of-life' LED,
479 for example. Enable this option to build the drivers in
480 drivers/gpio as part of an SPL build.
485 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
492 Enable this option to build the drivers in drivers/i2c as part of
493 an SPL build.
498 Enable support for common U-Boot libraries within SPL. These
499 libraries include common code to deal with U-Boot images,
501 boards. Enable this option to build the code in common/ as part of
502 an SPL build.
509 of a misnomer as it includes non-spinning media such as flash (as
514 devices, typically with an EXT2 or FAT filesystem in each. This
516 U-Boot to also be used in SPL. It brings in the code in disk/.
521 Enable support for generic U-Boot libraries within SPL. These
524 boards. Enable this option to build the code in lib/ as part of an
525 SPL build.
532 this option to build the drivers in drivers/mailbox as part of
533 SPL build.
542 be used within SPL. MMC can be used with or without disk partition
544 this option to build the drivers in drivers/mmc as part of an SPL
545 build.
550 default n
558 Enable support for DDR-SDRAM (double-data-rate synchronous dynamic
559 random-access memory) on the MPC8XXX family within SPL. This
560 allows DRAM to be set up before loading U-Boot into that DRAM,
568 SPI flash. This allows SPL to load U-Boot from supported MTD
569 devices. See SPL_NAND_SUPPORT and SPL_ONENAND_SUPPORT for how
576 driver used by some boards. Enable this option to build
577 the drivers in drivers/usb/musb-new as part of an SPL build. The
584 can be used to allow SPL to load U-Boot from supported devices.
586 build.
591 Enable support for network devices (such as Ethernet) in SPL.
592 This permits SPL to load U-Boot over a network link rather than
593 from an on-board peripheral. Environment support is required since
605 SPL or U-Boot itself makes the request
611 This is specific to the ARM926EJ-S CPU. It disables the standard
612 start.S start-up code, presumably so that a replacement can be
619 Enable support for loading U-Boot from memory-mapped NOR (Negative
621 a memory-mapped device makes it very easy to access. Loading from
628 Enable support for execute in place of U-Boot or kernel image. There
638 load U-Boot from supported devices. This enables the drivers in
639 drivers/mtd/onenand as part of an SPL build.
644 default n
661 default "tpl/u-boot-with-tpl.bin" if TPL
662 default "u-boot.bin"
664 Payload for SPL boot. For backward compatibility, default to
665 u-boot.bin, i.e. RAW image without any header. In case of
666 TPL, tpl/u-boot-with-tpl.bin. For new boards, suggest to
667 use u-boot.img.
675 as part of an SPL build.
680 Enable support for PCH (Platform Controller Hub) devices in SPL.
683 build.
688 Enable support for POST (Power-on Self Test) in SPL. POST is a
692 as part of an SPL build.
699 That can be useful in SPL to handle IP reset in driver, as in U-Boot,
701 This enables the drivers in drivers/reset as part of an SPL build.
707 for PMICs (Power-management Integrated Circuits) and some of the
713 as part of an SPL build.
722 the drivers in drivers/power/domain as part of a SPL build.
726 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
734 default y if MICROBLAZE || ARCH_SOCFPGA || TEGRA || ARCH_ZYNQ
749 Enable RTC (Real-time Clock) support in SPL. This includes support
750 for reading and setting the time. Some RTC devices also have some
751 non-volatile (battery-backed) memory which is accessible if
753 build.
759 use of SATA devices such as hard drives and flash drivers for
760 loading U-Boot. SATA is used in higher-end embedded systems and
779 Enable support for using SPI flash in SPL, and loading U-Boot from
782 but fast bidirectional 4-wire bus (clock, chip select and two data
784 SPL build. This normally requires SPL_SPI_SUPPORT.
791 default y if SPI_FLASH
809 Enable support for loading next stage, U-Boot or otherwise, from
810 SPI NOR in U-Boot SPL.
818 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
825 bool "Driver support for thermal devices"
827 Enable support for temperature-sensing devices. Some SoCs have on-chip
829 automatic power-off when the temperature gets too high or low. Other
830 devices may be discrete but connected on a suitable bus.
836 Enable access to USB (Universal Serial Bus) host devices so that
837 SPL can load U-Boot from a connected USB peripheral, such as a USB
841 drivers/usb/host as part of an SPL build.
847 Enable support for USB devices in SPL. This allows use of USB
848 devices such as hard drives and flash drivers for loading U-Boot.
849 The actual drivers are enabled separately using the normal U-Boot
865 drivers in SPL. This permits SPL to load U-Boot over a
866 USB-connected Ethernet link (such as a USB Ethernet dongle) rather
879 the SPL built with dfu. The user can load binaries (u-boot/kernel) to
880 selected device partition from host-pc using dfu-utils.
881 This feature is useful to flash the binaries to factory or bare-metal
893 (u-boot/kernel) to the selected device partition using
894 DFU and execute the u-boot/kernel from RAM.
912 enables the drivers in drivers/watchdog as part of an SPL build.
920 means of transmitting U-Boot over a serial line for using in SPL,
929 More detail at: https://github.com/ARM-software/arm-trusted-firmware
937 not U-Boot aware and have an insufficiently robust parameter
940 If this option is enabled, the spl_atf os-type handler will
947 default y if AM33XX
953 bool "Support OP-TEE Trusted OS"
956 OP-TEE is an open source Trusted OS which is loaded by SPL.
957 More detail at: https://github.com/OP-TEE/optee_os
964 If you want to build TPL as well as the normal image and SPL, say Y.
969 bool "Pass hand-off information from TPL to SPL and U-Boot proper"
971 default y
974 used to pass information like the size of SDRAM from TPL to U-Boot
979 bool "Call board-specific initialization in TPL"
981 If this option is enabled, U-Boot will call the function
988 default "arch/arm/cpu/armv8/u-boot-spl.lds" if ARM64
989 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
991 The TPL stage will usually require a different linker-script
993 U-Boot stage. Set this to the path of the linker-script to
997 fall back to the linker-script used for the SPL stage.
1000 bool "TPL needs a separate text-base"
1001 default n
1004 Enable, if the TPL stage should not inherit its text-base
1009 bool "TPL needs a separate initial stack-pointer"
1010 default n
1014 stack-pointer from the settings for the SPL stage.
1024 default 0
1030 hex "Address of the initial stack-pointer for the TPL stage"
1033 The address of the initial stack-pointer for the TPL stage.
1034 Usually this will be the (aligned) top-of-stack.
1040 ROM for loading the next boot-stage after performing basic setup
1044 BOOT_DEVICE_BOOTROM (or fall-through to the next boot device in the
1052 option to build the drivers in drivers/misc as part of an TPL
1053 build, for those that support building in TPL (not all drivers do).
1063 Enable support for GPIOs (General-purpose Input/Output) in TPL.
1064 GPIOs allow U-Boot to read the state of an input line (high or
1067 input. GPIOs can be useful in TPL to enable a 'sign-of-life' LED,
1068 for example. Enable this option to build the drivers in
1069 drivers/gpio as part of an TPL build.
1080 Enable support for common U-Boot libraries within TPL. See
1086 Enable support for generic U-Boot libraries within TPL. See
1092 Enable support for DDR-SDRAM on the MPC8XXX family within TPL. See
1112 as part of a TPL build.
1117 Enable support for PCH (Platform Controller Hub) devices in TPL.
1120 build.
1139 Enable RTC (Real-time Clock) support in TPL. This includes support
1140 for reading and setting the time. Some RTC devices also have some
1141 non-volatile (battery-backed) memory which is accessible if
1143 build.
1163 Enable support for loading next stage, U-Boot or otherwise, from
1164 SPI NOR in U-Boot TPL.
1178 means of transmitting U-Boot over a serial line for using in TPL,