Lines Matching +full:- +full:boot
2 The EFI Boot Stub
8 along with the EFI-specific entry point that the firmware loader
9 jumps to are collectively known as the "EFI boot stub", and live in
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.
21 By using the EFI boot stub it's possible to boot a Linux kernel
22 without the use of a conventional EFI boot loader, such as grub or
23 elilo. Since the EFI boot stub performs the jobs of a boot loader, in
24 a certain sense it *IS* the boot loader.
26 The EFI boot stub is enabled with the CONFIG_EFI_STUB kernel option.
30 --------------------------
32 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
37 arch/arm/boot/zImage should be copied to the system partition, and it
38 may not need to be renamed. Similarly for arm64, arch/arm64/boot/Image
43 --------------------------------------------
51 --------------------
53 Like most boot loaders, the EFI stub allows the user to specify
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 -----------------