From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace•com>
To: linuxppc-dev@ozlabs•org
Subject: Re: libfdt - flat tree manipulation library
Date: Fri, 01 Dec 2006 08:11:35 -0500 [thread overview]
Message-ID: <45702A07.2030303@smiths-aerospace.com> (raw)
In-Reply-To: <20061201060038.GA25476@localhost.localdomain>
David Gibson wrote:
> On Wed, Nov 29, 2006 at 04:59:04PM +1100, David Gibson wrote:
>> On Mon, Nov 27, 2006 at 04:59:05PM +1100, David Gibson wrote:
>> [snip]
>>> The code, such as it is, is at:
>>> git://ozlabs.org/home/dgibson/git/libfdt.git
>> Code for writing device trees from scratch, sequentially, is now
>> implemented.
>
> And now support for random access read-write is implemented. The
> library is now close to feature-complete, cleanups and convenience
> wrappers remain.
Hi David,
You have not gotten any feedback on your library efforts. I just
thought I would let you know I am interested in your code for possibly
using it in u-boot. I have not had time to review it carefully and
compare it to (a) existing u-boot fdt code and (b) current linux fdt
support but intend to do that soon.
The existing u-boot fdt code is pretty crude (IMHO - makes (a) above a
nobrainer) and could bear replacing with something that has more
widespread support and is more flexible. Easier to use would be a big
bonus. :-)
Size looks pretty comparable.
$ wc -l libfdt/*.c
124 fdt.c
237 fdt_ro.c
310 fdt_rw.c
226 fdt_sw.c
115 fdt_wip.c
1012 total
$ wc -l arch/powerpc/boot/flatdevtree*.c
880 flatdevtree.c
51 flatdevtree_misc.c
931 total
For u-boot purposes, I would like to create a command that can dump a
fdt starting at a give node (a string, e.g. "/" for the whole thing,
"/cpus" for the entire CPU node and subnodes, or "/cpus/#cpus" to get
just one property). I don't see a way of doing that directly with your
current interface. Am I missing something or would I have to add
something? The kernel doesn't need to support interactive fdt
manipulation, but that would be very beneficial for a bootrom like
u-boot. (FWIIW, I've done a "prototype" ;-) version of this command
with the existing u-boot code.)
If the linux kernel were to adopt your library, how do you envision this
happening? Replace the existing code with wrappers (your "convenience
wrappers"?) to provide a backwards compatible interface (looks nasty and
negates your simplification advantages) or rip out 'n replace?
Thanks for your efforts,
gvb
next prev parent reply other threads:[~2006-12-01 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 5:59 libfdt - flat tree manipulation library David Gibson
2006-11-29 5:59 ` David Gibson
2006-12-01 6:00 ` David Gibson
2006-12-01 13:11 ` Jerry Van Baren [this message]
2006-12-03 23:55 ` David Gibson
2006-12-02 8:41 ` Grant Likely
2006-12-04 0:03 ` David Gibson
2006-12-07 20:35 ` Hollis Blanchard
2006-12-07 22:23 ` David Gibson
2007-01-02 23:29 ` Mark A. Greer
2007-01-03 1:32 ` David Gibson
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=45702A07.2030303@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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