From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Diego Rondini <diego.rondini@kynetics.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] image_types: declare support for wic.zst
Date: Thu, 14 May 2020 22:59:06 +0100 [thread overview]
Message-ID: <a040ae6cce408cb4dfaa7f302679d426b65e66c1.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMfw5YopZDvTBsL=zVKGTLPv5uvfmJ0L7j+y0r9PpO7drYwKMQ@mail.gmail.com>
On Thu, 2020-05-14 at 23:53 +0200, Diego Rondini wrote:
> Hi Richard,
>
> On Thu, May 14, 2020 at 11:21 PM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > On Thu, 2020-05-14 at 15:19 +0200, Diego wrote:
> > > Declare images in wic.zst format as supported, as bmaptool now supports
> > > zstd:
> > > https://github.com/intel/bmap-tools/commit/1b8437d58447d3796dc11fd0f2c62bec5746e5d6
> > > Given the very fast decompression speed of zstd over, for example, gzip,
> > > writing images with bmaptool can provide big write speed improvements
> > > when decompression speed is the limiting factor (especially with very
> > > sparse images).
> > >
> > > Signed-off-by: Diego Rondini <diego.rondini@kynetics.com>
> > > ---
> > > meta/classes/image_types.bbclass | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> > > index f82f1d8862..ab05cc90ff 100644
> > > --- a/meta/classes/image_types.bbclass
> > > +++ b/meta/classes/image_types.bbclass
> > > @@ -273,7 +273,7 @@ IMAGE_TYPES = " \
> > > ubi ubifs multiubi \
> > > tar tar.gz tar.bz2 tar.xz tar.lz4 tar.zst \
> > > cpio cpio.gz cpio.xz cpio.lzma cpio.lz4 \
> > > - wic wic.gz wic.bz2 wic.lzma \
> > > + wic wic.gz wic.bz2 wic.lzma wic.zst \
> > > container \
> > > f2fs \
> > > "
> >
> > Causes selftest failures:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/931
> >
> > (oe-selftest -r imagefeatures.ImageFeatures.test_image_fstypes)
> >
>
> I'm wondering how this didn't pop up earlier. The following patch introduced zstd support:
> http://git.openembedded.org/openembedded-core/commit/meta/classes/image_types.bbclass?id=77e0f502020085875bbc74da66815c89f19a9351
> of course specifying a DEPENDS on zstd-native:
> http://git.openembedded.org/openembedded-core/tree/meta/classes/image_types.bbclass?h=yocto-3.1#n316
> but... zstd is NOT in oe-core, but in meta-oe!
> http://layers.openembedded.org/layerindex/recipe/116635/
>
> I guess the solution for master is to move zstd to oe-core, right?
>
> But what about dunfell? It has the zstd support in image_types.bbclass patch, but we can't add zstd. Shall we revert the patch?
I think:
meta/lib/oeqa/selftest/cases/imagefeatures.py: blacklist = set(('container', 'elf', 'f2fs', 'multiubi', 'tar.zst'))
may be the clue to fixing this.
Cheers,
Richard
next prev parent reply other threads:[~2020-05-14 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 13:19 [PATCH] image_types: declare support for wic.zst Diego
2020-05-14 21:21 ` [OE-core] " Richard Purdie
2020-05-14 21:53 ` Diego
2020-05-14 21:59 ` Richard Purdie [this message]
2020-05-14 22:08 ` Diego
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a040ae6cce408cb4dfaa7f302679d426b65e66c1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=diego.rondini@kynetics.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox