From: "Huang, Ying" <ying.huang@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC -mm 0/2] i386/x86_64 boot: 32-bit boot protocol
Date: Mon, 17 Sep 2007 16:47:35 +0800 [thread overview]
Message-ID: <1190018855.5866.27.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <200709171040.27043.ak@suse.de>
On Mon, 2007-09-17 at 10:40 +0200, Andi Kleen wrote:
> On Monday 17 September 2007 10:26:12 Huang, Ying wrote:
> > For machine with some new BIOS other than legacy BIOS, such as EFI,
> > LinuxBIOS, etc, and kexec, the 16-bit real mode setup code in kernel
> > based on legacy BIOS can not be used, so a 32-bit boot protocol need
> > to be defined.
>
> The patch doesn't seem to be what you advertise in the description.
> Can you start with a patch that just implements the new boot protocol
> parsing for better review? The EFI code should be all in separate
> patches.
> -Andi
The real contents of 32-bit boot protocol patch is is in another 2 mails
with the title:
[RFC -mm 1/2] i386/x86_64 boot: setup data
[RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol
The EFI patch in this mail is just an example of 32-bit boot protocol
usage.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2007-09-17 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 8:26 [RFC -mm 0/2] i386/x86_64 boot: 32-bit boot protocol Huang, Ying
2007-09-17 8:40 ` Andi Kleen
2007-09-17 8:47 ` Huang, Ying [this message]
2007-09-17 14:30 ` Andi Kleen
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=1190018855.5866.27.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=yhlu.kernel@gmail.com \
/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