| /openbmc/qemu/include/hw/riscv/ |
| H A D | boot_opensbi.h | 31 /** Representation dynamic info passed by previous booting stage */
37 /** Next booting stage address */
39 /** Next booting stage mode */
46 * It is possible that the previous booting stage uses same link
48 * lottery mechanism can potentially overwrite the previous booting
49 * stage while other HARTs are still running in the previous booting
51 * the previous booting stage can specify last HART that will jump
54 * To avoid specifying a preferred boot HART, the previous booting
61 /** Representation dynamic info passed by previous booting stage */
67 /** Next booting stage address */
[all …]
|
| /openbmc/u-boot/arch/arm/mach-omap2/ |
| H A D | config.mk | 12 # For booting spl from SD/MMC/eMMC use
15 # For booting spl over UART or USB use
18 # For booting spl from QSPI or NOR use
27 # For booting spl from SPI flash use
30 # For booting spl from all other media use
38 # For booting spl from SPI flash use
41 # For booting spl from NAND flash or raw SD/MMC/eMMC use
44 # For booting spl from a filesystem on SD/MMC/eMMC use
47 # For booting spl over UART, USB, or Ethernet use
|
| /openbmc/u-boot/board/freescale/mx6sabresd/ |
| H A D | README | 4 The following methods can be used for booting mx6sabresd boards:
6 1. Booting from SD card
8 2. Booting from eMMC
10 3. Booting via Falcon mode (SPL launches the kernel directly)
13 1. Booting from SD card via SPL
35 2. Booting from eMMC
62 3. Booting via Falcon mode
|
| /openbmc/u-boot/arch/arm/cpu/armv7/ |
| H A D | Kconfig | 13 bool "Enable support for booting in non-secure mode" if EXPERT
17 Say Y here to enable support for booting in non-secure / SVC mode.
26 suppport booting in non-secure mode. Only set this if you need it.
35 Say Y here to boot in hypervisor (HYP) mode when booting non-secure.
|
| /openbmc/qemu/docs/system/ |
| H A D | bootindex.rst | 12 firmware will consider devices for booting the guest OS. If the
15 ``bootindex`` property set will be considered for booting, but they
52 booting. For instance, the x86 PC BIOS boot specification allows only one
54 won't retry booting from other disk. It can still try to boot from
61 booting, and the same option ROM is used for booting from more then one
|
| /openbmc/u-boot/tools/ |
| H A D | ast2600_ubimg_gen.sh | 4 echo "AST2600 UART booting Image Generator"
6 echo "This script is used to generate a booting image with"
7 echo "the AST2600 UART booting header pre-appended. This is"
|
| /openbmc/u-boot/doc/ |
| H A D | README.mpc85xx-sd-spi-boot | 2 Booting from On-Chip ROM (eSDHC or eSPI)
8 When booting from an SD card/MMC, boot_format puts the configuration file and
10 When booting from an EEPROM, boot_format generates a binary image that is used
46 Example: To generate a u-boot.bin for a P1022DS booting from SD, run the
|
| /openbmc/u-boot/arch/arm/mach-omap2/omap5/ |
| H A D | Kconfig | 84 option for booting.
98 option for booting and choose this when unsure about other OPPs .
122 option for booting and choose this when unsure about other OPPs .
146 option for booting and choose this when unsure about other OPPs .
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/packagegroups/ |
| H A D | packagegroup-boot.bb | 1 SUMMARY = "Basic task to get a device booting"
8 # those ones can be set in machine config to supply packages needed to get machine booting
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | howto.txt | 24 its various properties used during booting. By convention, image source file
41 Here's a graphical overview of the image creation and booting process:
69 Example 1 -- old-style (non-FDT) kernel booting
110 for completeness -- they are part of the standard booting procedure and not
153 ## Booting kernel from FIT Image at 00900000 ...
181 Example 2 -- new-style (FDT) kernel booting
279 ## Booting kernel from FIT Image at 00900000 ...
311 Booting using the fdt blob at 0xa0abdc
317 Example 3 -- advanced booting
321 sophisticated booting scenarios (multiple kernels, ramdisks and fdt blobs).
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 4 Booting with bootindex parameter
11 So for booting an s390x guest in QEMU, you should always mark the
23 For booting from a CD-ROM ISO image (which needs to include El-Torito boot
36 Booting without bootindex parameter
107 Booting from a network device
112 important for booting via the network. If you don't specify the ``bootindex``
|
| /openbmc/u-boot/include/configs/ |
| H A D | pepper.h | 43 "uimageboot=echo Booting from mmc${mmcdev} ...; " \
46 "mmcboot=echo Booting from mmc ...; " \
49 "ubiboot=echo Booting from nand (ubifs) ...; " \
|
| H A D | omap3_logic.h | 122 "mmcbootcommon=echo Booting with DT from mmc${mmcdev} ...; " \
134 "mmcrambootcommon=echo 'Booting kernel from MMC w/ramdisk...'; " \
147 "tftpboot=echo 'Booting kernel/ramdisk rootfs from tftp...'; " \
154 "tftpbootz=echo 'Booting kernel NFS rootfs...'; " \
161 "nandbootcommon=echo 'Booting kernel from NAND...';" \
|
| H A D | socfpga_sr1500.h | 13 /* Booting Linux */
24 /* Enable SPI NOR flash reset, needed for SPI booting */
|
| /openbmc/u-boot/arch/arm/include/asm/mach-imx/ |
| H A D | imximage.cfg | 18 /* Specific image header offset for booting from OneNAND. */
20 /* Specific image header offset for booting from memory-mapped NOR. */
|
| /openbmc/u-boot/board/lego/ev3/ |
| H A D | README | 8 Booting
27 * If none of the above was successful, try booting from flash
50 If you are booting from the microSD card, it is enough to just write uboot.bin
|
| /openbmc/qemu/tests/functional/ |
| H A D | test_aarch64_sbsaref.py | 85 wait_for_console_pattern(self, "Booting Trusted Firmware")
87 wait_for_console_pattern(self, "BL1: Booting BL2")
91 wait_for_console_pattern(self, "Booting BL31")
|
| /openbmc/openbmc/poky/meta/recipes-core/images/ |
| H A D | core-image-minimal-initramfs.bb | 2 SUMMARY = "Small image capable of booting a device."
3 DESCRIPTION = "Small image capable of booting a device. The kernel includes \
|
| /openbmc/u-boot/doc/SPL/ |
| H A D | README.am335x-network | 4 have support for booting via network in ROM. The following describes
5 how to setup network booting and then optionally use this support to flash
13 SPL with support for booting over the network. Also you have to enable
18 comes with support for network booting preconfigured.
|
| /openbmc/openbmc/meta-ampere/meta-common/recipes-ampere/host/ac01-boot-progress/ |
| H A D | ampere_boot_progress.sh | 94 boot_stage_str="UEFI booting (UEFI Code=${ueficode})"
97 boot_stage_str="OS booting"
139 REDFISH_MESSAGE_ARGS="UEFI firmware booting done"
205 # Stop the service when booting to OS
|
| /openbmc/u-boot/board/qualcomm/dragonboard820c/ |
| H A D | head.S | 9 * https://www.kernel.org/doc/Documentation/arm64/booting.txt
17 * per document in linux/Doc/arm64/booting.text
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | SBE.interface.yaml | 5 initialize it to start the booting and also acts as a secure channel for
6 accessing certain control functions on the processor. During the booting or
|
| /openbmc/u-boot/board/freescale/mpc8315erdb/ |
| H A D | README | 28 When booting from NAND, use u-boot-nand.bin, not u-boot.bin.
41 When booting from NAND, NAND flash is CS0 and NOR flash
89 5.2 Downloading and Booting Linux Kernel
|
| /openbmc/u-boot/board/bticino/mamoj/ |
| H A D | README | 12 The following methods can be used for booting Mamoj boards:
95 Poweroff and Poweron the board and see U-Boot booting from eMMC.
120 Poweroff and Poweron the board and see Linux booting directly after SPL.
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-bsp/uefi/ |
| H A D | edk2-firmware_%.bbappend | 5 # No need for PXE booting in qemu, disable to reduce unnecessary noise
15 # No need for PXE booting in qemu, disable to reduce unnecessary noise
|