linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Add aliases node to 8641hpcn DTS file.
Date: Wed, 5 Dec 2007 21:05:36 +0300	[thread overview]
Message-ID: <20071205210536.41158b6b@kernel.crashing.org> (raw)
In-Reply-To: <fa686aa40712050938j2d286655o94534a00131872e2@mail.gmail.com>

On Wed, 5 Dec 2007 10:38:38 -0700
Grant Likely wrote:

> >
> > +       aliases {
> > +               ethernet0 = &enet0;
> > +               ethernet1 = &enet1;
> > +               ethernet2 = &enet2;
> > +               ethernet3 = &enet3;
> > +               serial0 = &serial0;
> > +               serial1 = &serial1;
> > +               pci0 = &pci0;
> > +               pci1 = &pci1;
> > +       };  
> 
> I had thought aliases were supposed to be full paths to nodes instead
> of phandles.  Was I wrong?
no, but dwg did a patch for dtc to do that dirty work for you, resolving labels. I am also curious if such a change made it in
dtc git (working with full path aliases now). dtc should prolly get tagged and next sub-rev to be clear if it supports aliases or not.

-- 
Sincerely, Vitaly

  parent reply	other threads:[~2007-12-05 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 17:32 [PATCH] Add aliases node to 8641hpcn DTS file Jon Loeliger
2007-12-05 17:38 ` Grant Likely
2007-12-05 18:05   ` Jon Loeliger
2007-12-05 18:15     ` Grant Likely
2007-12-05 18:31     ` Josh Boyer
2007-12-05 18:05   ` Vitaly Bordug [this message]
2007-12-05 22:28 ` Mark A. Greer
2007-12-05 22:33   ` David Gibson

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=20071205210536.41158b6b@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).