From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>,
U-Boot Users List <u-boot-users@lists.sourceforge.net>
Subject: Re: [U-Boot-Users] use of aliases in device trees
Date: Sat, 3 Nov 2007 21:29:48 -0600 [thread overview]
Message-ID: <fa686aa40711032029x3871b76m5b44a6e93d8d7217@mail.gmail.com> (raw)
In-Reply-To: <DD2A9B2C-5D35-4F53-8542-3470C6FA5265@kernel.crashing.org>
On 11/3/07, Kumar Gala <galak@kernel.crashing.org> wrote:
> In some discussion on the u-boot dev list it became clear that having
> aliases in the device tree might be useful as a common way to deal
> with finding specific nodes that need fixing up by the firmware.
> This problem also exists in the kernel bootwrappers.
>
> The common example is how to associate a given MAC address with the
> proper ethernet node. In u-boot an explicit path is hard coded into
> the u-boot build for each ethernet device. In the bootwrapper we use
> "linux,network-index = <N>" in the given ethernet node.
>
> One common solution would be having a top level aliases like the pmac
> tree's have:
>
> aliases {
> enet0 = "...";
> enet1 = "...";
> pci0 = "...";
> pci1 = "...";
> };
One question to ask is do we use full paths or phandles to point at nodes?
OF, of course, uses full paths, but that does require more memory and
processing power, but it might not be significant enough to worry
about.
If we use phandles, then we should use names that don't conflict with
full path alias names. It would also be desirable to be able to
generate a phandle alias from the full path alias in order to maintain
some level of compatibility with OF. It also think it will make
maintaining aliases in .dts files simpler because trivial changes to
node paths won't break the phandle alias.
Maybe something like:
aliases {
enet0,phandle = <&enet0>;
enet1,phandle = <&enet1>;
...
};
Cheers,
g.
>
> I wanted to see what people think of this idea and about trying to
> use common names for the aliases? If nothing else I believe we will
> look at doing this on the FSL boards/parts.
>
> - k
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
--
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 3:29 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 ` Grant Likely [this message]
2007-11-04 22:42 ` [U-Boot-Users] " David Gibson
2007-11-04 23:32 ` Grant Likely
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=fa686aa40711032029x3871b76m5b44a6e93d8d7217@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=david@gibson.dropbear.id.au \
--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).