linux/meta-boot2qt.git/classes/image_dd.bbclass, branch v5.9.7

image_dd: remove old boot.img before trying to create it

2017-05-10T05:25:08+00:00

rootfs creation failed if boot.img still existed from previous build. Change-Id: Ib85cc7dbacbc0d0cc7d0700985ad9c52a6ade0df Reviewed-by: Mikko Gronoff

Update image creation recipes, appends etc. to be poky 2.2 compliant

2017-03-14T18:43:09+00:00

DEPLOY_DIR_IMAGE macro has been replaced with IMGDEPLOYDIR in poky 2.2. Update all instances to make image creation work. Change-Id: I3740730ded84650d3a3a51b85c77ed4fef863a8a Reviewed-by: Samuli Piippo

Initial morty branch setup for poky & meta layers

2017-03-14T18:42:49+00:00

New or updated branches: * meta-fsl-arm & meta-fsl-arm-extra layers changes to meta-freescale & meta-freescale-3rdparty (morty) * poky (morty) * meta-openembedded (morty) * meta-qt5 (5.9) * meta-mingw (morty) * meta-tegra (morty) Modified accordingly: * conf/.sample files * classes/image_dd.class * conf/distro .inc files * scripts/manifest.xml Change-Id: Ia8ad563f2f1176882019490f274a6b4bb043475f Reviewed-by: Samuli Piippo

Update license headers

2016-05-18T09:31:21+00:00

License changed to GPLv3 + Commercial Change-Id: I267c97216e717ed29071df064337e1bcf83de973 Reviewed-by: Kalle Viironen

NUC: Use custom image layout

2016-02-23T11:18:52+00:00

This patch adds a new image class 'image_dd', by default it has an empty boot partition. image_dd_efi extends this class to support Intel NUC board. The layout of a generated image is a prerequisite for OSTree integarion. Image generated by 'hddimg' produces rootfs.img (ext3 filesystem file) and then "live" boots it from initramfs by mounting rootfs.img via loop device. For OTA integration we need to access contents of rootfs.img already from boot loader. The custom 'image_nuc_efi' layout allow for fully atomic updates on EFI based system, by keeping GRUB-EFI binary on a dedicated EFI system partition (ESP). OSTree currently is not fully atomic on EFI systems, but with this setup we use GRUB-BIOS code path in OSTree, which is atomic. After EFI firmware has loaded the GRUB-EFI binary, everything else is done on rootfs parition. One limitation from the above scenario is that you would need to update /EFI/BOOT/bootx64.efi (GRUB-EFI) binary manually. Not sure how common it is to update a boot loader binary on a deployed system, but its not impossible. Change-Id: Ibf2840aecd548000372131c4ded5cffa11ff1b0f Reviewed-by: Teemu Holappa