From: Florian Fainelli <florian@openwrt.org>
To: kexec@lists.infradead.org
Cc: Simon Horman <horms@verge.net.au>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] add support for loading lzma compressed kernels
Date: Tue, 17 Nov 2009 15:23:15 +0100 [thread overview]
Message-ID: <200911171523.15419.florian@openwrt.org> (raw)
In-Reply-To: <200911171508.29971.florian@openwrt.org>
On Tuesday 17 November 2009 15:08:29 Florian Fainelli wrote:
> Hello Simon,
>
> On Tuesday 17 November 2009 04:04:38 Simon Horman wrote:
> > On Mon, Nov 16, 2009 at 12:53:06AM +0100, Florian Fainelli wrote:
> > > Hi Eric,
> > >
> > > This patch allows one to load a lzma compressed kernel using kexec -l.
> > > As I wanted the lzma code to be very similar to the existing
> > > zlib slurp_decompress I took lzread and associated routines
> > > from the cpio lzma support. Tested on my x86 laptop using the
> > > following commands:
> > >
> > > lzma e bzImage bzImage.lzma
> > > kexec -l bzImage.lzma
> > >
> > > Having lzma support is particularly useful on some embedded
> > > systems on which we have the kernel already lzma compressed
> > > and available on a mtd partition.
> > >
> > > Signed-off-by: Florian Fainelli <florian@openwrt.org>
> >
> > Should lzma_code_ be lzma_code. The former doesn't seem to work with
> > liblzma 4.999.9beta+20091016-1 from Debian.
>
> You are right it's actually lzma_code (without the trailing _).
>
> > > + AC_MSG_NOTICE([lzma support disabled])))
> >
> > The trailing "fi" line appears to be missing.
>
> Fixed too.
> [snip]
>
> > Does this imply that zlib compression isn't supported if
> > lzma compression support is enabled?
>
> Indeed, we might want to support both at runtime. Would you agree with the
> following proposal:
>
> - rename slurp_decompress_file to zlib/lzma_decompress_file
> - in case gzopen fails, do not die, but return NULL
> - test the return value of zlib_decompress_file and try
> lzma_decompress_file
We would also have to modify the call sites of slurp_decompress file this might
become pretty heavy if we support more decompression algorithms. What do you
think?
--
WBR, Florian
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2009-11-17 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 23:53 [PATCH] add support for loading lzma compressed kernels Florian Fainelli
2009-11-16 13:37 ` wilbur.chan
2009-11-17 3:04 ` Simon Horman
2009-11-17 14:08 ` Florian Fainelli
2009-11-17 14:23 ` Florian Fainelli [this message]
2009-11-18 3:55 ` Simon Horman
2009-11-18 23:17 ` Florian Fainelli
2009-11-19 0:03 ` Eric W. Biederman
2009-11-30 5:51 ` Simon Horman
2009-11-30 10:08 ` Florian Fainelli
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=200911171523.15419.florian@openwrt.org \
--to=florian@openwrt.org \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.