From: "Nguyen Anh Quynh" <aquynh@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kvm-devel@lists.sourceforge.net, Alexander Graf <alex@csgraf.de>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: [RFC] linuxboot Option ROM for Linux kernel booting
Date: Wed, 23 Apr 2008 22:49:34 +0900 [thread overview]
Message-ID: <9cde8bff0804230649q6a7825cdk69cc0f8ef6117994@mail.gmail.com> (raw)
In-Reply-To: <480E10E5.1000401@zytor.com>
On 4/23/08, H. Peter Anvin <hpa@zytor.com> wrote:
> Nguyen Anh Quynh wrote:
>
> > Hi,
> >
> > I am thinking about comibing this ROM with the extboot. Both two ROM
> > are about "booting", so I think that is reasonable. So we will have
> > only 1 ROM that supports both external boot and Linux boot.
> >
> > Is that desirable or not?
> >
> >
>
> Does it make the code simpler and easier to understand? If not, then I would say no.
Actually no. I must say that it looks ugly to me.
The fact is that linuxboot ROM and extboot ROM are about different
things, and they only share a bit in that they both intercept int 19.
I very much like the the Unix principal, that is "Does one thing, and
does it well", so I prefer to have 2 independent ROM: one to boot
Linux, and one to do external boot. I see no problem that we have more
than one ROM, and these two can be independently loaded into the
memory.
So I think I agree with Peter here.
Thanks,
Q
next prev parent reply other threads:[~2008-04-23 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 3:32 [Qemu-devel] [RFC] linuxboot Option ROM for Linux kernel booting Nguyen Anh Quynh
2008-04-21 3:33 ` [Qemu-devel] " Nguyen Anh Quynh
2008-04-21 3:36 ` Nguyen Anh Quynh
2008-04-22 9:07 ` Nguyen Anh Quynh
2008-04-22 10:35 ` Alexander Graf
2008-04-23 13:40 ` Nguyen Anh Quynh
2008-04-22 13:45 ` Anthony Liguori
2008-04-22 16:23 ` H. Peter Anvin
2008-04-23 13:49 ` Nguyen Anh Quynh [this message]
2008-04-22 13:50 ` Anthony Liguori
2008-04-22 15:02 ` Laurent Vivier
2008-04-23 13:41 ` Nguyen Anh Quynh
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=9cde8bff0804230649q6a7825cdk69cc0f8ef6117994@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=alex@csgraf.de \
--cc=aliguori@us.ibm.com \
--cc=hpa@zytor.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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).