All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: OpenSolaris and multiboot
Date: Sat, 25 Nov 2006 04:08:54 +0100	[thread overview]
Message-ID: <200611250408.55885.okuji@enbug.org> (raw)
In-Reply-To: <1164221907.29546.2.camel@basalt>

On Wednesday 22 November 2006 19:58, Hollis Blanchard wrote:
> I think he's referring to the "architecture-specific" tags (which are
> currently not fleshed out in the spec). There are different sections for
> x86 and x86-64, and it is a good question about when each is used.
>
> I'm really not sure what would be different about the two sets, but if
> there are differences, the ELF class seems like a reasonable way to
> decide which to use.

No difference, in my opinion. GRUB never activate 64-bit mode, and the 
firmware behaves exactly in the same way. Thus we don't need to pass 
different tags.

Briefly, i386 and x86_64 are treated identically in the Multiboot 
Specification. I wrote some notes about x86_64, only because I had to make it 
clear how to initialize additional registers before passing the control to a 
kernel.

Okuji



      reply	other threads:[~2006-11-25  3:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1163802029.20484.53.camel@basalt>
     [not found] ` <456252C2.1060101@sun.com>
2006-11-21 16:01   ` OpenSolaris and multiboot Hollis Blanchard
2006-11-21 23:25     ` Joe Bonasera
2006-11-22  9:41       ` Johan Rydberg
2006-11-22 18:58         ` Hollis Blanchard
2006-11-25  3:08           ` Yoshinori K. Okuji [this message]

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=200611250408.55885.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.