Lines Matching +full:device +full:- +full:tree
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
19 and drivers/firmware/efi/libstub/arm64-stub.c.
30 --------------------------
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 -----------------
86 For the ARM and arm64 architectures, a device tree must be provided to
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
93 device tree before booting the kernel. If dtb= is used to override
94 the device tree, then any runtime data provided by firmware will be
96 as a last resort when a device tree is not provided in the EFI