In looking at the poky tiny initramfs image, it sets:
IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
Which would then make the two variable the same and make the check kick
in. But I cannot find where it manual says that you have to make them
the same value and cannot generate an initramfs image al
I added some debugging to print out the various variables on interest
and got this output:
DEBUG: image_fstypes= tar.xz wic.xz wic.bmap tar.xz.md5sum cpio cpio.xz
DEBUG: initramfs_fstypes=cpio.gz cpio cpio.xz
DEBUG: initramfs_maxsize=65536.00
DEBUG: base_size=74366
So I'm not sure I agree
Image builds obey IMAGE_FSTYPES. Initramfs images set that to
INITRAMFS_FSTYPES, so it's comparing the two as a check to see if this is
an initramfs image. It isn't making sure it matches a hardcoded list, so
intersection isn't necessary.
On Wed, Aug 2, 2023 at 9:41 AM Ryan Eatmon via lists.openem
I am trying to add support for the INITRAMFS_MAXSIZE into the meta-ti
layer for our tiny image.
I have added the following to our tiny image file:
INITRAMFS_FSTYPES += "cpio cpio.xz"
INITRAMFS_MAXSIZE = "65536"
But I'm not seeing any errors about the image being too big being printed.
In lo
