From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: EFI and binary distributors
Date: Tue, 1 May 2007 23:01:26 +0200 [thread overview]
Message-ID: <200705012301.26473.okuji@enbug.org> (raw)
In-Reply-To: <20070501201001.GA21299@aragorn>
On Tuesday 01 May 2007 22:10, Robert Millan wrote:
> What is the recommended way for binary distributors of GRUB to support
> PC/BIOS and EFI at the same time? Is it possible to build a mixed binary
> that supports both systems somehow? (and if it isn't, are there plans or
> ongoing work for that?)
I don't think so. The size restriction is too severe for PC BIOS.
One possibility is to bundle binary images both for PC BIOS and EFI in a
package, and selectively use one of them by grub-install. But this has a
serious issue, on a EFI platform which supports Legacy Boot, because the user
can use both.
Personally, I think it is much cleaner to use just EFI on EFI platforms
instead of Legacy Boot. But this depends on a preference... For now, I have
no good idea.
> Also, which are the cpu platforms that may use EFI? From what I could
> find, it seems that:
>
> - ia32 doesn't have it
You forgot about Intel Mac. :)
In fact, my Mac Mini is with Intel Core Solo, which definitely does not
support 64-bit.
> - ia64 always has it
> - amd64 only has it on Intel-Macs, and will have it on more devices in
> the future
Do Intel Mac have AMD processors, or do you mean EM64T? If you just mean IA-32
architecture with 64-bit extensions (both Intel's and AMD's), the canonical
name in GNU is "x86_64".
> Am I missing something?
No idea. In theory, nothing prevents porting EFI to other architectures.
Wikipedia mentions XScale:
http://en.wikipedia.org/wiki/Extensible_Firmware_Interface
Okuji
next prev parent reply other threads:[~2007-05-01 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 20:10 EFI and binary distributors Robert Millan
2007-05-01 21:01 ` Yoshinori K. Okuji [this message]
2007-05-02 13:42 ` Robert Millan
2007-05-02 13:49 ` Stefan Reinauer
2007-05-03 5:24 ` Hollis Blanchard
2007-05-01 21:03 ` Marco Gerards
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=200705012301.26473.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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 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.