From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] alias in powerpc device tree
Date: Wed, 10 Sep 2008 20:03:54 -0400 [thread overview]
Message-ID: <48C8606A.9080508@gmail.com> (raw)
In-Reply-To: <20080910212546.1D61D8A005B@mail212-wa4.bigfish.com>
Hi John,
John Linn wrote:
> It appears that u-boot expects an alias list in the device tree. I only
> found this in the code for the fdt processing.
Yes. The /aliases node gives tremendous advantages.
> I'm working on getting our device tree correct to be able to allow
> u-boot to alter the device tree.
Good. The "common/fdt_support.c" file should have all the utilities you
need already written, assuming you have a proper /aliases node.
> Is this all that's needed as my device tree is good as far as the kernel
> booting with it and u-boot passes it fine to the kernel such that it
> boots?
>
> Or somewhere there's some documentation that I didn't read and should
> have?
Are you telling us to WTFM? ;-)
Adding the /aliases node and properties should be sufficient. This is
not documented in any obvious way in u-boot (sorry). I don't see any
documentation in Documentation/powerpc/booting-without-of.txt either.
It probably should be added. It probably should be considered to be one
of the "Required nodes and properties".
The /aliases node is a standard Open Firmware-ism, but it isn't real
obvious to non OF gurus (and I'm not a OF guru).
> Thanks,
> John
Best regards,
gvb
next prev parent reply other threads:[~2008-09-11 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 14:18 [U-Boot] [PATCH] Update mailing list email and archive addresses Peter Tyser
2008-09-10 21:25 ` [U-Boot] alias in powerpc device tree John Linn
2008-09-11 0:03 ` Jerry Van Baren [this message]
2008-09-13 0:12 ` [U-Boot] [PATCH] Update mailing list email and archive addresses Wolfgang Denk
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=48C8606A.9080508@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