From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2: variable data size
Date: Tue, 28 Nov 2006 12:35:48 +0100 [thread overview]
Message-ID: <200611281235.48809.okuji@enbug.org> (raw)
In-Reply-To: <87psb7hqc4.fsf@night.trouble.net>
On Tuesday 28 November 2006 10:29, Johan Rydberg wrote:
> "Yoshinori K. Okuji" <okuji@enbug.org> writes:
> > On Saturday 25 November 2006 04:33, Hollis Blanchard wrote:
> >> That's exactly the point: there will be no difference. Both
> >> architectures will use 64-bit types.
> >
> > No. Both should use 32-bit, because GRUB transfers control in 32-bit
> > mode. Passing 64-bit addresses would be useless in this case. Note that
> > the memory map information is 64-bit even in the previous version of
> > Multiboot Spec.
>
> That will not be true for x86_64-efi, which will have to run in long
> mode.
Oh, sorry. I meant "x86_64-pc" in the previous message. I just omitted "pc".
When the firmware is different, it is feasible to make a different spec,
but...
But is it true that EFI starts with 64-bit mode? Where is it defined? In UEFI?
Could you give me a pointer?
Okuji
next prev parent reply other threads:[~2006-11-28 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <iss.8f960c3c.4ebf.45648480.44026.78@relay0i.sun.com>
2006-11-22 20:55 ` Grub-devel Digest, Vol 33, Issue 19 Joe Bonasera
2006-11-25 2:09 ` multiboot2: variable data size Hollis Blanchard
2006-11-25 3:10 ` Yoshinori K. Okuji
2006-11-25 3:33 ` Hollis Blanchard
2006-11-25 3:46 ` Yoshinori K. Okuji
2006-11-25 4:08 ` Hollis Blanchard
2006-11-25 4:36 ` Yoshinori K. Okuji
2006-11-25 5:01 ` Hollis Blanchard
2006-11-28 9:29 ` Johan Rydberg
2006-11-28 11:35 ` Yoshinori K. Okuji [this message]
2006-11-28 12:46 ` bibo,mao
2006-11-28 23:29 ` Yoshinori K. Okuji
2006-11-29 1:55 ` bibo,mao
2006-11-29 2:37 ` Andrei E. Warkentin
2006-11-29 0:22 ` Johan Rydberg
2006-11-29 2:13 ` bibo,mao
2006-11-28 12:50 ` tgingold
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=200611281235.48809.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.