From: Sam Ravnborg <sam@ravnborg.org>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Tim Bird <tim.bird@am.sony.com>,
lasse.collin@tukaani.org, glp@openwrt.org,
linux-embedded@vger.kernel.org
Subject: Re: LZMA inclusion
Date: Wed, 3 Dec 2008 21:20:09 +0100 [thread overview]
Message-ID: <20081203202009.GA6790@uranus.ravnborg.org> (raw)
In-Reply-To: <20081203195852.GB8563@mx.loc>
On Wed, Dec 03, 2008 at 08:58:52PM +0100, Bernhard Reutner-Fischer wrote:
> On Wed, Dec 03, 2008 at 11:36:45AM -0800, Tim Bird wrote:
> >Gregers Petersen wrote:
> >> There was a small talk a few days ago involving a few of the OpenWrt
> >> developers and David Woodhouse. One of the topics discussed, was a
> >> question about the potential of including LZMA in the kernel.
> >> Such an inclusion would be quite benefitial in terms of embedded
> >> systems, but the major hurdle seems to be the code quality of LZMA itself.
> >> This leads to the question I would like to raise; are there ongoing
> >> plans (or considerations) to rewrite and merge LZMA, and has anyone
> >> started working on it in practical terms?
> >
> >Did anyone answer this? CELF is currently considering funding
> >a project to do this (add LZMA support to the kernel), and
> >it would be good to get a feel for the current status...
> > -- Tim
>
> AFAIK xz will be/is incompatible with this older LZMA, perhaps
> larhzu wants to chime in on that.
>
> PS: A previous incarnation of that patch didn't work conventiently
> for me, i had to do some small adjustments to the way it was put
> into the kernel configury, like
> http://repo.or.cz/w/buildroot.git?a=blob_plain;f=toolchain/kernel-headers/lzma/linux-2.6.22.1-002-lzma-vmlinuz.01.patch;hb=HEAD
> http://repo.or.cz/w/buildroot.git?a=blob_plain;f=toolchain/kernel-headers/lzma/linux-2.6.22.1-003-lzma-vmlinuz.patch;hb=HEAD
If these are required with latest kernel could I then ask you to
properly submit them to: linux-kbuild@vger.kernel.org
No need to have good patches sitting at random places.
Sam
next prev parent reply other threads:[~2008-12-03 20:20 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 [this message]
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
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=20081203202009.GA6790@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--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).