From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [FIX] FDT bug - MPC83xx
Date: Tue, 10 Jul 2007 09:26:13 -0400 [thread overview]
Message-ID: <469388F5.7080208@smiths-aerospace.com> (raw)
In-Reply-To: <2927.5445-20943-1028852284-1184069606@seznam.cz>
Michal Simek wrote:
> Hi,
> thanks for explanation.
> Do you have any documentation about FDT? I would like to test it.
> I have proprietary board with MPC8343 like a testing platform and if
> is useful for Microblaze, I will try to port it.
>
> Best regards,
> Michal
Documentation? We don't need no steeenkin' documentation!
I'm NOT a fdt expert. I simply stood on the experts' shoulders. To be
specific, I took David Gibson's libfdt interface library and created a
"fdt" command on top of that. As part of that, I adapted some board,
etc, munging that was done as part of the "bootm" command to use David's
libfdt as well, instead of the older set of utilities (the older utility
routines have a kinda funky interface).
If you look at the custodians' page
<http://www.denx.de/wiki/UBoot/Custodians>
you will see a pointer to my Work In Progress page
<http://www.denx.de/wiki/UBoot/UBootFdtInfo>
I've just added a background section that is a lot of jump-off links for
more information.
<http://www.denx.de/wiki/view/UBoot/UBootFdtInfo#Background_Information_on_Flatte>
Note that it's a wiki -- please add improvements!
gvb
prev parent reply other threads:[~2007-07-10 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 11:42 [U-Boot-Users] [FIX] FDT bug - MPC83xx Michal Simek
2007-07-09 20:47 ` Kim Phillips
2007-07-09 21:06 ` Jerry Van Baren
2007-07-10 11:52 ` Michal Simek
2007-07-10 11:59 ` Jerry Van Baren
2007-07-10 12:13 ` Michal Simek
2007-07-10 13:26 ` 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=469388F5.7080208@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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