From: Matthew McClintock <msm@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Kumar Gala <kumar.gala@freescale.com>,
linuxppc-dev@lists.ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH V4] powerpc/prom: Export device tree physical address via proc
Date: Thu, 15 Jul 2010 01:17:22 -0500 [thread overview]
Message-ID: <1279174642.28344.6.camel@localhost> (raw)
In-Reply-To: <FFCEA7A1-6F2B-402F-A698-C882D0B4EB2E@kernel.crashing.org>
On Wed, 2010-07-14 at 17:46 +0200, Segher Boessenkool wrote:
> > What about just one node called "flat-device-tree"?
>
> But *what* flat device tree? It cannot be "the" flat device tree,
> or it would be useless information, since we are already reading it!
I thought about it all day and did not come up with anything terribly
insightful...
"boot-fdt-phys-addr"
"fdt-phys-addr"
"boot-fdt-phys-reg"
"fdt-phys-addr-reg"
Thoughts?
-M
next prev parent reply other threads:[~2010-07-15 6:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:18 [PATCH V4] powerpc/prom: Export device tree physical address via proc Matthew McClintock
2010-07-14 15:33 ` Tabi Timur-B04825
2010-07-14 15:35 ` Segher Boessenkool
2010-07-14 15:42 ` Matthew McClintock
2010-07-14 15:46 ` Segher Boessenkool
2010-07-15 6:17 ` Matthew McClintock [this message]
2010-07-15 6:21 ` Grant Likely
2010-07-15 15:19 ` Matthew McClintock
2010-07-15 16:22 ` Grant Likely
2010-07-15 16:39 ` Matthew McClintock
2010-07-15 16:57 ` Grant Likely
2010-07-15 18:03 ` Matthew McClintock
2010-07-15 18:37 ` Grant Likely
2010-07-15 18:58 ` Matthew McClintock
2010-07-15 19:18 ` Grant Likely
2010-07-16 5:44 ` Mitch Bradley
2010-07-17 16:41 ` Segher Boessenkool
2010-07-19 4:24 ` Matthew McClintock
2010-07-30 1:38 ` David Gibson
2010-07-30 1:23 ` David Gibson
2010-07-19 0:09 ` Benjamin Herrenschmidt
2010-07-19 4:34 ` Matthew McClintock
2010-07-18 23:41 ` Benjamin Herrenschmidt
2010-07-19 4:28 ` Matthew McClintock
2010-07-19 4:32 ` Grant Likely
2010-07-19 16:57 ` Scott Wood
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=1279174642.28344.6.camel@localhost \
--to=msm@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=timur@freescale.com \
/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).