openembedded-core.git/meta/classes/bootimg.bbclass, branch fido

bootimg: Use deploy artefacts, not STAGING_KERNEL_DIR

2014-12-21T12:37:18+00:00

bzImage is no longer in STAGING_KERNEL_DIR. Rather than add it back,
depend on the kernel deploy task and find it in DEPLOY_DIR_IMAGE.

Signed-off-by: Richard Purdie

code cleanup for INITRD variable handing

2014-08-06T09:26:56+00:00

* Remove an unnecessary check
* Instead of ignoring, report the errors

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

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

bootimg.bbclass: Add parameter to specify HDDIMG volume ID

2014-07-10T16:37:39+00:00

Users and children of the bootimg class may need to specify at build
time the volume ID of the HDDIMG vfat partition. An example of this
may be when at runtime the partition is uniquely identified by
the volume ID.

The HDDIMG_ID is expected to be provided externally. If the variable
is not set, mkdosfs will use the default volume-id.

Signed-off-by: Ricardo Neri 
Signed-off-by: Saul Wold

Globally replace 'base_contains' calls with 'bb.utils.contains'

2014-04-25T16:10:58+00:00

The base_contains is kept as a compatibility method and we ought to
not use it in OE-Core so we can remove it from base metadata in
future.

Signed-off-by: Otavio Salvador 
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

image*.bbclass, bootimg.bbclass: add image type dependencies

2014-02-20T14:28:04+00:00

The following dependencies were manually added in the image creation
code. However, in order to have an image dependency mechanism in place,
use a new variable, IMAGE_TYPEDEP, to declare that an image type depends
on another being already created.

The following dependencies are added by this commit:

elf -> cpio.gz
live -> ext3
vmdk -> ext3
iso -> ext3
hddimg -> ext3

This commit adds also another new variable: IMAGE_TYPES_MASKED. Currently,
masking out certain types from IMAGE_FSTYPES was hardcoded in the image
creation code.

[YOCTO #5830]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Saul Wold

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

bootimage.bbclass, zisofs-tools-native: add ability to compress ISO images

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

The mkzftree is needed to allow ISO images to be compressed with
minimal runtime overhead.  Below is an example of the savings on a
core-image-minimal.

Before ls -l:
24117248 core-image-minimal-qemux86-64.iso

Using the mkzftree ls -l:
16777216 core-image-minimal-qemux86-64.iso

Signed-off-by: Jason Wessel 
Reviewed-by: Darren Hart 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

bootimage.bbclass, grub-efi.bbclass: Improve EFI & PCBIOS+EFI ISO support

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

Using the latest mkisofs it is possible to generate 3 different types
of ISO images, which can be used in various scenarios.

1) PCBIOS Only ISO
   - This option remains unchanged by this commit
   - Uses syslinux menus
   - Can be directly copied with dd to a USB device
   - Can be burned to optical media

2) EFI Only ISO
   - Uses grub 2 menus
   - Can be burned to optical media
   - If you want to use this image on a USB device
     extra steps must be taken in order to format the USB
     device with fat32, and copy an EFI loader which will
     in turn load the iso image

3) PCBIOS / EFI ISO
   - This is a hybrid image ISO that will work for case 1 or 2
     as above with the same restrictions and boot menu types
     depending on what type of firmware is installed on
     the hardware or depending on if EFI or "Legacy Boot" is
     enabled on some UEFI firmwares.

The syslinux.bbclass is now always required because that is where the
isohybrid dependencies come from as well as the configuration data for
the isohybrid.  The isohybrid is the secret sauce which allows the ISO
to work as optical media or as a disk image on USB or a HDD/SSD.

[YOCTO #4100]

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