Lines Matching refs:the

4 On the x86 and ARM platforms, a kernel zImage/bzImage can masquerade
6 it as an EFI executable. The code that modifies the bzImage header,
7 along with the EFI-specific entry point that the firmware loader
8 jumps to are collectively known as the "EFI boot stub", and live in
10 respectively. For ARM the EFI stub is implemented in
15 For arm64, there is no compressed kernel support, so the Image itself
16 masquerades as a PE/COFF image and the EFI stub is linked into the
20 By using the EFI boot stub it's possible to boot a Linux kernel
21 without the use of a conventional EFI boot loader, such as grub or
22 elilo. Since the EFI boot stub performs the jobs of a boot loader, in
23 a certain sense it *IS* the boot loader.
25 The EFI boot stub is enabled with the CONFIG_EFI_STUB kernel option.
30 The bzImage located in arch/x86/boot/bzImage must be copied to the EFI
31 System Partition (ESP) and renamed with the extension ".efi". Without
32 the extension the EFI firmware loader will refuse to execute it. It's
33 not possible to execute bzImage.efi from the usual Linux file systems
34 because EFI firmware doesn't have support for them. For ARM the
35 arch/arm/boot/zImage should be copied to the system partition, and it
40 **** Passing kernel parameters from the EFI shell
42 Arguments to the kernel can be passed after bzImage.efi, e.g.
49 Like most boot loaders, the EFI stub allows the user to specify
50 multiple initrd files using the "initrd=" option. This is the only EFI
51 stub-specific command line parameter, everything else is passed to the
54 The path to the initrd file must be an absolute path from the
55 beginning of the ESP, relative path names do not work. Also, the path
57 backslashes (\). For example, given the following directory layout,
68 to boot with the initrd-large.img file if the current working
69 directory is fs0:\Kernels, the following command must be used,
74 because the image we're executing is interpreted by the EFI shell,
75 which understands relative paths, whereas the rest of the command line
81 For the ARM and arm64 architectures, we also need to be able to provide a
82 device tree to the kernel. This is done with the "dtb=" command line option,
83 and is processed in the same manner as the "initrd=" option that is