From: Joel Schopp <jschopp@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: Merging ppc32 and ppc64
Date: Mon, 08 Aug 2005 12:59:37 -0500 [thread overview]
Message-ID: <42F79D89.3040709@austin.ibm.com> (raw)
In-Reply-To: <17136.13558.773102.465379@cargo.ozlabs.ibm.com>
> I don't see the merge as changing the actual code that gets executed
> on any given platform very much, except in one respect: we are going
> to standardize on a flattened device tree as the way that information
> about the platform gets passed from the boot loader to the kernel.
>
> Comments? Flames? :)
There are several userspace applications that parse the non-flat device
tree in /proc/device-tree on pSeries. While I like the idea of the
flattened device tree I think we need to consider how many apps we are
going to break with it.
next prev parent reply other threads:[~2005-08-08 17:59 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 [this message]
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
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=42F79D89.3040709@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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).