From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fdt: Add simple alias support to fdt print command
Date: Sun, 03 Aug 2008 21:24:40 -0400 [thread overview]
Message-ID: <48965A58.30807@gmail.com> (raw)
In-Reply-To: <20080804011038.GD775@yookeroo.seuss>
David Gibson wrote:
> On Sat, Aug 02, 2008 at 08:51:54PM -0400, Jerry Van Baren wrote:
[snip]
>> I've CC:ed David Gibson in case he has some advice - the concept is to
>> indicate a dereference of /aliases nodes so that us lazy engineers don't
>> have to cut'n'paste the whole long path from the alias. Kumar
>> originally proposed to do it automagically and I countered proposing
>> using "*" to indicate the next path name should be looked up in /aliases
>> and the result used instead (i.e. dereferenced). Discussion thread:
>> <http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/43575/focus=44941>
>
> No, I really don't think using this "dereference" character is a good
> idea. If you're going to expand aliases, you should do it as real OF
> does - see section 4.3 of IEEE1275. Essentially it's the *lack* of a
> leading '/' character that triggers alias expansion. So you could use
> e.g.
> /soc8360 at e0000000/ethernet at e0000400
> or
> soc/ethernet at e0000400
> or
> ethernet0
Ahh, I didn't read far enough. The algorithm in section 4.3 is much
better thought out than either of our proposals.
[snip]
> If you're interepreting them in one place, you should probably
> interpret them everywhwere and have a single "resolve pathname"
> function.
Yes.
> In fact, I should quite possibly put such a function into libfdt.
That would be very useful. :-)
Thanks,
gvb
prev parent reply other threads:[~2008-08-04 1:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 14:40 [U-Boot-Users] [PATCH] fdt: Add simple alias support to fdt print command Kumar Gala
2008-07-09 15:17 ` Jerry Van Baren
2008-07-09 16:51 ` Kumar Gala
2008-07-09 17:02 ` Jerry Van Baren
2008-08-01 14:08 ` Kumar Gala
2008-08-03 0:51 ` Jerry Van Baren
2008-08-04 1:10 ` David Gibson
2008-08-04 1:24 ` Jerry Van Baren [this message]
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=48965A58.30807@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.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