From: David Gibson <david@gibson•dropbear.id.au>
To: Andy Fleming <afleming@freescale•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: Subject: [PATCH] Add support for the 8568 MDS board
Date: Sat, 10 Feb 2007 13:56:01 +1100 [thread overview]
Message-ID: <20070210025601.GA21415@localhost.localdomain> (raw)
In-Reply-To: <F7DA9D5D-B489-48DA-A9A3-77B8A37395FF@freescale.com>
On Fri, Feb 09, 2007 at 08:07:47PM -0600, Andy Fleming wrote:
>
> On Feb 9, 2007, at 18:47, David Gibson wrote:
>
> > On Fri, Feb 09, 2007 at 05:28:31PM -0600, Andy Fleming wrote:
> > [snip]
> >> +/ {
> >> + model = "MPC8568EMDS";
> >> + compatible = "MPC85xxMDS";
> >> + #address-cells = <1>;
> >> + #size-cells = <1>;
> >> + linux,phandle = <100>;
> >> +
> >> + cpus {
> >> + #cpus = <1>;
> >> + #address-cells = <1>;
> >> + #size-cells = <0>;
> >> + linux,phandle = <200>;
> >
> > So, every Freescale device tree source I've seen so far has had these
> > hardcoded phandles all through it. dtc has supported
> > reference-to-path to automatically generate the necessary phandles for
> > ages now. Please can we use it...
>
> Ok, I'll take a look. Any pointers on syntax?
interrupt-parent = <&/path/to/interrupt-controller>;
That will give a phandle to the target node, if it doesn't have one
already, and insert that phandle value as a cell into the property.
In very recent versions of dtc (as of about yesterday..) you can also
reference a node's label instead of it's path.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-02-10 2:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 23:28 Subject: [PATCH] Add support for the 8568 MDS board Andy Fleming
2007-02-10 0:47 ` David Gibson
2007-02-10 2:07 ` Andy Fleming
2007-02-10 2:56 ` David Gibson [this message]
2007-02-13 18:39 ` Kumar Gala
2007-02-13 18:48 ` Andy Fleming
2007-02-13 18:58 ` Kumar Gala
2007-02-13 22:08 ` Jon Loeliger
2007-02-13 22:13 ` Kumar Gala
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=20070210025601.GA21415@localhost.localdomain \
--to=david@gibson$(echo .)dropbear.id.au \
--cc=afleming@freescale$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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