From: Segher Boessenkool <segher@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/3] Bamboo DTS
Date: Mon, 14 May 2007 17:52:15 +0200 [thread overview]
Message-ID: <345f23c36f44912708e8c42d3f432013@kernel.crashing.org> (raw)
In-Reply-To: <92b3319be989145b0191cf9693ddd90c@kernel.crashing.org>
>> + ranges = <00000000 0 00000000 80000000
>> + 80000000 0 80000000 80000000>;
>
> You can avoid having two ranges by using #size-cells = 2
> in the root node.
Erm ignore this, size in a "ranges" property is encode
with the "#size-cells" of the child bus, not the parent
bus. #size-cells = 2 does fix similar problems, just
not this one :-)
> Having two ranges is a problem if any
> mapping straddles the boundary between the two.
You can get around this problem by making one range's
top or bottom boundary identical to that same boundary
of a bus range or reg range of a direct child of this
bus. Since you don't have any kids for this node yet
it doesn't matter for now, but keep it in mind.
Segher
next prev parent reply other threads:[~2007-05-14 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 14:56 [PATCH 0/3] Initial AMCC Bamboo support Josh Boyer
2007-05-14 14:57 ` [PATCH 1/3] Bamboo DTS Josh Boyer
2007-05-14 15:21 ` Segher Boessenkool
2007-05-14 15:52 ` Segher Boessenkool [this message]
2007-05-14 18:44 ` Josh Boyer
2007-05-14 14:59 ` [PATCH 2/3] Bamboo platform support Josh Boyer
2007-05-15 0:58 ` Stephen Rothwell
2007-05-15 1:03 ` Josh Boyer
2007-05-15 2:03 ` Stephen Rothwell
2007-05-15 2:42 ` Josh Boyer
2007-05-14 14:59 ` [PATCH 3/3] Bamboo wrapper Josh Boyer
2007-05-15 1:28 ` David Gibson
2007-05-15 1:29 ` Josh Boyer
2007-05-15 1:26 ` [PATCH 0/3] Initial AMCC Bamboo support David Gibson
2007-05-15 1:38 ` Josh Boyer
2007-05-15 1:44 ` David Gibson
2007-05-15 7:33 ` Benjamin Herrenschmidt
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=345f23c36f44912708e8c42d3f432013@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-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).