All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <ak@suse.de>,
	Chandramouli Narayanan <mouli@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86_64 EFI runtime service support
Date: Mon, 20 Aug 2007 21:13:44 +0100	[thread overview]
Message-ID: <20070820201344.GA13059@srcf.ucam.org> (raw)
In-Reply-To: <46C9C9C7.8080506@zytor.com>

On Mon, Aug 20, 2007 at 10:05:11AM -0700, H. Peter Anvin wrote:
> Yinghai Lu wrote:
> > 
> > someone told me that EFI PEI will be 32 bit ( for mem etc
> > initialization), and after that will be 64 bit, so the Run time
> > service will be 64 bit only, and it will only support 64 bit OS with
> > EFI. and they have another mode to emulate the legacy BIOS to boot
> > 32bit OS.
> > 
> 
> That seems unlikely for e.g. the existing Macs already in the field.

In which direction? The existing Macs will boot a 32 (or 16) bit OS 
using legacy BIOS emulation. I've no idea if their EFI is 32 or 64 bit, 
though.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  parent reply	other threads:[~2007-08-20 20:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  7:30 [PATCH 0/3] x86_64 EFI runtime service support Huang, Ying
2007-08-15 22:42 ` Andrew Morton
2007-08-16  7:51   ` Huang, Ying
2007-08-16 14:11     ` Andi Kleen
2007-08-17  1:25       ` Huang, Ying
2007-08-17 16:11         ` H. Peter Anvin
2007-08-20  3:20           ` Huang, Ying
2007-08-20 17:12             ` H. Peter Anvin
2007-08-21  1:44               ` Huang, Ying
2007-08-21  3:54                 ` H. Peter Anvin
2007-08-21  4:53                   ` Huang, Ying
2007-08-21 11:33               ` Andi Kleen
2007-08-21 10:41                 ` H. Peter Anvin
2007-08-21 11:45                   ` Andi Kleen
2007-08-21 23:58                     ` Yinghai Lu
2007-08-22  1:22                       ` Andi Kleen
2007-08-22  6:43                         ` Yinghai Lu
2007-08-22 11:11                           ` Andi Kleen
2007-08-22 14:23                             ` huang ying
2007-08-22 16:28                               ` H. Peter Anvin
2007-08-23  2:21                                 ` Huang, Ying
2007-08-23  2:46                                   ` H. Peter Anvin
2007-08-22 14:41                             ` Eric W. Biederman
2007-08-22 16:44                               ` H. Peter Anvin
2007-08-22  7:20                         ` Yinghai Lu
2007-08-15 23:16 ` Andrew Morton
2007-08-15 23:22   ` H. Peter Anvin
2007-08-16  8:00     ` Huang, Ying
2007-08-16 16:09       ` H. Peter Anvin
2007-08-19 22:27         ` Eric W. Biederman
2007-08-19 22:25       ` Eric W. Biederman
2007-08-19 23:46         ` Yinghai Lu
2007-08-20 17:05           ` H. Peter Anvin
2007-08-20 17:20             ` San Mehat
2007-08-20 20:13             ` Matthew Garrett [this message]
2007-08-20  5:14         ` Huang, Ying
2007-08-16  7:52   ` Huang, Ying

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=20070820201344.GA13059@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --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 \
    --cc=ying.huang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.