From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Uboot Device Tree
Date: Tue, 16 Oct 2007 09:32:58 -0400 [thread overview]
Message-ID: <4714BD8A.6030306@ge.com> (raw)
In-Reply-To: <13233573.post@talk.nabble.com>
reckless wrote:
> Hi,
>
> I am using the u-boot-1.2 on powerpc. I am using separate device tree
> compiled by DTC.
> Is there any way to embed the device tree in uboot i.e auto generate the
> device tree?
> What is libftd? i didnt get any links or details about that? I search the
> CONFIG_OF_LIBFDT macro in the u-boot source and i didn't find it any where?
>
> Do anyone have any idea?
>
> Regards
> Manish Sharma
Hi Manish,
You need to upgrade to the latest u-boot, LIBFDT is a relatively recent
addition. The "tip of the tree" in git (and soon to be released 1.3)
has libfdt support, 1.2 does not. The support is expected to improve
over the next couple of months, but what we have is functional.
See also:
<http://www.denx.de/wiki/UBoot/UBootFdtInfo>
and lots of recent email exchanges on the list...
Best regards,
gvb
prev parent reply other threads:[~2007-10-16 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:26 [U-Boot-Users] Uboot Device Tree reckless
2007-10-16 13:32 ` 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=4714BD8A.6030306@ge.com \
--to=gerald.vanbaren@ge.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