From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L14M4-0006aF-0F for qemu-devel@nongnu.org; Fri, 14 Nov 2008 14:29:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L14M2-0006ZP-I6 for qemu-devel@nongnu.org; Fri, 14 Nov 2008 14:29:19 -0500 Received: from [199.232.76.173] (port=46278 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L14M2-0006ZM-D6 for qemu-devel@nongnu.org; Fri, 14 Nov 2008 14:29:18 -0500 Received: from mail-qy0-f33.google.com ([209.85.221.33]:50979) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L14M2-0005aX-2k for qemu-devel@nongnu.org; Fri, 14 Nov 2008 14:29:18 -0500 Received: by qyk14 with SMTP id 14so20150qyk.10 for ; Fri, 14 Nov 2008 11:29:16 -0800 (PST) Message-ID: <491DD188.6000603@codemonkey.ws> Date: Fri, 14 Nov 2008 13:29:12 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Machine config files References: <200811140332.14093.paul@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed 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: qemu-devel@nongnu.org Cc: Hollis Blanchard Blue Swirl wrote: > On 11/14/08, Paul Brook wrote: > >> It's come up in other contexts recently, so I think it's worth mentioning that >> I am currently working on adding a machine config file support to qemu. >> >> I am focusing on the board setup side of things, rather than the user-level >> config side. My goal is to come up with a system that will allow e.g. the >> entirety of realview.c and gumstix.c to be eliminated. Currently this is >> based this round Flattened Device Trees (as used by ppc-linux). >> >> I have looked at the bits that Fabrice did a while ago. While that contains >> some good ideas (which I will probably steal!) it is approaching the problem >> from a somewhat different direction. FTDs are a much better fit for some of >> my requirements (e.g. being able to pass the config through to the guest OS). >> > > libfdt looks like an excellent choice for both Sparc32 and Sparc64, I > think the whole OF tree can be represented with it. > > The config could be passed using the firmware configuration device. > I was looking through libfdt too. I think it could also be used for x86. Hollis, I was looking through the Bamboo code, any reason you don't describe the bus/device layouts in the DTS and then use that to determine what bus/nic to add? Regards, Anthony Liguori