[yocto] How to proceed with kernel-fitimage and INITRAMFS_IMAGE
Khem Raj
raj.khem at gmail.com
Thu Oct 27 19:36:28 PDT 2016
> On Oct 27, 2016, at 10:34 AM, Rick Altherr <raltherr at google.com> wrote:
>
> Krogoth (2.1.1) doesn't include the changes required to build a fitImage with an initramfs. Specifically, it lacks ec755d2524fcbd9dfded23a576f25c990d405a6c <http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ec755d2524fcbd9dfded23a576f25c990d405a6c> which is only submitted to master. From https://www.mail-archive.com/yocto@yoctoproject.org/msg31779.html <https://www.mail-archive.com/yocto@yoctoproject.org/msg31779.html>, it looks like those changes will show up in the upcoming 2.2.
>
> I've been testing those changes in OpenBMC <https://github.com/openbmc/openbmc> (Krogoth-based) and can successfully generate a fitImage with an initramfs. Currently, kernel-fitimage.bbclass only stores an uncompressed initramfs which is problematic for the SoC I'm working on. In short, even once 2.2 is released, fitImage w/ initramfs may not quite work for you yet.
>
>
CC'ing krogoth maintainer for back port consideration
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161027/af7d2e2e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161027/af7d2e2e/attachment.pgp>
More information about the yocto
mailing list