LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux PPC Mailing List <linuxppc-dev@lists.ozlabs.org>
Subject: for muram in DTS file, why change #address-cells from <1> to <2>?
Date: Tue, 17 May 2016 08:43:46 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1605170839440.3461@localhost.localdomain> (raw)


  currently working on a project involving MPC8360 board, and was
handed a patch to the system .dts file that contained the following
snippet for the muram node:

                muram@10000 {
-                       #address-cells = <1>;
+                       #address-cells = <2>;
                        #size-cells = <1>;
                        compatible = "fsl,qe-muram", "fsl,cpm-muram";
-                       ranges = <0 0x10000 0xc000>;
+                       ranges = <0 0 0x10000 0xc000>;

                        data-only@0 {
                                compatible = "fsl,qe-muram-data","fsl,cpm-muram-data";
-                               reg = <0 0xc000>;
+                               reg = <0 0x4000 0x4000>, <0 0x9400 0x1c00>;
                        };

                };

  i'm not a .dts file expert, but i'm baffled by the change in the
value of #address-cells. how does that make any sense? it seems to me
that that kind of change is a *really* fundamental change in the
specification of the underlying architecture.

  can someone explain what that might mean? thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

                 reply	other threads:[~2016-05-17 12:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.20.1605170839440.3461@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linuxppc-dev@lists.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