summaryrefslogtreecommitdiffstats
path: root/meta/classes/boot-directdisk.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* bootimg/image-vm/image-live: Improve image dependenciesRichard Purdie2016-01-191-1/+1
| | | | | | | | | | | | | | Now that image generation consists of separate tasks, we can improve the dependencies in these classes. We can also incorporate the tasks within do_image_complete instead of do_build so we have a specific task for when the deploy directory is populated with images. This fixes various expectations about do_image_completed and the way I'd tried to use it to fix some sanity test problems. (From OE-Core rev: 9543c4a9ce0ac7d9ced66fa14e48a1aa7401011e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk.bbclass: remove HDDIMG before createRobert Yang2015-12-011-0/+2
| | | | | | | | | | | Fixed when rebuild: mkdosfs: file /path/to/hdd.image already exists (From OE-Core rev: 9abcd309c098558360cde2bff65be840ead25f83) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "boot-directdisk.bbclass: use rootfs UUID by default"Patrick Ohly2015-09-121-1/+1
| | | | | | | | | | | | | | | | | 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 <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk.bbclass: use rootfs UUID by defaultPatrick Ohly2015-09-061-1/+1
| | | | | | | | | | | | 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 <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image: Support for qcow2Christian Ziethén2015-07-251-1/+1
| | | | | | | | | | | 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 <christian.ziethen@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Make kernel image inclusion conditional.Christian Ziethén2015-07-251-1/+3
| | | | | | | | | | | 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 <christian.ziethen@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-direct.bbclass: Add support for VDI imagesJuro Bystricky2015-06-111-2/+2
| | | | | | | | | | Same treatment for both VMDK and VDI images. (From OE-Core rev: 605dd9f8eb719d0aa278c8ec892e62214cdcfddc) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Use kernel from DEPLOY_DIR_IMAGE, not sysrootRichard Purdie2014-12-211-1/+2
| | | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* boot-directdisk.bbclass: use local HDDDIRRobert Yang2014-08-111-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | 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 <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* code cleanup for INITRD variable handingNitin A Kamble2014-08-061-1/+3
| | | | | | | | | | * Remove an unnecessary check * Instead of ignoring, report the errors (From OE-Core rev: 7afc6df6f0d0bbe0c5cb8ec021d430d6d9714941) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* INITRD var: make it a list of filesystem imagesNitin A Kamble2014-08-021-3/+10
| | | | | | | | | | | | | | | | | | 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 <nitin.a.kamble@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Globally replace 'base_contains' calls with 'bb.utils.contains'Otavio Salvador2014-04-251-5/+5
| | | | | | | | | | | 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. (From OE-Core rev: d83b16dbf0862be387f84228710cb165c6d2b03b) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bootimg/grub-efi.bbclass: allow using a different class for EFI imagesStefan Stanacar2014-03-111-3/+4
| | | | | | | | | | | | 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 <stefanx.stanacar@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: fix the support of vmdkJoao Henrique Ferreira de Freitas2014-01-231-10/+8
| | | | | | | | | | | | | | | 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. (From OE-Core rev: 2fe667afbdc6880c377657b5ff27e6db3b6cbe77) Signed-off-by: Joao Henrique Ferreira de Freitas <joaohf@gmail.com> [edit to change the usage of IMAGE_FSTYPE to IS_VMDK] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: add the support of vmdkyanjun.zhu2013-12-091-3/+18
| | | | | | | | | add the support of vmdk. (From OE-Core rev: 086ce22b88f5ef5f75a83119a32c8b3fdcfa296d) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: avoid loop in MBR disk signature generationJonathan Liu2013-10-041-4/+5
| | | | | | | | | | | | 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. (From OE-Core rev: 34c74ba45c04efc2dd998545bf7a31d7b06a0ee0) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: ensure generated MBR disk signature is non-zeroJonathan Liu2013-09-301-1/+5
| | | | | | | | | | | A zero MBR disk signature is generally seen as no signature and another partitioning program might install a new signature. (From OE-Core rev: b6cafb1fcd6c168f8f4a4d2d5c74f3b425f156f3) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk.bbclass: Fix media generation problems with vmdkJason Wessel2013-09-301-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | 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] (From OE-Core rev: 63d164b755b984021f7e3cdba7280918ded6e821) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Allow for EFI-only boot direct disk imagesJoão Henrique Ferreira de Freitas2013-09-141-10/+55
| | | | | | | | | | | | | 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. (From OE-Core rev: c58aceee7dc243467dd87f07ccc61859f8d945e6) Signed-off-by: João Henrique Ferreira de Freitas <joaohf@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: use awk instead of echo -ne for dash compatibilityJonathan Liu2013-07-241-1/+1
| | | | | | | | | | | | | | | | 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] (From OE-Core rev: 1928f46e8e9f281e3e64f916048cc9314e125150) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: allow specifying custom MBR disk signatureJonathan Liu2013-07-131-0/+20
| | | | | | | | | | | | | | | | | | | | | | 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. (From OE-Core rev: 4382a419b4c90312d22aa55ff535b45bcf704716) Signed-off-by: Jonathan Liu <net147@gmail.com> Acked-by: Darren hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Scope HDDDIR and HDDIMG variables to avoid conflictsJonathan Liu2013-05-161-13/+12
| | | | | | | | | | | | 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. (From OE-Core rev: 94c83fa26af104d28aa4e6951bcb109bb0c82265) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* syslinux: Update to 4.06Jonathan Liu2013-05-161-2/+2
| | | | | | | | | | | | | | | Patches are now part of upstream or no longer needed. Added new util-linux dependency for isohybrid. Paths updated to reflect directory structure changes. Add CFLAGS and LDFLAGS overrides. [YOCTO #4438] (From OE-Core rev: 17e7ac0c5e75245d17a90e5cc49ade3d18a168ba) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk/bootimg/image-vmdk: remove more nostamps for image generationRobert Yang2013-05-101-1/+0
| | | | | | | | | | | | | | | | | | | We have removed the nostamps for do_rootfs and do_build, so it seems reasonable to remove the stamps for do_bootimg, do_bootdirectdisk and do_vmdkimg. The current problem is that the do_vmdkimg always re-run, but the do_rootfs may not, so the code like below in the do_rootfs function doesn't re-run and cause problems (the symlink exists when the do_vmdkimg creates the symlink again): if d.getVar('IMAGE_LINK_NAME', True): cmds += "\trm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.*" (From OE-Core rev: 45c7dab5d51065c7b24ab5292f8e9d3104eb0626) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert tab indentation in python functions into four-spaceRichard Purdie2012-07-191-2/+2
| | | | | | (From OE-Core rev: 604d46c686d06d62d5a07b9c7f4fa170f99307d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Fix kernel location after STAGING_KERNEL_DIR changeRichard Purdie2012-07-181-1/+1
| | | | | | | | | | | This catches up with the STAGING_KERNEL_DIR location change and uses the correct variable to future proof this issue. [YOCTO #2783] (From OE-Core rev: 28715eff6dff3415b1d7b0be8cbb465c417e307f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: remove the default setting of SYSLINUXCFG and SYSLINUXMENUSaul Wold2012-04-111-3/+0
| | | | | | | | | | | These two should get setup in {S} and installed into {HDDDIR}, by having them defined with {HDDDIR} they try to get created when the directory does not exist yet. (From OE-Core rev: 215ea5ea8b97270a3602b3f20469226a56442552) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Fix Block CalcuationSaul Wold2012-03-271-6/+13
| | | | | | | | | | | | | | This also changes the timeout to be settable The block calcuation was not correctly rounding, see comment Thanks to Darren Hart for fixing this. Cc: Darren Hart <dvhart@linux.intel.com> (From OE-Core rev: 53ae1737611e10e7fef815e8fde9e22165aa1047) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Use correct SYSLINUX_TIMEOUT and SYSLINUX_ROOT instead of ↵Saul Wold2012-02-231-2/+4
| | | | | | | | | APPEND (From OE-Core rev: 1284230ad554f8607cb02b054fdd74017ae7c861) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: fix bzImage source locationTom Zanussi2011-05-051-1/+1
| | | | | | | | | | | | Fixes yocto [BUGID #876] boot-directdisk.class looks in the wrong location for the bzImage to install. Make it look in the right place. (From OE-Core rev: 173d04ea828e7f790ede40929c8ffd7340b4c077) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bootimg/boot-directdisk.bbclass: Update afer syslinux changes, fix mbr.bin ↵Richard Purdie2010-03-251-4/+6
| | | | | | location and fix dependencies Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* boot-directdisk.bbclass: Add direct disk image creation classRichard Purdie2010-03-251-0/+92
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 03:53:33 +0000