RE: [PATCH] Directly reference i8259@4d0 nodes in mpc8641_hpcn.dts.

Is it a good idea? Why we can not endure the "linux,phandle =3D <4d0>" =
in
i8259 node? And besides, this node was already referenced by the other
entries.

Using "&/soc8641@f8000000/pci@8000/i8259@4d0" or label seems so verbose
and weird.

-----Original Message-----
From: linuxppc-dev-bounces+wei.zhang=3Dfreescale.com@ozlabs.org=20
[mailto:linuxppc-dev-bounces+wei.zhang=3Dfreescale.com@ozlabs.or
g] On Behalf Of Benjamin Herrenschmidt
Sent: Friday, August 18, 2006 10:00 AM
To: Mark A. Greer
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Directly reference i8259@4d0 nodes in=20
mpc8641_hpcn.dts.
=20
On Thu, 2006-08-17 at 17:43 -0700, Mark A. Greer wrote:

quoted

On Fri, Aug 18, 2006 at 10:09:21AM +1000, Benjamin=20

Herrenschmidt wrote:

quoted

quoted

On Thu, 2006-08-17 at 16:20 -0500, Jon Loeliger wrote:

quoted

Rather than using some hand-coded linux,phandle
node references, use DTC's direct node refs ability
and let it manage the phandle names instead.

=20
Not 100% sure here but can't we use a label and do &label=20

rather than

quoted

quoted

having to copy the full path every time ? Would make=20

things easier :) If

quoted

quoted

not, that's probably something to add to dtc...

=20
Isn't linux,phandle basically the label that you speak of, though?
IOW, you may be saying, "No, keep using the linux,phandle".

=20
No, more something like
=20
pic:
  <pic_node>
=20
and later
=20
&pic
=20

quoted

Just trying to clarify things although I'm not sure that I=20

really am...  :)

quoted

=20
Mark

=20
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
=20