LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: PATCH/RFC: bzImage payload as compressed ELF file.
Date: Tue, 29 Jan 2008 13:50:28 -0800 [thread overview]
Message-ID: <479F9FA4.8020504@zytor.com> (raw)
In-Reply-To: <1201639112.9516.23.camel@cthulhu.hellion.org.uk>
Ian Campbell wrote:
>
> I finessed the length issue slightly since it happens that the word
> before the payload is the payload's length. I'm mulling a variety of
> options:
> * declare it compression scheme dependant. At least for gzip it
> knows when it has reached the end.
> * codify the length followed by data thing we happen to have now
> * add a length field to the header, using another 4 bytes (is
> there any pressure on the size of the header?).
>
> I'd probably go with the later unless we are pressed for space in the
> header.
I would agree with that. In fact, while we're adding fields to the
header, I would like to add a field that would be the CRC32 (or other
simple integrity check) over the whole image.
-hpa
next prev parent reply other threads:[~2008-01-29 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 22:42 Ian Campbell
2008-01-28 22:54 ` Jeremy Fitzhardinge
2008-01-29 9:34 ` Ian Campbell
2008-01-29 17:54 ` Jeremy Fitzhardinge
2008-01-29 18:05 ` H. Peter Anvin
2008-01-29 18:31 ` Jeremy Fitzhardinge
2008-01-29 18:34 ` H. Peter Anvin
2008-01-29 20:38 ` Ian Campbell
2008-01-29 21:50 ` H. Peter Anvin [this message]
2008-01-29 21:55 ` Ian Campbell
2008-01-29 22:09 ` H. Peter Anvin
2008-01-28 23:20 ` H. Peter Anvin
2008-01-29 9:31 ` Ian Campbell
2008-02-01 13:10 ` Ingo Molnar
2008-02-01 18:05 ` H. Peter Anvin
2008-02-01 18:15 ` H. Peter Anvin
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=479F9FA4.8020504@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: PATCH/RFC: bzImage payload as compressed ELF file.' \
/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
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).