From: "Segher Boessenkool" <segher-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Stefan Roese <sr-ynQEQJNshbs@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: dtc: Empty ranges property: #cells-size warning
Date: Wed, 21 Oct 2009 18:41:22 +0200 (CEST) [thread overview]
Message-ID: <54889.84.105.60.153.1256143282.squirrel@gate.crashing.org> (raw)
In-Reply-To: <200910211713.12503.sr-ynQEQJNshbs@public.gmane.org>
> when changing #cells-size from 1 to 2 in the root node (to support >= 4GB
> of
You mean "#size-cells".
> RAM in katmai.dts) I get the following warning:
>
> Warning (ranges_format): /plb has empty "ranges" property but its
> #size-cells
> (1) differs from / (2)
>
> I could change #cells-size to 2 in the plb node as well. But this not
> really
> what I want, because of it's child nodes.
>
> So my questions is: How can I solve this problem? Perhaps this warning
> should
> be removed from dtc?
No, the warning is correct, and your device tree is in error.
An empty "ranges" property means that the child address space is
identical to the parent address space, which isn't the case here.
You should resolve this by using a non-empty "ranges" property,
instead. If e.g. the address space is 1GB, and located at 0, you
would do
< 0 0 0 0x40000000 >
(child) (parent) (size)
Segher
next prev parent reply other threads:[~2009-10-21 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 15:13 dtc: Empty ranges property: #cells-size warning Stefan Roese
[not found] ` <200910211713.12503.sr-ynQEQJNshbs@public.gmane.org>
2009-10-21 16:41 ` Segher Boessenkool [this message]
[not found] ` <54889.84.105.60.153.1256143282.squirrel-JorI+TVEvZrY24RiXHRV3ti2O/JbrIOy@public.gmane.org>
2009-10-21 22:04 ` David Gibson
[not found] ` <20091021220413.GA12560-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2009-10-22 9:56 ` Stefan Roese
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=54889.84.105.60.153.1256143282.squirrel@gate.crashing.org \
--to=segher-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=sr-ynQEQJNshbs@public.gmane.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