linux/poky.git/meta/classes/boot-directdisk.bbclass, branch 2.1_M1

boot-directdisk.bbclass: remove HDDIMG before create

2015-12-01T21:31:59+00:00

Fixed when rebuild: mkdosfs: file /path/to/hdd.image already exists (From OE-Core rev: 9abcd309c098558360cde2bff65be840ead25f83) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Revert "boot-directdisk.bbclass: use rootfs UUID by default"

2015-09-12T21:48:35+00:00

This reverts commit 8ca8e2e5bf4a9f01dc48300149a8e1d71d715400. Further testing showed the kernel does not support root=UUID; it is something typically handled by the initramfs. Because boot-directdisk.bbclass cannot know whether it is using a suitable initramfs, root=UUID cannot be the default. Instead, it will have to be set in image recipes on a case-by-case basis. (From OE-Core rev: 8478024bd25651aa866d4582dcc193d51553554a) Signed-off-by: Patrick Ohly Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boot-directdisk.bbclass: use rootfs UUID by default

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

This changes the default SYSLINUX_ROOTFS such that the rootfs is no longer expected under a fixed device path. Instead, the UUID is used to find it. This makes the resulting .hdddirect (and thus also the vdi/vdmk/qcow2 images derived from that) more flexible. (From OE-Core rev: 8ca8e2e5bf4a9f01dc48300149a8e1d71d715400) Signed-off-by: Patrick Ohly Signed-off-by: Richard Purdie

image: Support for qcow2

2015-07-25T13:41:43+00:00

Add support for qcow2 image format. Implemented in the same way as the previously existing vmdk and vdi solutions. (From OE-Core rev: c1f9ed400e4b5fe5be4fac86021dea11a7546035) Signed-off-by: Christian Ziethén Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boot-directdisk: Make kernel image inclusion conditional.

2015-07-25T13:41:43+00:00

When building for qcow2 and a dummy kernel, avoid installing a non existing bzImage. (From OE-Core rev: 7d476f117c62e532c99abef5728e729b8001fa32) Signed-off-by: Christian Ziethén Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boot-direct.bbclass: Add support for VDI images

2015-06-11T22:59:13+00:00

Same treatment for both VMDK and VDI images. (From OE-Core rev: 605dd9f8eb719d0aa278c8ec892e62214cdcfddc) Signed-off-by: Juro Bystricky Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

boot-directdisk: Use kernel from DEPLOY_DIR_IMAGE, not sysroot

2014-12-21T12:37:55+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. (From OE-Core rev: 40e83470ca45ae5c305609a5065278612e69a7e2) Signed-off-by: Richard Purdie

boot-directdisk.bbclass: use local HDDDIR

2014-08-11T09:53:05+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. (From OE-Core rev: 1891c39a359e983bb8fd7992b7b5a1aaac11baf7) Signed-off-by: Robert Yang Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

code cleanup for INITRD variable handing

2014-08-06T09:27:00+00:00

* Remove an unnecessary check * Instead of ignoring, report the errors (From OE-Core rev: 7afc6df6f0d0bbe0c5cb8ec021d430d6d9714941) Signed-off-by: Nitin A Kamble 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