[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B21656B.1090607@lougher.demon.co.uk>
Date: Thu, 10 Dec 2009 21:17:31 +0000
From: Phillip Lougher <phillip@...gher.demon.co.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
CC: dedekind1@...il.com, Andrew Morton <akpm@...ux-foundation.org>,
linux-embedded@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, phillip.lougher@...il.com,
Tim Bird <tim.bird@...sony.com>,
Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>,
Felix Fietkau <nbd@...nwrt.org>
Subject: Re: [PATCH 1/9] Squashfs: move zlib decompression wrapper code into
a separate file
Geert Uytterhoeven wrote:
>
>> Yes I did consider using the cryptoapi, but this doesn't have support for
>> lzma in mainline.
>
> IIRC, Felix Fietkau added support for that for OpenWRT...
>
Yes, but it isn't in mainline, and OpenWRT don't appear to have tried to submit
it. IMHO the major problem with their patch is it uses a second private copy
of lzma, rather than being a wrapper around the pre-existing lzma implementation.
I don't think it's going to be easy to get a second lzma implementation accepted
into mainline, when it took so long to get one accepted. I have nothing against
the cryptoapi, but it doesn't seem likely to be getting lzma support anytime soon.
As I previously said my aim is to use the pre-existing lzma implementation. Unless
it is stupendously bad (which it isn't), that seems to be the quickest, easiest and
best way to get lzma support into Squashfs.
Phillip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists