From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Joel Schopp <jschopp@austin.ibm.com>,
linuxppc64-dev@ozlabs.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Merging ppc32 and ppc64
Date: Tue, 9 Aug 2005 17:16:05 +0200 [thread overview]
Message-ID: <265a318e3c20a3ba217e374d12a8f9f6@kernel.crashing.org> (raw)
In-Reply-To: <3F1564F6-3732-403B-BA6B-BFAB28568AEE@freescale.com>
> I was under the impression that ALL platforms regardless if the had a
> OF firmware or not would be using a flattened device tree. Any
> conversion between an OF tree to a flatten tree would end up happening
> in boot wrapper code going forward.
Ah OK -- so part of the problem is indeed terminology
confusion. I view the "boot wrapper code" (prom_init.c)
as being part of the kernel.
Another thing is that I do not want prom_init to kill
OF at all, which means you cannot have a static device
tree. But that is another fight ;-)
Segher
next prev parent reply other threads:[~2005-08-09 15:16 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
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 [this message]
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=265a318e3c20a3ba217e374d12a8f9f6@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=jschopp@austin.ibm.com \
--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).