| /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/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/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/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/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 \
|
| H A D | core-image-tiny-initramfs.bb | 2 SUMMARY = "Tiny image capable of booting a device."
3 DESCRIPTION = "Tiny image capable of booting a device. The kernel includes \
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-platform-devices-ampere-smpro | 290 - 00: SMpro firmware booting
291 - 01: PMpro firmware booting
292 - 02: ATF BL1 firmware booting
295 - 05: ATF BL2 firmware booting
296 - 06: ATF BL31 firmware booting
297 - 07: ATF BL32 firmware booting
298 - 08: UEFI firmware booting
299 - 09: OS booting
|
| /openbmc/u-boot/doc/ |
| H A D | README.mpc85xx-sd-spi-boot | 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.iscsi | 1 # iSCSI booting with U-Boot and iPXE
6 network booting has been on UDP based protocols. A TCP stack and HTTP support
9 For booting a diskless computer this leaves us with BOOTP or DHCP to get the
31 via HTTPS and to download any other files needed for booting via iSCSI from the
36 network booting. It supports both HTTPS and iSCSI. It has a scripting engine for
|
| H A D | README.mpc85xx-spin-table | 6 __secondary_start_page. For other cores to use the spin table, the booting
20 TLB. While booting, they set up another TLB in AS=1 space and jump into
|
| /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/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-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0028-corstone1000-boot-index-from-active.patch | 8 we know that the we are booting from the active index.
31 + * we know that the we are booting from the active index
|
| /openbmc/linux/arch/arm/boot/dts/samsung/ |
| H A D | exynos5420-cpus.dtsi | 12 * but particular boards choose different booting order.
15 * booting cluster (big or LITTLE) is chosen by IROM code by reading
16 * the gpg2-1 GPIO. By default all Exynos5422 based boards choose booting
|
| H A D | exynos5422-cpus.dtsi | 11 * but particular boards choose different booting order.
14 * booting cluster (big or LITTLE) is chosen by IROM code by reading
15 * the gpg2-1 GPIO. By default all Exynos5422 based boards choose booting
|
| /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/linux/Documentation/translations/zh_CN/arch/arm/ |
| H A D | Booting | 1 Chinese translated version of Documentation/arch/arm/booting.rst
12 Documentation/arch/arm/booting.rst 的中文翻译
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | multi_spl.its | 8 * For booting U-Boot, "firmware" is searched first. If not found, "loadables"
11 * same flow as booting U-Boot. Changing image type will result skipping
|
| 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
181 Example 2 -- new-style (FDT) kernel booting
317 Example 3 -- advanced booting
321 sophisticated booting scenarios (multiple kernels, ramdisks and fdt blobs).
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | wkup_m3_rproc.txt | 8 the firmware and booting of the CM3.
29 booting the wkup_m3 remote processor.
|
| /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/linux/Documentation/arch/xtensa/ |
| H A D | index.rst | 11 booting
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | runqemu.README | 5 on a desktop system. The scripts currently support booting ARM, MIPS, PowerPC
22 If <filesystem> isn't specified, nfs booting will be assumed.
|
| /openbmc/linux/Documentation/arch/mips/ |
| H A D | index.rst | 11 booting
|