linux/meta-boot2qt.git/recipes, branch v5.6.0

ostree: Mount boot partition from user space

2016-03-08T09:55:29+00:00

In the current approach we assumed that boot/ - is on a separate boot partition - boot partition is right before rootfs partition - rootfs parition is provided as a *device node* - has "ext2" filesystem (mount shell cmd tries to auto detect FS type, mount system call does not.) The new approch does not assume any of the above, and moves this logic from early user space (initramfs) to user space. Initramfs by design should be used only to prepare the rootfs, other tasks should be done later. Change-Id: Idc429c8061c1fd486658e4b4d170ee487682cc91 Reviewed-by: Samuli Piippo

ostree: Do not use grub2-mkconfig.

2016-03-08T09:55:23+00:00

For more details see: https://bugzilla.gnome.org/show_bug.cgi?id=762220 To summarize: 1) The current approach is less flexible than using a custom 'ostree-grub-generator' script. Each device can adjust this script for its needs, instead of hardcoding some values in ostree-bootloader-grub2.c. 2) Too much overhead on embedded to generate grub.cfg via /etc/grub.d/ configuration files. It is still possible to do so, even with this patch applied. 3) The grub2-mkconfig code path has other issues: https://bugzilla.gnome.org/show_bug.cgi?id=761180 Change-Id: I077838fdf16fbbb42f98df6fa6720bfbaf7c6f8b Reviewed-by: Samuli Piippo

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

Format os-release file as specified in standard

2016-02-23T09:33:49+00:00

os-release spec: https://www.freedesktop.org/software/systemd/man/os-release.html "Variable assignment values must be enclosed in double or single quotes if they include spaces, semicolons or other special characters outside of A–Z, a–z, 0–9." Some tools might fail to read the file properly. Dracut for example prints warnings when parsing os-release file. Change-Id: I678a59aa8f33aa0c0398afb8ac87384f7ed52bc8 Reviewed-by: Samuli Piippo

Dracut: use more recent version

2016-02-23T08:12:18+00:00

The current version in certain situations fails with the following error message: [3.129861] systemd[1]: Cannot add dependency job for unit systemd-journald-audit.socket, ignoring: Unit systemd-journald-audit.socket failed to load: No such file or directory. It was fixed in Dracut by: 3e7a05f - systemd: add systemd-journald-audit.socket Version 44 contains this fix. Change-Id: Ia0233ab01929a6a7360af6c595f3e93181af85f5 Reviewed-by: Samuli Piippo

Add iproute2 to image

2016-02-15T14:39:54+00:00

Busybox provided ip does not work when trying to bring up can interface. Change-Id: Ied78c0036843993264bebae728763864dd83efd7 Reviewed-by: Teemu Holappa

Update license headers

2016-02-09T10:15:02+00:00

Change-Id: Iabcf736e6f4ae2149b57c84ebdc8b5b1be82023d Reviewed-by: Teemu Holappa

toradex: move perf patches

2016-02-05T10:30:12+00:00

Toradex machines are the last ones to use these. Change-Id: I6c769a250267733f851453eb8e72193201f5fbd6 Reviewed-by: Teemu Holappa

perl: include perl modules

2016-02-04T09:30:16+00:00

If perl is used from the SDK, it also needs modules. Use python magic to separate packages that cannot be installed to mingw32 toolchain. Change-Id: I9190cea1f00a166cc2f9119f2d4ad29c00347e19 Reviewed-by: Teemu Holappa

perl: use relocatable path in the wrapper

2016-02-04T09:30:10+00:00

Instead of using $OECORE_NATIVE_SYSROOT environment variable, that require sourcing the environment-setup-xxx script, use the SDKPATHNATIVE path that gets relocated during sdk installation. Change-Id: Ife7f84b3bb92d1492e96e9a65fd9cec4555aaecc Reviewed-by: Teemu Holappa