linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Directly reference i8259@4d0 nodes in mpc8641_hpcn.dts.
Date: Fri, 18 Aug 2006 11:59:48 +1000	[thread overview]
Message-ID: <1155866388.5803.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20060818004301.GA8734@mag.az.mvista.com>

On Thu, 2006-08-17 at 17:43 -0700, Mark A. Greer wrote:
> On Fri, Aug 18, 2006 at 10:09:21AM +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2006-08-17 at 16:20 -0500, Jon Loeliger wrote:
> > > 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.
> > 
> > Not 100% sure here but can't we use a label and do &label rather than
> > having to copy the full path every time ? Would make things easier :) If
> > not, that's probably something to add to dtc...
> 
> Isn't linux,phandle basically the label that you speak of, though?
> IOW, you may be saying, "No, keep using the linux,phandle".

No, more something like

pic:
  <pic_node>

and later

&pic

> Just trying to clarify things although I'm not sure that I really am...  :)
> 
> Mark

  reply	other threads:[~2006-08-18  2:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 17:24 Patch] Fix the mpc8641_hpcn.dts file Jon Loeliger
2006-08-17 18:51 ` Hollis Blanchard
2006-08-17 21:20   ` [PATCH] Directly reference i8259@4d0 nodes in mpc8641_hpcn.dts Jon Loeliger
2006-08-18  0:09     ` Benjamin Herrenschmidt
2006-08-18  0:43       ` Mark A. Greer
2006-08-18  1:59         ` Benjamin Herrenschmidt [this message]
2006-08-18  5:54           ` Zhang Wei-r63237
2006-08-18  7:21             ` Benjamin Herrenschmidt
2006-08-18 17:32     ` Jon Loeliger

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=1155866388.5803.10.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.com \
    /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).