From: Isaac Dupree <id@isaac.cedarswampstudios.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: x86_64 EFI support for grub2 ?
Date: Wed, 28 May 2008 16:15:34 -0400 [thread overview]
Message-ID: <483DBD66.5030407@isaac.cedarswampstudios.org> (raw)
In-Reply-To: <20080528141735.GI26495@thorin>
Robert Millan wrote:
> On Tue, May 27, 2008 at 08:23:09PM +0800, Bean wrote:
>> It's possible to create multiple arch image, but it requires some
>> extra work. We need to compile i386-efi and x86_64-efi separately,
>> then use a tool to merge them. This can't be done in a single step.
>
> Why not just drop the -m32 and always build "native" images? So if you
> build the i386-efi target on i386, you get a 32-bit image and if you build
> it on x86_64 you get a 64-bit one?
take the MacBook. There are different versions, let's call them (A),
the original MacBook, 32-bit CPU; (B), mine, 64-bit CPU; and (C),
Bean's, 64-bit CPU.
A and B require 32-bit EFI image. (actually, B might accept both 32 and
64 bits images, I'm not sure)
C requires 64-bit EFI image.
I can run a 32-bit distro and linux-kernel on any of them -- A, B or C.
I can run a 64-bit distro on B or C.
Basically, neither CPU nor system arch tells you what kind of EFI image
is "native". There must be some way to find out what kind of image *is*
native -- but I have no idea what it is.
-Isaac
next prev parent reply other threads:[~2008-05-28 20:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 11:32 x86_64 EFI support for grub2 ? Bean
2008-05-25 15:48 ` Isaac Dupree
2008-05-25 16:29 ` Bean
2008-05-26 13:21 ` Isaac Dupree
2008-05-28 14:15 ` Robert Millan
2008-05-25 16:44 ` Bean
2008-05-26 13:25 ` Isaac Dupree
2008-05-26 14:23 ` Bean
2008-05-26 19:11 ` Isaac Dupree
2008-05-26 19:43 ` Bean
2008-05-27 10:09 ` Isaac Dupree
2008-05-27 10:38 ` Bean
2008-05-27 12:06 ` Isaac Dupree
2008-05-27 12:23 ` Bean
2008-05-28 14:17 ` Robert Millan
2008-05-28 16:27 ` Vesa Jääskeläinen
2008-05-28 20:15 ` Isaac Dupree [this message]
2008-05-25 19:05 ` Marco Gerards
2008-05-28 14:20 ` Robert Millan
2008-05-28 14:37 ` Bean
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=483DBD66.5030407@isaac.cedarswampstudios.org \
--to=id@isaac.cedarswampstudios.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.