linux/meta-updater.git/recipes-core, branch fix/rpi-bootfiles-path

meta: introduce ostree-kernel-initramfs recipe

2020-07-08T13:52:07+00:00

We package kernel image, devicetrees, initramfs and install them to /usr/lib/modules/${KERNEL_VERSION}, which is the preferred location according to ostree's new implementation, this could simplify the deployment. Reference: https://github.com/ostreedev/ostree/commit/3ab0d5e6644885440bac6abd17b6d2637df5435f To let initramfs-ostree-image be able to be depended by ostree-kernel-initramfs, it must inherit nopackages to avoid a annoying QA warning like the follows: | WARNING: initramfs-ostree-image-0.0.1-r0 do_package: Manifest ...initramfs-ostree-image.packagedata | not found in colibri_imx6 armv7ahf-neon-imx armv7at2hf-neon-imx armv7at2hf-neon armv7ahf-neon armv7at2hf-vfp | armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp allarch | x86_64_x86_64-nativesdk (variant '')? Also we need define OSTREE_KERNEL, OSTREE_DEPLOY_DEVICETREE and OSTREE_DEVICETREE in sota.bbclass so they could be accessed in other recipes as well as in image recipes. Signed-off-by: Stefan Agner Signed-off-by: Ming Liu

initramfs-ostree-image: drop qemuboot from IMAGE_CLASSES

2020-06-02T10:05:40+00:00

To avoid generating a qemuboot.conf for qemu machines, it's useless for a initramfs image. Signed-off-by: Ming Liu

initramfs-ostree-image: drop image_repo_manifest from IMAGE_CLASSES

2020-01-30T15:07:04+00:00

We should remove image_repo_manifest from IMAGE_CLASSES instead of dropping buildinfo_manifest from IMAGE_PREPROCESS_COMMAND, which would ensure the entire class not to be inherited. Signed-off-by: Ming Liu

Don't try to put the repo manifest in the initramfs image.

2019-09-09T15:06:02+00:00

It isn't very useful there and just takes up space. Signed-off-by: Patrick Vacek

initramfs-ostree-image: unset EXTRA_IMAGEDEPENDS to avoid extra dependencies

2019-07-24T21:49:16+00:00

It is common for machine configurations to set EXTRA_IMAGEDEPENDS, which can end up causing circular dependencies when building the initramfs image (they are usually only required for the actual rootfs image). Signed-off-by: Ricardo Salveti

classes, images: Use standard variables for initramfs

2018-08-14T14:03:10+00:00

This will reduce the level of indirection and improve compatibility with the rest of OE. For example, FIT that includes initramfs may now be built. Signed-off-by: Yevgeny Popovych

Replace INITRAMFS_FSTYPES with OSTREE_INITRAMFS_FSTYPES

2018-02-09T02:32:03+00:00

User is able to customize the init script via OSTREE_INITRAMFS_IMAGE but there is no way to set INITRAMFS_FSTYPES as it gets defined by sota.bbclass. Create a new variable called OSTREE_INITRAMFS_IMAGE to handle the INITRAMFS_FSTYPES update, and also allow the user to override it. Signed-off-by: Ricardo Salveti

sota: introduce INITRAMFS_FSTYPES

2017-11-20T08:45:32+00:00

RAMDISK_EXT and IMAGE_FSTYPES of initramfs-ostree-image should not be defined separately, because they are representing the same fstype of a same initramfs image, or else, they turn out to be inconsistent if the users change one of them. So we use INITRAMFS_FSTYPES already defined in bitbake.conf, to be able to set fstype for initramfs. And it should default to ext4.gz.u-boot or ext4.gz depending on what OSTREE_BOOTLOADER is being set. Signed-off-by: Ming Liu

Fix incompatibilities with latest pyro, use wic on RPi

2017-11-07T13:31:52+00:00

Set IMAGE_OVERHEAD_FACTOR for fixed initrd size

2017-08-14T12:21:41+00:00

Set IMAGE_OVERHEAD_FACTOR = "1.0" Otherwise the initrd was 12M due to the default overhead (x1.3).