openembedded-core.git/meta/classes/boot-directdisk.bbclass, branch daisy

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

boot-directdisk: fix the support of vmdk

2014-01-23T10:17:13+00:00

Previous change (086ce22b88f5ef5f75a83119a32c8b3fdcfa296d) broke
the creating of vmdk images. This protects shell expansion variables
and let dd generate the image to be transformed to vmdk by image-vmdk.class.

Signed-off-by: Joao Henrique Ferreira de Freitas 

[edit to change the usage of IMAGE_FSTYPE to IS_VMDK]

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

boot-directdisk: add the support of vmdk

2013-12-09T18:01:35+00:00

add the support of vmdk.

Signed-off-by: Saul Wold

boot-directdisk: avoid loop in MBR disk signature generation

2013-10-04T17:25:05+00:00

Instead of looping until the generated signature is non-zero, just
return 'ffffffff' if it's zero. This avoids an infinite loop if the
generated signature is always zero.

Signed-off-by: Jonathan Liu 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

boot-directdisk: ensure generated MBR disk signature is non-zero

2013-09-30T21:03:23+00:00

A zero MBR disk signature is generally seen as no signature and
another partitioning program might install a new signature.

Signed-off-by: Jonathan Liu 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

boot-directdisk.bbclass: Fix media generation problems with vmdk

2013-09-26T16:27:23+00:00

The various populate methods need to accept a path as an argument vs
using hard expanded variables.  In the case of the boot-directdisk
class it uses a different path for HDDDIR but it gets eclipsed by the
the class definition at the point in time ${HDDDIR} gets expanded.

The logical fix is to pass the arguments to the functions as opposed
to using globally expanded variables from the class definitions.

This patch changes 3 things:
1) syslinux_hddimg_populate takes an argument for the destination
2) syslinux_iso_populate takes an argument for the destination
3) populate is changed to boot_direct_populate because there
   was a conflict with it overriding the populate in bootimg.bbclass

[YOCTO #3994]

Signed-off-by: Jason Wessel 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

boot-directdisk: Allow for EFI-only boot direct disk images

2013-09-14T07:26:44+00:00

    Condition building PCBIOS legacy images on MACHINE_FEATURES containing "pcbios"
    or not containing "efi". This ensures existing BSPs will continue to get the
    old PCBIOS legacy-only images. New BSPs can add "efi", "pcbios", or both. The
    images created likewise support one or the other or both.

Signed-off-by: João Henrique Ferreira de Freitas 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

boot-directdisk: use awk instead of echo -ne for dash compatibility

2013-07-23T14:22:38+00:00

The echo command is a dash shell built-in and does not support the
-n and -e options so use awk instead.

This fixes the partition table being corrupted when writing the MBR
disk signature into the image.

[YOCTO #4859]

Signed-off-by: Jonathan Liu 
Signed-off-by: Saul Wold

boot-directdisk: allow specifying custom MBR disk signature

2013-07-11T23:07:24+00:00

This introduces a DISK_SIGNATURE variable that allows controlling the
32-bit MBR disk signature. By default it is set to an automatically
generated disk signature but it may by overridden in the image recipe
by setting DISK_SIGNATURE to a 8 digit hex string.

This DISK_SIGNATURE variable can also be used in the image recipe to
specify the root by UUID using:
SYSLINUX_ROOT = "root=PARTUUID=${DISK_SIGNATURE}-02"

Specifying the root by UUID allows the kernel to locate the root
filesystem even if the device name changes (e.g. /dev/hda2, /dev/hdb2 or
/dev/sdb2 instead of /dev/sda2) due to differences in hardware
configuration.

Signed-off-by: Jonathan Liu 
Acked-by: Darren hart

boot-directdisk: Scope HDDDIR and HDDIMG variables to avoid conflicts

2013-05-15T21:05:07+00:00

These variables should not be shared with other image classes.
The bootimg class also has an HDDDIR variable that could be overwritten
if executing concurrently in the same image recipe.

Signed-off-by: Jonathan Liu 
Signed-off-by: Saul Wold