From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Lasse Collin <lasse.collin@tukaani.org>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Tim Bird <tim.bird@am.sony.com>,
glp@openwrt.org, linux-embedded@vger.kernel.org
Subject: Re: LZMA inclusion
Date: Thu, 4 Dec 2008 22:46:42 +0100 [thread overview]
Message-ID: <20081204214642.GF7336@game.jcrosoft.org> (raw)
In-Reply-To: <200812032348.36921.lasse.collin@tukaani.org>
> The primary compression algorithm of the .xz format is LZMA2. It fixes
> some practical problems of the original LZMA. The .xz format also
> supports filters for executable data (x86, ARM and a few others), which
> combined with LZMA2 usually improve compression ratio 5-10 % over plain
> LZMA or LZMA2. I suppose such filters would be useful in the kernel,
> since the kernel image and iniramfs contain mostly executable code.
>
> Final version of the .xz format specification will be released in this
> month. I try to get the first stable release or at least a good beta
> release of the xz package out in this month too.
>
> Once the stable release of the xz package is out, I could be willing to
> write an easy-to-use .xz decoder that is suitable for inclusion to
> Linux (including proper coding style with comments). I have understood,
> that for kernel and initramfs compression as well as for SquashFS, it
> would be enough to support single-call buffer-to-buffer decoding
> (comparable to uncompress() in zlib). Such code can be significantly
> simpler than stateful multi-call implementation.
This sound very good.
Please note that we also use it in U-Boot so if could help us to have it also
in it. It will be usefull
Best Regards,
J.
next prev parent reply other threads:[~2008-12-04 21:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 7:06 LZMA inclusion Gregers Petersen
2008-12-03 19:36 ` Tim Bird
2008-12-03 19:50 ` Florian Fainelli
2008-12-03 19:58 ` Bernhard Reutner-Fischer
2008-12-03 20:20 ` Sam Ravnborg
2008-12-03 20:45 ` Bernhard Reutner-Fischer
2008-12-03 21:16 ` Sam Ravnborg
2008-12-03 21:28 ` Bernhard Reutner-Fischer
2008-12-03 21:43 ` Sam Ravnborg
2008-12-03 21:48 ` Lasse Collin
2008-12-04 21:46 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-12-05 8:31 ` Geert Uytterhoeven
2008-12-06 21:56 ` Lasse Collin
2008-12-07 16:01 ` Jörn Engel
2008-12-07 23:32 ` Phillip Lougher
2008-12-08 13:46 ` Jamie Lokier
2008-12-08 18:23 ` Lasse Collin
2008-12-08 19:00 ` Phillip Lougher
2008-12-09 10:20 ` Lasse Collin
2008-12-09 10:37 ` Geert Uytterhoeven
2008-12-16 8:55 ` Lasse Collin
2008-12-08 20:17 ` Jörn Engel
2008-12-08 21:47 ` Phillip Lougher
2008-12-08 22:15 ` Jörn Engel
2008-12-03 20:09 ` Gregers Petersen
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=20081204214642.GF7336@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=glp@openwrt.org \
--cc=lasse.collin@tukaani.org \
--cc=linux-embedded@vger.kernel.org \
--cc=rep.dot.nop@gmail.com \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).