| /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/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/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/linux/Documentation/riscv/ |
| H A D | boot.rst | 56 using the ``$a1`` register, or when booting with UEFI, it can be passed using the
72 - ``Ordered booting``: the firmware releases only one hart that will execute the
74 extension. The ordered booting method is the preferred booting method for
75 booting the RISC-V kernel because it can support CPU hotplug and kexec.
83 When booting with UEFI, the RISC-V kernel will use only the EFI memory map to
95 When booting with UEFI, the EFI stub requires the boot hartid in order to pass
113 When booting with UEFI, the devicetree is supplemented (or created) by the EFI
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | qcom,wcnss-pil.yaml | 61 PX regulator to be held on behalf of the booting of the WCNSS core
65 MX regulator to be held on behalf of the booting of the WCNSS core.
69 CX regulator to be held on behalf of the booting of the WCNSS core.
129 Reference to the regulator to be held on behalf of the booting WCNSS
134 Reference to the regulator to be held on behalf of the booting WCNSS
139 Reference to the regulator to be held on behalf of the booting WCNSS
144 Reference to the regulator to be held on behalf of the booting WCNSS
|
| /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).
|
| H A D | overlay-fdt-boot.txt | 100 Booting this image is done by using
108 This selects the DTB to use when booting.
114 being passed to the booting kernel. This saves on space and avoid the combinatorial
195 Booting this image is exactly the same as the non-overlay example.
216 While booting a revb with bar and baz is as follows:
|
| /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
|
| H A D | README.falcon | 10 Falcon Mode is introduced to speed up the booting process, allowing
13 Falcon Mode relies on the SPL framework. In fact, to make booting faster,
15 image. In most implementations, SPL is used to start U-Boot when booting from
90 boot_os : Set to yes/Yes/true/True/1 to enable booting to OS,
165 ## Booting kernel from Legacy Image at 82000000 ...
211 2. Set bootargs as desired for Linux booting (e.g. flash_mtd):
|
| H A D | README.POST | 22 of tests running on normal/power-fail booting.
65 1) Tests running on power-on booting only
70 2) Tests running on normal booting only
117 #define POST_POWERON 0x01 /* test runs on power-on booting */
118 #define POST_NORMAL 0x02 /* test runs on normal booting */
219 power-fail booting will be kept in the environment. Namely, the
327 handler of the power-fail IRQ on booting. Being called, the handler
348 location in IMMR. On booting, the POST layer will check the value of
400 booting.
405 run on normal booting.
[all …]
|
| H A D | README.odroid | 78 Check if Hardkernel U-Boot is booting, and next do the same with your U-Boot.
146 10. The environment and booting the kernel
228 TFTP booting:
265 Booting using the fdt blob at 0x42000000
270 [ 0.000000] Booting Linux on physical CPU 0xa00
275 USB Storage booting:
281 For this example the second EXT partition is used for booting and as rootfs.
325 Booting using the fdt blob at 0x42000000
330 [ 0.000000] Booting Linux on physical CPU 0xa00
|
| /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/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/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 | 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 | 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 | colibri_imx7.h | 57 "${vidargs}; echo Booting from internal eMMC chip...; " \
75 "${setupargs} ${vidargs}; echo Booting from MMC/SD card...; " \
84 "${setupargs} ${vidargs}; echo Booting from MMC/SD card...; " \
96 "${setupargs} ${vidargs}; echo Booting from NFS...;" \
106 "${setupargs} ${vidargs}; echo Booting from NAND...; " \
|
| H A D | imx6_logic.h | 63 "mmcboot=echo Booting from mmc...; run finduuid; run mmcargs;" \
68 "nandboot=echo Booting from nand ...; " \
73 "nandramboot=echo Booting RAMdisk from nand ...; " \
82 "netboot=echo Booting from net ...; " \
|
| /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/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
| H A D | README.falcon | 10 booting U-Boot is not the first choice. The kernel FIT image needs to be put
17 does FDT fixups when booting Linux. For falcon boot, Linux boots directly from
40 this macro is passed as the location of device tree when booting Linux.
51 Following normal booting process, all variables are set, all images are loaded
56 where the address is the location of FIT image. U-Boot goes through the booting
|
| /openbmc/u-boot/common/ |
| H A D | Kconfig | 6 Enable recording of boot time while booting. To use it, insert
40 bool "Display a detailed boot timing report before booting the OS"
97 bool "Stash the boot timing information in memory before booting OS"
126 bool "Support for booting from NOR flash"
135 bool "Support for booting from NAND flash"
144 bool "Support for booting from ONENAND"
153 bool "Support for booting from QSPI flash"
161 bool "Support for booting from SATA"
169 bool "Support for booting from SD/EMMC"
177 bool "Support for booting from SPI flash"
[all …]
|
| /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
|