From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Grant Likely" <grant.likely@secretlab.ca>,
"Kumar Gala" <galak@kernel.crashing.org>,
"linux-ppc list" <linuxppc-dev@ozlabs.org>,
"U-Boot Users List" <u-boot-users@lists.sourceforge.net>
Subject: Re: [U-Boot-Users] use of aliases in device trees
Date: Sun, 4 Nov 2007 16:32:49 -0700 [thread overview]
Message-ID: <fa686aa40711041532u21e95467i444e999ae45c2f03@mail.gmail.com> (raw)
In-Reply-To: <20071104224256.GC15444@localhost.localdomain>
On 11/4/07, David Gibson <david@gibson.dropbear.id.au> wrote:
> On Sat, Nov 03, 2007 at 09:29:48PM -0600, Grant Likely wrote:
> > Maybe something like:
> > aliases {
> > enet0,phandle = <&enet0>;
> > enet1,phandle = <&enet1>;
> > ...
> > };
>
> The fairly small advantages of using phandles here are not worth the
> hassle of defining a new alias format, when the OF one with full paths
> already exists.
>
> I would, however, like to extend dtc so that we can do something like:
> aliases {
> enet0 = &enet0;
> };
> and the reference in non-cell context will expand to the full path.
> That could be used for things like linux,stdout-path in /chosen, too.
>
> I'd also like to extend dtc so that the label can be tagged somehow, say:
> *enet0: { ... };
> and as well as creating a normal dtc label, an alias will also be
> automatically added to /aliases.
Yeah, okay! I like both of those ideas. That certainly addresses my
ease of maintenance concerns.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-11-04 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 1:02 use of aliases in device trees Kumar Gala
2007-11-04 3:29 ` [U-Boot-Users] " Grant Likely
2007-11-04 22:42 ` David Gibson
2007-11-04 23:32 ` Grant Likely [this message]
2007-11-04 9:24 ` Segher Boessenkool
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=fa686aa40711041532u21e95467i444e999ae45c2f03@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=u-boot-users@lists.sourceforge.net \
/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).