From: Jerry Van Baren <gerald.vanbaren@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFA & Update: Using libfdt in u-boot for fdt command
Date: Thu, 01 Mar 2007 20:17:15 -0500 [thread overview]
Message-ID: <45E77B1B.5060509@comcast.net> (raw)
In-Reply-To: <20070301234951.GC8177@mag.az.mvista.com>
Mark A. Greer wrote:
> On Thu, Mar 01, 2007 at 09:01:24AM -0500, Jerry Van Baren wrote:
>> Hi all,
>>
>> This is a Request for Advice.
>
> Hi Jerry.
>
> One minor thing. I'd just want to remind you that we shouldn't stray
> too far from the OF interface. The bootwrapper code sits on top of
> either the FDT access interface or the true OF DT access interface.
> The closer we keep the two, the cleaner & easier the we can keep
> the bootwrapper code.
>
> Mark
Hi Mark,
Understood, but that isn't really my battle. David Gibson created the
libfdt interface so any linux/bootwrapper changes are really his battle.
I'm working in u-boot land so linux/bootwrapper aren't in my problem
domain - using libfdt in u-boot doesn't affect the bootwrapper code.
Having said that, I'm hoping for shared code synergy, which would
require the linux kernel to adopt libfdt as a replacement for
flatdevtree.[ch]. David has also talked about using libfdt in the dtc
suite, so there is potentially a three way synergy.
The flattened device tree which is passed from u-boot to linux is
unchanged*, so the interface is the same at that level (to state the
obvious).
David's libfdt is a potential replacement for flatdevtree.c. I have
pursued using libfdt rather than flatdevtree (in u-boot) because the
interface is much cleaner (IMHO, and, I'm sure, IDHO). Of course "much
cleaner" is the fancy way of saying "not compatible." :-/ On the other
hand, I looked at arch/powerpc/boot/of.c, ops.h, and flatdevtree_misc.c.
It looks like it would be relatively easy to redo flatdevtree_misc.c
to glue to libfdt instead of flatdevtree.c (he says blithely).
* ...other than a backwards compatible version 16 -> 17 upgrade.
Best regards,
gvb
next prev parent reply other threads:[~2007-03-02 1:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 14:01 [U-Boot-Users] RFA & Update: Using libfdt in u-boot for fdt command Jerry Van Baren
2007-03-01 23:49 ` Mark A. Greer
2007-03-02 1:17 ` Jerry Van Baren [this message]
2007-03-02 20:53 ` Mark A. Greer
2007-03-02 1:55 ` David Gibson
2007-03-02 4:08 ` Jerry Van Baren
2007-03-02 4:48 ` David Gibson
2007-03-02 5:25 ` Jerry Van Baren
2007-03-02 5:36 ` David Gibson
2007-03-02 12:31 ` Jerry Van Baren
2007-03-02 18:35 ` Jerry Van Baren
2007-03-02 22:31 ` David Gibson
2007-03-02 18:38 ` Jerry Van Baren
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=45E77B1B.5060509@comcast.net \
--to=gerald.vanbaren@comcast.net \
--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