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

boot-directdisk: Use kernel from DEPLOY_DIR_IMAGE, not sysroot

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

After the recent kernel changes, this avoids failures like:

DEBUG: Executing shell function build_boot_dd
install: cannot stat '/home/pokybuild/yocto-autobuilder/yocto-worker/build-appliance/build/build/tmp/sysroots/qemux86-64/usr/src/kernel/bzImage': No such file or directory
WARNING: exit code 1 from a shell command.

Signed-off-by: Richard Purdie

boot-directdisk.bbclass: use local HDDDIR

2014-08-11T09:46:58+00:00

Use $HDDDIR rather than ${HDDDIR} in build_boot_dd(), otherwise may
errors:
- Set these in local.conf:
  IMAGE_FSTYPES += "live"
  IMAGE_FSTYPES += "vmdk"
  AUTO_SYSLINUXMENU = "1"
  NOHDD = "1"

$ bitbake core-image-sato
  DEBUG: Executing shell function build_boot_dd
  install: cannot create regular file
  `/path/to/core-image-sato-1.0/hddimg//vesamenu.c32': No such file or directory
  WARNING: exit code 1 from a shell command.

This because it uses the ${HDDDIR} which is set in bootimg.bbclass, use
local HDDDIR which is set in build_boot_dd() will fix the problem.

Signed-off-by: Robert Yang 
Signed-off-by: Saul Wold

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

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

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