From: Thiemo Seufer <ths@networkno.de>
To: Paul Brook <paul@codesourcery.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation
Date: Tue, 16 Dec 2008 21:34:37 +0100 [thread overview]
Message-ID: <20081216203437.GA16415@networkno.de> (raw)
In-Reply-To: <200812161634.08950.paul@codesourcery.com>
Paul Brook wrote:
> On Tuesday 16 December 2008, Anthony Liguori wrote:
> > Hollis Blanchard wrote:
> > > If you'd prefer to make libfdt mandatory, I'm fine with that.
> >
> > No, it shouldn't be mandatory :-)
> >
> > >>> This patch introduces a dependency on libfdt for flat device tree
> > >>> support.
> > >>
> > >> I don't like the way this is done.
> > >>
> > >> AFAIK libfdt isn't present in any of the major distros. I thought the
> > >> conclusion was that we should import libfdt into qemu.
> > >
> > > That was our conclusion, but Anthony never agreed.
> >
> > Because it's better to let the distros maintain this. That way, they
> > can deal with security issues, etc.
>
> That's fine in theory. In practice it means we can't realistically use libfdt
> for anything important for at least another 12 months or so. I'm also rather
> sceptical about the stability of the libfdt API.
An approach commonly taken is to try to link against a system-provided
(dynamic) library, and fall back to the in-tree version if this fails.
(This assumes a system will only provide libfdt once its API/ABI is
stable enough.)
Thiemo
next prev parent reply other threads:[~2008-12-16 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 10:43 [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation Aurelien Jarno
2008-12-16 12:30 ` Paul Brook
2008-12-16 15:09 ` Hollis Blanchard
2008-12-16 16:17 ` Anthony Liguori
2008-12-16 16:34 ` Paul Brook
2008-12-16 17:03 ` Blue Swirl
2008-12-16 20:34 ` Thiemo Seufer [this message]
2008-12-16 16:31 ` Paul Brook
2008-12-16 16:46 ` Daniel P. Berrange
2008-12-16 17:15 ` Hollis Blanchard
2008-12-16 18:15 ` Josh Boyer
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=20081216203437.GA16415@networkno.de \
--to=ths@networkno.de \
--cc=aurelien@aurel32.net \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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).