From: Scott Wood <scottwood@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Yoder Stuart-B08248 <stuart.yoder@freescale.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [RFC][PATCH 6/8] Walnut DTS
Date: Wed, 18 Jul 2007 11:47:46 -0500 [thread overview]
Message-ID: <469E4432.5050900@freescale.com> (raw)
In-Reply-To: <A86AB8AE-E421-457B-ABE8-9AD93CCFCDC8@kernel.crashing.org>
Segher Boessenkool wrote:
> Yes indeed. The problem with your suggested "obvious way"
I said it was obvious, not obviously correct. :-)
> is that you wouldn't get a unit address included if your
> interrupt-map points (for some entry) at your device tree
> parent, either. Not all that hypothetical.
Ah, good point. My inclination would be to, rather than check how we
got to the node, check whether it's the device's parent. If not, then
the presence of #address-cells (other than zero for compatibility) is an
error. Otherwise, #address-cells is used, and defaults are handled the
same as with reg/ranges translation.
-Scott
next prev parent reply other threads:[~2007-07-18 16:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 13:52 [RFC][PATCH 0/8] arch/powerpc support for Walnut Board Josh Boyer
2007-07-11 13:53 ` [RFC][PATCH 1/8] 4xx Kconfig cleanup Josh Boyer
2007-07-11 13:55 ` [RFC][PATCH 2/8] 4xx boot wrapper reworks Josh Boyer
2007-07-11 13:56 ` [RFC][PATCH 3/8] 4xx MMU Josh Boyer
2007-07-11 20:56 ` Arnd Bergmann
2007-07-11 21:15 ` Josh Boyer
2007-07-12 7:09 ` Kumar Gala
2007-07-12 12:40 ` Josh Boyer
2007-07-11 13:57 ` [RFC][PATCH 4/8] 4xx decrementer fixes Josh Boyer
2007-07-11 13:58 ` [RFC][PATCH 5/8] Fix 4xx build Josh Boyer
2007-07-11 21:00 ` Arnd Bergmann
2007-07-11 13:59 ` [RFC][PATCH 6/8] Walnut DTS Josh Boyer
2007-07-11 14:26 ` Stefan Roese
2007-07-11 14:37 ` Josh Boyer
2007-07-11 17:49 ` Segher Boessenkool
2007-07-11 17:55 ` Josh Boyer
2007-07-11 18:07 ` Segher Boessenkool
2007-07-18 1:02 ` David Gibson
2007-07-12 15:13 ` Yoder Stuart-B08248
2007-07-16 14:34 ` Segher Boessenkool
2007-07-16 21:47 ` Benjamin Herrenschmidt
2007-07-16 21:55 ` Scott Wood
2007-07-16 22:11 ` Benjamin Herrenschmidt
2007-07-16 22:18 ` Scott Wood
2007-07-16 22:34 ` Benjamin Herrenschmidt
2007-07-16 21:55 ` Yoder Stuart-B08248
2007-07-16 22:12 ` Benjamin Herrenschmidt
2007-07-17 2:39 ` Josh Boyer
2007-07-17 14:26 ` Segher Boessenkool
2007-07-17 14:15 ` Segher Boessenkool
2007-07-17 21:25 ` Benjamin Herrenschmidt
2007-07-17 22:25 ` Scott Wood
2007-07-17 22:58 ` Benjamin Herrenschmidt
2007-07-18 13:53 ` Segher Boessenkool
2007-07-18 16:47 ` Scott Wood [this message]
2007-07-19 16:54 ` Segher Boessenkool
2007-07-18 13:48 ` Segher Boessenkool
2007-07-11 14:02 ` [RFC][PATCH 7/8] Walnut defconfig Josh Boyer
2007-07-11 14:03 ` [RFC][PATCH 8/8] Walnut board support Josh Boyer
2007-07-11 14:04 ` [RFC][PATCH 9/8] Walnut zImage wrapper Josh Boyer
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=469E4432.5050900@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.org \
--cc=stuart.yoder@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).