All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: Johan Rydberg <jrydberg@night.trouble.net>
Cc: The development of GRUB 2 <grub-devel@gnu.org>, jan.setje-eilers@sun.com
Subject: Re: OpenSolaris and multiboot
Date: Wed, 22 Nov 2006 12:58:27 -0600	[thread overview]
Message-ID: <1164221907.29546.2.camel@basalt> (raw)
In-Reply-To: <87u00rhl7w.fsf@night.trouble.net>

On Wed, 2006-11-22 at 10:41 +0100, Johan Rydberg wrote:
> Joe Bonasera <joe.bonasera@sun.com> writes:
> 
> > Would the different tags i86-pc vs x86_64 (if any) be determined by
> > knowing if which type elf gets loaded?
> 
> My personal opinion is that we should not pass any information to the
> kernel about what format it is provided in.  
> 
> If the image is an ELF64, it will be loaded as an ELF64.  So in your
> case, for x86_64 hosts, provide the kernel as an ELF64 image.  For
> IA-32, provide an ELF32 image.

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.

-Hollis




  reply	other threads:[~2006-11-22 18:59 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 [this message]
2006-11-25  3:08           ` Yoshinori K. Okuji

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=1164221907.29546.2.camel@basalt \
    --to=hollis@penguinppc.org \
    --cc=grub-devel@gnu.org \
    --cc=jan.setje-eilers@sun.com \
    --cc=jrydberg@night.trouble.net \
    /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.