linux/poky.git/meta/classes/grub-efi.bbclass, branch python3

classes/oeqa: Update for print statements and file() -> open() for python3

2016-05-16T08:31:23+00:00

Found some more syntax cleanups needed for python3. (From OE-Core rev: 1181d86e8707c5b8e8d43d5e785d7d9cf01fa491) Signed-off-by: Richard Purdie

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

2016-04-03T14:51:35+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] (From OE-Core rev: 1f46fe7d501644c83f81dc4cc3310073c804f797) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

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

2016-03-25T10:29:16+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 (From OE-Core rev: e38039e43f22d55a443064efa91752e2943fda79) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

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

2016-03-25T10:29:16+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. (From OE-Core rev: d7d1e0193c94abb1cd2daf1c298c8c1788f3616d) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

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

2015-10-19T16:57:58+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 (From OE-Core rev: 38fe481911e7c4e9f674ded8f66878dff9e12ce3) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boot loader: support root=UUID

2015-09-06T14:26:25+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. (From OE-Core rev: 1e29d77d0d33ee216b43022439876863f0db39bb) 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-07T23:01:19+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. (From OE-Core rev: 3630f7963a472fa11a1d52bd9782fde9a9880971) Signed-off-by: Nicolas Guyomard Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

INITRD var: make it a list of filesystem images

2014-08-02T08:26: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. (From OE-Core rev: b0ac481dda99d8f4be8015964fcb2cb01afce08c) 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:54:12+00:00

Add MLPREFIX to depends flag to ensure the correct grub-efi is dependended upon. (From OE-Core rev: b62bf9e1cb8670901cfc37b1cd1822703ebdc000) 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:30:14+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. (From OE-Core rev: 14e5de3b8f4d5902d0ac683ff45fb878e88b40ef) Signed-off-by: Stefan Stanacar Signed-off-by: Saul Wold Signed-off-by: Richard Purdie