linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: Sven Luther <sven.luther@wanadoo.fr>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: chrp mmu and booting.
Date: Fri, 23 Jan 2004 14:49:44 -0600	[thread overview]
Message-ID: <1074890984.2840.25.camel@otta.rchland.ibm.com> (raw)
In-Reply-To: <20040123185433.GB5125@iliana>


On Fri, 2004-01-23 at 12:54, Sven Luther wrote:
> Yeah, but in my case, i have no yaboot, and i know that these boxes are
> also capable of booting from the OF.

Yes, you can boot any 32-bit ELF binary from OF.  Yaboot and the zImage
wrapper for the 64-bit kernel are both 32-bit ELF binaries, so you can
boot either of these.  Note that you cannot boot a plain PPC64 vmlinux,
as the OF ELF loader doesn't support 64-bit ELF binaries.


> But then, how comes the OF translate call is able to map the address 0
> to the 0x10000 address ?

In real mode, there is no address mapping done.  When the kernel starts
executing, we are not loaded where we were linked at, so we must be very
careful about what we touch.  You'll see in arch/ppc64/kernel/prom.c,
that we use the RELOC() macro to access global data.  It essentially
maps the virtual/effective address the kernel expects things to be at
to the physical address it's actually loaded at.  The ppc32 kernel was
able to remove the RELOC() macro, but for various reasons, the PPC64
kernel is still stuck using it.


Peter


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-01-23 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 11:17 chrp mmu and booting Sven Luther
2004-01-23 18:44 ` Peter Bergner
2004-01-23 18:54   ` Sven Luther
2004-01-23 20:49     ` Peter Bergner [this message]
2004-01-24  1:06       ` Benjamin Herrenschmidt
2004-01-24 20:01       ` Geert Uytterhoeven
2004-01-26  7:52       ` Segher Boessenkool
2004-01-24  1:08     ` Benjamin Herrenschmidt
2004-01-24  8:21       ` Sven Luther
2004-01-24 11:36         ` Benjamin Herrenschmidt
2004-01-26  7:51       ` Segher Boessenkool

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=1074890984.2840.25.camel@otta.rchland.ibm.com \
    --to=bergner@vnet.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=sven.luther@wanadoo.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).