From: Jerone Young <jyoung5@us.ibm.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: [dtc] breaking out libfdt from dtc so other progs can use it
Date: Wed, 27 Feb 2008 13:40:43 -0600 [thread overview]
Message-ID: <1204141243.18831.12.camel@thinkpad.austin.ibm.com> (raw)
Currently the dtc source code has libfdt integrated in it. This seems to
have become place for upstream libfdt changes. Now we all know everyone
(linux kernel, cuboot) also have their own versions over libfdt. But if
another userspace app wants to use libfdt , it has to copy it from the
dtc source and try to maintain it's own copy.
The question I have is can libfdt be split out from dtc source, and
become it's own thing. This way other userspace apps can easily download
it and link with it?
The reason I ask is I have added dynamic manipulation support of device
trees in memory into qemu for KVM. But the issue is keeping a copy of
libfdt in the KVM userspace repository, which is getting some opposition
(understandably). But this would be much easier if there was a libfdt
repo for the library so that we wouldn't need to keep our own copy.
next reply other threads:[~2008-02-27 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 19:40 Jerone Young [this message]
2008-02-27 20:31 ` [dtc] breaking out libfdt from dtc so other progs can use it Josh Boyer
2008-02-27 21:24 ` Jerone Young
2008-02-28 1:41 ` David Gibson
2008-02-28 16:30 ` Jerone Young
2008-02-28 18:59 ` Josh Boyer
2008-02-28 20:02 ` Jerone Young
2008-02-29 2:53 ` Jerry Van Baren
2008-02-29 8:35 ` Geert Uytterhoeven
2008-02-29 14:09 ` Josh Boyer
2008-03-01 9:12 ` Fathi Boudra
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=1204141243.18831.12.camel@thinkpad.austin.ibm.com \
--to=jyoung5@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).