From: Olof Johansson <olof@lixom.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Joel Schopp <jschopp@austin.ibm.com>,
linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: Merging ppc32 and ppc64
Date: Tue, 9 Aug 2005 09:52:59 -0500 [thread overview]
Message-ID: <20050809145259.GH7163@austin.ibm.com> (raw)
In-Reply-To: <bb9b1e9e1ebdc3ac5b23b3cab327bfd5@kernel.crashing.org>
On Tue, Aug 09, 2005 at 03:09:02PM +0200, Segher Boessenkool wrote:
> _Please_ don't throw the real device tree away; I'm happy with
> the flattened device tree if and only if it is a _minimum_
> requirement, and having a _real_ device tree (or even real
> Open Firmware support) is still an option.
We already do that. prom_init.c will walk the OF device tree and build a
flattened one before booting the kernel.
-Olof
next prev parent reply other threads:[~2005-08-09 15:12 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
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 [this message]
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=20050809145259.GH7163@austin.ibm.com \
--to=olof@lixom.net \
--cc=jschopp@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=segher@kernel.crashing.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.