From: "H. Peter Anvin" <hpa@zytor.com>
To: Rob Landley <rob@landley.net>
Cc: lkml <linux-kernel@vger.kernel.org>,
v12n <virtualization@lists.linux-foundation.org>,
Vivek Goyal <vgoyal@in.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH RFC 6/7] i386: make the bzImage payload an ELF file
Date: Thu, 07 Jun 2007 09:14:50 -0700 [thread overview]
Message-ID: <46682EFA.1020406@zytor.com> (raw)
In-Reply-To: <200706071208.04777.rob@landley.net>
Rob Landley wrote:
>
> Er, make that objcopy, not objdump.
>
> Sane, maybe not. Something people want to do (and under the mistaken
> assumption I know more about initramfs then they do, have asked me how), yes.
> It always boils down to "do you have a vmlinux image lying around? Doing
> this with a bzImage _is_ brain surgery", and has yet to get beyond that
> question. I had about half of a script worked out for this, once...
>
If it can be done today on a vmlinux then it can be done the same way
with the mechanism I have proposed. Period, full stop.
> You can also supply an external initramfs image through the initrd mechanism,
> but this is unpleasant to do with some bootloaders (or lack of bootloaders).
> Plus it doesn't remove the old one, and wasting space makes embedded
> developers itch.
In thory one could create an extended bzImage format which could handle
a concatenated, and easily replaceable, initrd, but if it's done on
vmlinux today it would make a *lot* more sense to have it be done on the
vmlinux and nothing else.
-hpa
next prev parent reply other threads:[~2007-06-07 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 22:58 [PATCH RFC 0/7] proposed updates to boot protocol and paravirt booting Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 1/7] update boot spec to 2.07 Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 2/7] add WEAK() for creating weak asm labels Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 3/7] allow linux/elf.h to be included in assembler Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 4/7] define ELF notes for adding to a boot image Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 5/7] i386: clean up bzImage generation Jeremy Fitzhardinge
2007-06-06 22:58 ` [PATCH RFC 6/7] i386: make the bzImage payload an ELF file Jeremy Fitzhardinge
2007-06-06 23:41 ` H. Peter Anvin
2007-06-06 23:56 ` Jeremy Fitzhardinge
[not found] ` <466749C8.2010700@goop.org>
2007-06-07 0:08 ` H. Peter Anvin
[not found] ` <46674C96.7090104@zytor.com>
2007-06-07 0:20 ` Jeremy Fitzhardinge
[not found] ` <46674F68.6030100@goop.org>
2007-06-07 0:42 ` H. Peter Anvin
[not found] ` <4667547B.8080502@zytor.com>
2007-06-07 1:01 ` Jeremy Fitzhardinge
2007-06-08 3:49 ` Vivek Goyal
[not found] ` <20070608034958.GA10728@in.ibm.com>
2007-06-08 4:01 ` H. Peter Anvin
2007-06-07 1:47 ` Rob Landley
[not found] ` <200706062147.21225.rob@landley.net>
2007-06-07 1:54 ` H. Peter Anvin
2007-06-07 16:08 ` Rob Landley
[not found] ` <200706071208.04777.rob@landley.net>
2007-06-07 16:14 ` H. Peter Anvin [this message]
2007-06-06 22:58 ` [PATCH RFC 7/7] i386: paravirt boot sequence Jeremy Fitzhardinge
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=46682EFA.1020406@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=vgoyal@in.ibm.com \
--cc=virtualization@lists.linux-foundation.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).