From: nico@fluxnic.net (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/4] Add support for LZ4-compressed kernels
Date: Thu, 31 Jan 2013 17:16:27 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1301311700470.6300@xanadu.home> (raw)
In-Reply-To: <510AE6BF.4080303@zytor.com>
On Thu, 31 Jan 2013, H. Peter Anvin wrote:
> On 01/30/2013 10:33 AM, Nicolas Pitre wrote:
> >>
> >> The only concern I have with that is if someone paints themselves into a
> >> corner and absolutely wants, say, LZO.
> >
> > That would be hard to justify given that the kernel provides its own
> > decompressor code, making the compression format transparent to
> > bootloaders, etc. And no one should be poking into the compressed
> > zImage.
> >
>
> Some utterly weird things like the Xen domain builder do that, because
> they have to. That is why we explicitly document that the payload is
> ELF and how to access it in the bzImage spec.
Are you kidding?
And what format do they expect?
If people are doing weird things with formats we're about to remove then
it's their fault if they didn't make upstream developers aware of it.
And if the reason they didn't tell anyone is because it is too nasty for
public confession then they simply deserve to be broken and come up with
a more sustainable solution.
Nicolas
next prev parent reply other threads:[~2013-01-31 22:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 5:50 [RFC PATCH 0/4] Add support for LZ4-compressed kernels Kyungsik Lee
2013-01-26 5:50 ` [RFC PATCH 1/4] decompressors: add lz4 decompressor module Kyungsik Lee
2013-01-26 5:50 ` [RFC PATCH 2/4] lib: add support for LZ4-compressed kernels Kyungsik Lee
2013-01-26 5:50 ` [RFC PATCH 3/4] arm: " Kyungsik Lee
2013-01-26 5:50 ` [RFC PATCH 4/4] x86: " Kyungsik Lee
2013-01-28 22:25 ` [RFC PATCH 0/4] Add " Andrew Morton
2013-01-29 1:16 ` kyungsik.lee
2013-01-29 4:29 ` Nicolas Pitre
2013-01-29 6:18 ` H. Peter Anvin
2013-01-30 10:23 ` Johannes Stezenbach
2013-02-04 2:02 ` Markus F.X.J. Oberhumer
2013-02-04 10:50 ` Russell King - ARM Linux
2013-02-05 11:39 ` Johannes Stezenbach
2013-01-29 7:26 ` Richard Cochran
2013-01-29 10:15 ` Russell King - ARM Linux
2013-01-29 11:43 ` Egon Alter
2013-01-29 12:15 ` Russell King - ARM Linux
2013-02-01 8:15 ` kyungsik.lee
2013-01-30 3:36 ` H. Peter Anvin
2013-01-30 18:33 ` Nicolas Pitre
2013-01-31 21:48 ` H. Peter Anvin
2013-01-31 22:16 ` Nicolas Pitre [this message]
2013-01-31 22:18 ` H. Peter Anvin
2013-02-01 2:28 ` Nicolas Pitre
2013-02-01 6:37 ` H. Peter Anvin
2013-01-29 21:09 ` Rajesh Pawar
2013-02-01 7:00 ` kyungsik.lee
2013-02-04 1:37 ` Markus F.X.J. Oberhumer
2013-01-29 22:55 ` David Sterba
2013-01-30 4:03 ` 이경식
2013-01-30 4:27 ` 이경식
2013-02-01 7:13 ` kyungsik.lee
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=alpine.LFD.2.02.1301311700470.6300@xanadu.home \
--to=nico@fluxnic.net \
--cc=linux-arm-kernel@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 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).