From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LCbYX-0005N9-S2 for qemu-devel@nongnu.org; Tue, 16 Dec 2008 10:09:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LCbYW-0005MQ-9g for qemu-devel@nongnu.org; Tue, 16 Dec 2008 10:09:53 -0500 Received: from [199.232.76.173] (port=58895 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LCbYW-0005MJ-4I for qemu-devel@nongnu.org; Tue, 16 Dec 2008 10:09:52 -0500 Received: from e5.ny.us.ibm.com ([32.97.182.145]:43832) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LCbYV-0000J4-Md for qemu-devel@nongnu.org; Tue, 16 Dec 2008 10:09:51 -0500 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e5.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id mBGF90OV022968 for ; Tue, 16 Dec 2008 10:09:00 -0500 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mBGF9nG9189402 for ; Tue, 16 Dec 2008 10:09:49 -0500 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id mBGF9mWi014965 for ; Tue, 16 Dec 2008 10:09:48 -0500 Subject: Re: [Qemu-devel] [6064] Implement device tree support needed for Bamboo emulation From: Hollis Blanchard In-Reply-To: <200812161230.24052.paul@codesourcery.com> References: <200812161230.24052.paul@codesourcery.com> Content-Type: text/plain Date: Tue, 16 Dec 2008 15:09:47 +0000 Message-Id: <1229440187.31337.15.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: qemu-devel@nongnu.org, Aurelien Jarno On Tue, 2008-12-16 at 12:30 +0000, Paul Brook wrote: > > To implement the -kernel, -initrd, and -append options, 4xx board emulation > > must load the guest kernel as if firmware had loaded it. Where u-boot would > > be the firmware, we must load the flat device tree into memory and set key > > fields such as /chosen/bootargs. > > Then why is it optional? As you mention below, libfdt isn't generally available yet, and since it's possible to make a real firmware work in this environment (in which case -kernel isn't needed), the code can still be useful. If you'd prefer to make libfdt mandatory, I'm fine with that. > > 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. FWIW, I have requested that Fedora and Debian package libfdt, and they agreed in principle, but it's still missing in Fedora 10 for example. Is the existence of distribution packages a requirement for use, or should we say "install it by hand into /usr/local"? If it is a requirement, which versions of which distributions? > Certainly adding libfdt_env.h, which is never used, seems very wrong. I'm > pretty sure this won't build on win32 either. Oops, that was a holdover from when we *were* importing libfdt source. I can remove that, or if we want to import a copy of libfdt, I can leave it. I doubt anyone has tried to build libfdt on Windows... -- Hollis Blanchard IBM Linux Technology Center