Lines Matching +full:as +full:- +full:is
17 If you want to build SPL as well as the normal image, say 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
36 in SPL (or TPL if that is being used).
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"
53 used to pass information like the size of SDRAM from SPL to U-Boot
55 if that is enabled.
59 default "arch/$(ARCH)/cpu/u-boot-spl.lds"
61 The SPL stage will usually require a different linker-script
62 (as it runs from a different memory region) than the regular
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
88 On some boards, which use 'falcon' mode, it is necessary to check
90 use proper U-Boot for normal boot flow and hence needs those
99 is y. If this is not set, SPL will move on to other available
107 is y. If this is not set, SPL will move on to other available
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.
143 function, it is possible for the stack to move there before
144 board_init_r() is reached. This option enables a special SDRAM
145 location for the SPL stack. U-Boot SPL switches to this after
154 before board_init_r() is called.
161 Specify the amount of the stack to use as memory pool for
164 SRAM which is limited to SYS_MALLOC_F_LEN bytes.
167 bool "BSS section is in a different memory region from text"
170 because RAM is already set up. In this case BSS can be moved to RAM.
172 location is used. Normally we put the device tree at the end of BSS
176 bool "Enable output of the SPL banner 'U-Boot SPL ...'"
179 If this option is enabled, SPL will print the banner with version
184 bool "Enable output of the TPL banner 'U-Boot TPL ...'"
187 If this option is enabled, SPL will not print the banner with version
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
220 Use sector number for specifying U-Boot location on MMC/SD in
224 hex "Address on the MMC to load U-Boot from"
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"
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
272 This is a 32-bit checksum value that can be used to verify images.
273 For FIT images, this is the least secure type of checksum, suitable
282 checksum is a 128-bit hash value used to check that the image
283 contents have not been corrupted. Note that MD5 is not considered
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
297 While SHA1 is fairly secure it is coming to the end of its life
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
338 in SPL, if space for the SPL binary is very tight.
341 first image to be treated as having a U-Boot style calling
344 ensure this information is available to the next image
351 up CPUs and provide information about them such as the model and
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
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
390 in drivers/dma as part of an SPL build.
397 option to build the drivers in drivers/misc as part of an SPL
403 Enable environment support in SPL. The U-Boot environment provides
405 control many aspects of U-Boot's operation. Normally this is not
406 needed in SPL as it has a much simpler task with less
409 starting U-Boot first. Enabling this option will make env_get()
418 the saveenv option is not provided in SPL, but some boards need
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
433 is required since the network stack uses a number of environment
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
465 implement peripherals (such as UARTs, LCD displays, MMC) or
466 accelerate custom processing functions, such as image processing
467 or machine learning. Sometimes it is useful to program the FPGA
468 as early as possible during boot, and this option can enable that
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,
480 drivers/gpio as part of an SPL build.
485 Enable support for the I2C (Inter-Integrated Circuit) bus in SPL.
487 one or more masters or slaves. It is a fairly complex bus but is
488 widely used as it only needs two lines for communication. Speeds of
489 400kbps are typical but up to 3.4Mbps is supported by some
492 Enable this option to build the drivers in drivers/i2c as part of
498 Enable support for common U-Boot libraries within SPL. These
499 libraries include common code to deal with U-Boot images,
500 environment and USB, for example. This option is enabled on many
501 boards. Enable this option to build the code in common/ as part of
508 Enable support for disk partitions within SPL. 'Disk' is something
509 of a misnomer as it includes non-spinning media such as flash (as
513 'partition'. These partitions are typically uses as individual block
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
523 printf(), compression and the like. This option is enabled on many
524 boards. Enable this option to build the code in lib/ as part of an
532 this option to build the drivers in drivers/mailbox as part of
544 this option to build the drivers in drivers/mmc as part of an SPL
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
575 Enable support for Mentor Graphics USB in SPL. This is a new
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.
585 This enables the drivers in drivers/mtd/nand/raw as part of an SPL
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
601 As defined by RFC 2132 the vendor class identifier field can be
603 of a client. This is often used in practice to allow for the DHCP
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
620 OR) flash in SPL. NOR flash is slow to write but fast to read, and
621 a memory-mapped device makes it very easy to access. Loading from
622 NOR is typically achieved with just a memcpy().
628 Enable support for execute in place of U-Boot or kernel image. There
629 is no need to copy image from flash to ram if flash supports execute
636 Enable support for OneNAND (Negative AND) flash in SPL. OneNAND is
638 load U-Boot from supported devices. This enables the drivers in
639 drivers/mtd/onenand as part of an SPL build.
651 hex "addr, where OS is found"
654 Specify the address, where the OS image is found, which
661 default "tpl/u-boot-with-tpl.bin" if TPL
662 default "u-boot.bin"
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.
682 boot. This enables the drivers in drivers/pch as part of an SPL
688 Enable support for POST (Power-on Self Test) in SPL. POST is a
690 be functionally correctly. It is a sanity check that can be
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.
749 Enable RTC (Real-time Clock) support in SPL. This includes support
751 non-volatile (battery-backed) memory which is accessible if
752 needed. This enables the drivers in drivers/rtc as part of an SPL
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
771 for displaying messages while SPL is running. It also brings in
774 enabling USE_TINY_PRINTF which is a small printf() version.
779 Enable support for using SPI flash in SPL, and loading U-Boot from
780 SPI flash. SPI flash (Serial Peripheral Bus flash) is named after
781 the SPI bus that is used to connect it to a system. It is a simple
782 but fast bidirectional 4-wire bus (clock, chip select and two data
783 lines). This enables the drivers in drivers/mtd/spi as part of an
804 tables as per JESD216 standard in SPL.
809 Enable support for loading next stage, U-Boot or otherwise, from
810 SPI NOR in U-Boot SPL.
817 Enable support for using SPI in SPL. This is used for connecting
818 to SPI flash for loading U-Boot. See SPL_SPI_FLASH_SUPPORT for
822 as a SPI PMIC.
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
837 SPL can load U-Boot from a connected USB peripheral, such as a USB
839 buses, it is very flexible since many different types of storage
841 drivers/usb/host as part of an SPL build.
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
867 than from an onboard peripheral. Environment support is required
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.
903 using the same protocol as implemented by the i.MX family's boot ROM.
909 Enable support for watchdog drivers in SPL. A watchdog is
911 detects no activity for a while (such as a software crash). This
912 enables the drivers in drivers/watchdog as part of an SPL build.
918 While loading from serial is slow it can be a useful backup when
919 there is no other option. The Ymodem protocol provides a reliable
920 means of transmitting U-Boot over a serial line for using in SPL,
927 ATF(ARM Trusted Firmware) is a component for ARM AArch64 which
928 is loaded by SPL (which is considered as BL2 in ATF terminology).
929 More detail at: https://github.com/ARM-software/arm-trusted-firmware
936 as the platform parameter to an ATF, some ATF versions are
937 not U-Boot aware and have an insufficiently robust parameter
940 If this option is enabled, the spl_atf os-type handler will
943 If your ATF is affected, say Y.
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"
974 used to pass information like the size of SDRAM from TPL to U-Boot
975 proper. The information is also available to SPL if it is useful
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
992 (as it runs from a different memory region) than the regular
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"
1004 Enable, if the TPL stage should not inherit its text-base
1009 bool "TPL needs a separate initial stack-pointer"
1014 stack-pointer from the settings for the SPL stage.
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
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,
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.
1119 boot. This enables the drivers in drivers/pch as part of a TPL
1139 Enable RTC (Real-time Clock) support in TPL. This includes support
1141 non-volatile (battery-backed) memory which is accessible if
1142 needed. This enables the drivers in drivers/rtc as part of an TPL
1163 Enable support for loading next stage, U-Boot or otherwise, from
1164 SPI NOR in U-Boot TPL.
1176 While loading from serial is slow it can be a useful backup when
1177 there is no other option. The Ymodem protocol provides a reliable
1178 means of transmitting U-Boot over a serial line for using in TPL,