From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>
Subject: Re: [PATCH] [POWERPC] 4xx: Add aliases node to 4xx dts files
Date: Sun, 16 Dec 2007 23:44:50 +0100 [thread overview]
Message-ID: <9618c94dbc228065db8bd99fbf6b7ba6@kernel.crashing.org> (raw)
In-Reply-To: <20071216223342.GD26307@localhost.localdomain>
>> Hopefully some version that stores path strings in the properties
>> in /aliases, and not phandles. Or does that current version of DTC
>> do that correctly already, and just has an inconvenient source
>> syntax?
>
> I don't think anyone's actually gone and generated phandles in
> /aliases, although it was suggested early on. The syntax is
> foo = < &bar >;
> to generate a phandle and
> foo = &bar;
> to generate a path.
Ah, I see.
> I was a bit worried about confusion between these forms, but at least
> Kumar and myself came up with this syntax independently, which
> suggests it's not too surprising to most people, and no-one had any
> other suggestions.
I think I suggested it before, but anyway:
how about you write
aliases {
foo = "/the/path/to/foo";
};
and then you can use &foo in the rest of the DTS to refer to the
phandle (or path string, as it turns out :-) ) of the node? I.e.,
use the aliases node to _generate_ aliases.
Seems simpler than the current thing to me.
Segher
next prev parent reply other threads:[~2007-12-16 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 7:55 [PATCH] [POWERPC] 4xx: Add aliases node to 4xx dts files Stefan Roese
2007-12-16 6:19 ` David Gibson
2007-12-16 14:58 ` Josh Boyer
2007-12-16 18:10 ` Segher Boessenkool
2007-12-16 18:45 ` Josh Boyer
2007-12-16 22:33 ` David Gibson
2007-12-16 22:44 ` Segher Boessenkool [this message]
2007-12-17 0:00 ` David Gibson
2007-12-17 13:46 ` Jon Loeliger
2007-12-16 22:30 ` 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=9618c94dbc228065db8bd99fbf6b7ba6@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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).