From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Using CONFIG_OF_LIBFDT
Date: Wed, 04 Apr 2007 19:52:47 -0400 [thread overview]
Message-ID: <46143A4F.1060600@gmail.com> (raw)
I've added the following Important Safety Tips to the u-boot-fdt status page
<http://www.denx.de/wiki/UBoot/UBootFdtInfo>
based on feedback from Jon Diekema (thanks, Jon):
* Need to use the latest device tree compiler (dtc) to generate a
Version 17 blob
* libfdt needs V17 in order to write to the blob
* Need to specify a size with fdt addr
* By default, the blob has the minimum necessary size for its
compiled content. This means there is no room to add a "chosen" (or
other) node.
* Using CONFIG_OF_LIBFDT modifies bootm so that it does not
auto-generate nodes ("chosen", "u-boot-env", and "bd_t") when it runs.
With CONFIG_OF_LIBFDT, the boot script or the user must use the sequence:
* fdt addr command to set the blob address
* fdt chosen to generate/augment the chosen node
* fdt env to generate the u-boot-env node (optional)
* fdt bd_t to generate the bd_t node (optional)
Bear with me, we'll get this smoothed out...
gvb
reply other threads:[~2007-04-04 23:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46143A4F.1060600@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.