From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LCgcu-0005fE-D9 for qemu-devel@nongnu.org; Tue, 16 Dec 2008 15:34:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LCgcs-0005e2-Qu for qemu-devel@nongnu.org; Tue, 16 Dec 2008 15:34:44 -0500 Received: from [199.232.76.173] (port=56369 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LCgcs-0005dy-Lf for qemu-devel@nongnu.org; Tue, 16 Dec 2008 15:34:42 -0500 Received: from relay01.mx.bawue.net ([193.7.176.67]:58658) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LCgcs-0005gN-AO for qemu-devel@nongnu.org; Tue, 16 Dec 2008 15:34:42 -0500 Date: Tue, 16 Dec 2008 21:34:37 +0100 From: Thiemo Seufer Subject: Re: [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation Message-ID: <20081216203437.GA16415@networkno.de> References: <1229440187.31337.15.camel@localhost.localdomain> <4947D48D.8010203@codemonkey.ws> <200812161634.08950.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200812161634.08950.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: Aurelien Jarno , qemu-devel@nongnu.org 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