From: Tom Rini <trini@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc64-dev@ozlabs.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Merging ppc32 and ppc64
Date: Tue, 9 Aug 2005 09:21:33 -0700 [thread overview]
Message-ID: <20050809162133.GL3187@smtp.west.cox.net> (raw)
In-Reply-To: <80BD2461-35F1-4B9D-983E-E2BCFFC08C77@freescale.com>
On Tue, Aug 09, 2005 at 10:01:05AM -0500, Kumar Gala wrote:
> >I think you are both right, just using different terminology. The
> >running kernel uses its own representation of the device tree, which
> >is neither the flattened stuff nor using the OF interfaces. The
> >conversion from OF to the flattened tree is done by the kernel itself.
> >
> > Apple OF \
> > SLOF \
> > pSeries |-1- prom_init------,
> > PIBS / \
> > ... / \
> > \
> > other -----------------------------2--
> >unflatten_device_tree--3--
> > boot loader /
> > /
> > iSeries ----------- early_setup---`
> >
> >All "regular" machines enter in the traditional prom_init path (1)
> >from Open Firmware. The embedded machines that are too memory
> >constraint
> >to use SLOF have a flattened device tree in their boot loader and the
> >legacy iSeries boxes can fake the device tree in their
> >iSeries_early_setup
> >function. The main entry point (2) is entered by all machines when the
> >flattened device tree is there and the kernel builds its tree
> >representation
> >for run time (3).
>
> I guess my point is that in the "new" powerpc arch doing steps 1 & 3
> should no longer be part of the kernel proper. The should be handled
> by boot wrappers of some form. I know Ben tool care to ensure that
> prom_init was isolated from kernel proper and I'm suggesting we move
> it into a boot wrapper going forward.
That's not 100% true because as Segher said, prom_init.c is part of the
kernel (tree, image), but is what does the translation.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-08-09 16:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 3:07 Merging ppc32 and ppc64 Paul Mackerras
2005-08-03 5:48 ` Fwd: " Kumar Gala
2005-08-08 17:59 ` Joel Schopp
2005-08-08 23:48 ` Paul Mackerras
2005-08-09 13:09 ` Segher Boessenkool
2005-08-09 13:11 ` Geert Uytterhoeven
2005-08-09 13:30 ` Segher Boessenkool
2005-08-09 14:12 ` Kumar Gala
2005-08-09 14:47 ` Arnd Bergmann
2005-08-09 15:01 ` Kumar Gala
2005-08-09 16:21 ` Tom Rini [this message]
2005-08-09 17:41 ` Kumar Gala
2005-08-09 17:47 ` Tom Rini
2005-08-09 18:49 ` Kumar Gala
2005-08-09 15:16 ` Segher Boessenkool
2005-08-09 22:55 ` Paul Mackerras
2005-08-09 23:00 ` Kumar Gala
2005-08-10 10:15 ` Segher Boessenkool
2005-08-09 14:52 ` Olof Johansson
2005-08-09 22:48 ` Paul Mackerras
2005-08-10 10:51 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 2:37 Goodman, Brad
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=20050809162133.GL3187@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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 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).