Lines Matching +full:system +full:- +full:firmware

6 as a PE/COFF image, thereby convincing EFI firmware loaders to load
8 along with the EFI-specific entry point that the firmware loader
10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c,
12 arch/arm/boot/compressed/efi-header.S and
13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared
14 between architectures is in drivers/firmware/efi/libstub.
18 kernel. The arm64 EFI stub lives in drivers/firmware/efi/libstub/arm64.c
19 and drivers/firmware/efi/libstub/arm64-stub.c.
30 --------------------------
33 System Partition (ESP) and renamed with the extension ".efi". Without
34 the extension the EFI firmware loader will refuse to execute it. It's
36 because EFI firmware doesn't have support for them. For ARM the
37 arch/arm/boot/zImage should be copied to the system partition, and it
43 --------------------------------------------
51 --------------------
55 stub-specific command line parameter, everything else is passed to the
60 is an EFI-style path and directory elements must be separated with
66 			initrd-large.img
69 			initrd-small.img
70 			initrd-medium.img
72 to boot with the initrd-large.img file if the current working
75 	fs0:\Kernels> bzImage.efi initrd=\Kernels\initrd-large.img
84 -----------------
87 the kernel. Normally firmware shall supply the device tree via the
89 be used to override the firmware supplied device tree, or to supply
90 one when firmware is unable to.
92 Please note: Firmware adds runtime configuration information to the
94 the device tree, then any runtime data provided by firmware will be