From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Mon, 6 Dec 2010 13:06:39 -0500 Subject: [U-Boot] [PATCH 1/2] Add support for XZ decompression algorithm. In-Reply-To: <1291658317.20072.664.camel@petert> References: <1291562184-27126-1-git-send-email-luigi.mantellini@idf-hit.com> <1291658317.20072.664.camel@petert> Message-ID: <201012061306.40676.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Monday, December 06, 2010 12:58:37 Peter Tyser wrote: > On Sun, 2010-12-05 at 16:16 +0100, Luigi 'Comio' Mantellini wrote: > > XZ (aka LZMA2) is the new version of lzma compression format. > > The following patch add a cut-down version of XZ Embedded library > > (v20100702) that supports only single-call API. > > > > In order to enable XZ support, the CONFIG_XZ must be defined by board > > configuration file. > > > > For any details, please refer to XZ Embedded homesite > > (http://tukaani.org/xz/embedded.html) > > If I understand the xz format correctly, its nearly identical to lzma, > and the 'xz' utility can decompress .lzma files too. Any chance the xz > code you're adding can be used to handle lzma-compressed archives? If > so, can we deprecate CONFIG_LZMA and have the new CONFIG_XZ support > handle both .xz and .lzma archives? Or at least share a significant > chunk of code between the two formats? my understanding is that the compression algorithm is the same, but the ".xz" file format adds nice/detectable header of metadata where as ".lzma" does not. so yes, i believe the two should have quite a lot of [undesirable] overlap. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20101206/8702d35a/attachment.pgp