From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How to define CONFIG_OF_FLAT_TREE?
Date: Wed, 09 Jan 2008 15:37:02 -0500 [thread overview]
Message-ID: <4785306E.40902@ge.com> (raw)
In-Reply-To: <679169.84689.qm@web15107.mail.cnb.yahoo.com>
jie han wrote:
> What's different between CONFIG_OF_LIBFDT and CONFIG_OF_FLAT_TREE?
CONFIG_OF_FLAT_TREE was the original FDT interface code and had a
...uh... funky interface. David Gibson wrote a FDT library intended for
embedded use and CONFIG_OF_LIBFDT uses that. We've been switching
processors/boards over. I believe the switchover is mostly complete.
> My board is mpc8641d and u-boot version is 1.3.1.
No direct experience, but I believe that is good. Is this a custom
board or an eval board? If it is a custom board, you will need to
generate an appropriate *.dts file by customizing an example.
> I f I define CONFIG_OF_FLAT_TREE,and u-boot command bootm will call
> ft_setup() function, and how is it work?
With CONFIG_OF_LIBFDT, bootm calls the appropriate board and processor
setup routines fdt_chosen() and ft_board_setup().
Note that CONFIG_OF_LIBFDT adds the "fdt" command which is very helpful
for printing out out (and modifying) blob data.
> I found DTS files under kernel /arch/powerpc/sysDev directory,Could
> you give me some advice how to build it?
You need to build the device tree compiler (dtc). You can get the
source from Jon Loeliger's repository:
<http://jdl.com/git_repos/>
> Thanks,
> Jie
[snip]
gvb
next prev parent reply other threads:[~2008-01-09 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 19:29 [U-Boot-Users] How to define CONFIG_OF_FLAT_TREE? jie han
2008-01-09 19:55 ` Jerry Van Baren
2008-01-09 20:14 ` jie han
2008-01-09 20:37 ` Jerry Van Baren [this message]
2008-01-10 13:01 ` samppa at sundmangroup.com
2008-01-10 20:52 ` Jon Loeliger
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=4785306E.40902@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 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.