openembedded-core.git/meta/classes/grub-efi.bbclass, branch krogoth

meta/classes: fix bb.build.FuncFailed typos

2016-09-23T14:25:37+00:00

Signed-off-by: Jonathan Liu 
Signed-off-by: Armin Kuster

grub-efi.bbclass: use GRUB_ROOT rather than APPEND for root device

2016-04-03T14:51:08+00:00

Use APPEND for grub's root device may cause confusion, for example, when
building efi + pcbios, there maybe be two root=/dev/ram0, one of them
would be carried to the installed target, and the target would fail to
boot. Use GRUB_ROOT to fix the problem, and remove SYSLINUX_ROOT from
APPEND will fix the problem.

[YOCTO #9354]

Signed-off-by: Robert Yang 
Signed-off-by: Richard Purdie

grub-efi.bbclass: make it can build vm and live together

2016-03-24T21:44:26+00:00

* Make it can build vm and live (e.g., iso + vmdk) together as we did
  for syslinux.
* GRUBCFG -> GRUB_CFG as other GRUB_FOO vars

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

bootimg.bbclass: fix settings for grub-efi.bbclass

2016-03-24T21:44:26+00:00

Fixed:
- Found potential conflicted var LABELS ...
  Set LABELS to "boot install" would build out broken images when build
  vm + live together, use set_live_vm_vars() to fix the problem.

- Use ROOT and LABEL in boot-directdisk.bbclass and image-foo.bbclass,
  they are not only used by syslinux.bbclass, but also grub-efi.bbclass,
  add "SYSLINUX_" prefix would mislead users.

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

grub-efi, gummiboot: Emit correct path in startup.nsh

2015-10-19T16:47:45+00:00

when we generate hddimage and use it to prepare SD card
using scripts/contrib/mkefidisk.sh as described here

http://elinux.org/Minnowboard:MinnowMaxYoctoProject

The content of startup.nsh contains

bootx64.efi

but this file is actually not in same dir as startup.nsh
its in /EFI/BOOT so for this to work entry in startup.nsh
should be

fs0:\EFI\BOOT\bootx64.efi

Otherwise the image is D-O-A

Signed-off-by: Khem Raj 
Signed-off-by: Ross Burton

boot loader: support root=UUID

2015-09-06T14:24:26+00:00

As mentioned when introducing the VM images
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=7374), the
resulting images only work when the image is mounted as a disk that
results in the hard-coded path (/dev/sda in the current
default). Using the file system UUID to find the rootfs is more
flexible.

To enable this for boot-direct.bbclass and thus image-vm.bbclass (aka
FSTYPEs vdi/vmdk/qcow2), set SYSLINUX_ROOT =
"root=UUID=<>". The rootfs image must use an ext file
system.

The special string will get replaced in the APPEND line with the
actual UUID when the boot loader (grub-efi, syslinux or gummiboot)
writes the boot loader configuration files. At that time, the rootfs
image has already been created and its UUID can be extracted using
"tune2fs -l", which also should be available because the
e2fsprogs-native tools were needed to create the image in the first
place.

Signed-off-by: Patrick Ohly 
Signed-off-by: Richard Purdie

grub-efi: Allow to use file name different from grub.cfg in GRUBCFG

2015-07-07T22:56:23+00:00

To generate a same image both in live image type and boot-directdisk image type
and make boot-direct image boot directly on the rootfs partition without using
an initramfs we need to have the ability to generate several grub.cfg files.

Signed-off-by: Nicolas Guyomard 
Signed-off-by: Ross Burton

INITRD var: make it a list of filesystem images

2014-08-02T08:21:14+00:00

The initrd image used by the Linux kernel is list of file system images
concatenated together and presented as a single initrd file at boot time.

So far the initrd is a single filesystem image. But in cases like to support
early microcode loading, the initrd image need to have multiple filesystem
images concatenated together.

This commit is extending the INITRD variable from a single filesystem image
to a list of filesystem images to satisfy the need mentioned above.

Signed-off-by: Nitin A Kamble 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

grub-efi.bbclass: Ensure MLPREFIX is applied to depends flag

2014-06-24T18:53:02+00:00

Add MLPREFIX to depends flag to ensure the correct grub-efi is
dependended upon.

Signed-off-by: Ming Liu 
Signed-off-by: Richard Purdie

bootimg/grub-efi.bbclass: allow using a different class for EFI images

2014-03-11T16:29:40+00:00

Abstract away some names so one can select using EFI_PROVIDER a different
class than grub-efi for populating live images, basically allowing the use
of a different bootloader than grub-efi.

Signed-off-by: Stefan Stanacar 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie