From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Vivek Goyal <vgoyal@in.ibm.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: another RFC patch: bzImage with ELF payload
Date: Fri, 01 Jun 2007 12:42:15 -0700 [thread overview]
Message-ID: <46607697.7060402@goop.org> (raw)
In-Reply-To: <m1lkf3zdki.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
> Jeremy Fitzhardinge <jeremy@goop.org> writes:
>
>
>> Jeremy Fitzhardinge wrote:
>>
>>> BTW, this won't apply as-is; I have some mucking-around patches to try
>>> and get the linux/elf*.h headers into a bit more order, but that's not
>>> ready yet.
>>>
>>>
>> BTW2: I've been basically ignoring zImage. Do we need to support it at
>> all? Has anyone used it in the last 10 years?
>>
>
> zImage is uninteresting. I think HPA explicitly dropped support a few
> years ago so we can't even build it.
>
Hm, its still there, and he put explicit support for it into the new
bootcode rewrite. Doesn't boot for me though.
> That said a bImage (non-compressed bzImage). Might actually be
> interesting.
>
That's pretty easy in my current plan. You just glue vmlinux into the
image rather than compressor+compressed data.
J
next prev parent reply other threads:[~2007-06-01 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 17:58 another RFC patch: bzImage with ELF payload Jeremy Fitzhardinge
2007-06-01 18:00 ` Jeremy Fitzhardinge
2007-06-01 19:20 ` Eric W. Biederman
2007-06-01 19:42 ` Jeremy Fitzhardinge [this message]
2007-06-01 21:38 ` H. Peter Anvin
2007-06-01 21:38 ` 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=46607697.7060402@goop.org \
--to=jeremy@goop.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=vgoyal@in.ibm.com \
--cc=virtualization@lists.osdl.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).