From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L0pPv-0002a3-8w for qemu-devel@nongnu.org; Thu, 13 Nov 2008 22:32:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L0pPu-0002Zm-4N for qemu-devel@nongnu.org; Thu, 13 Nov 2008 22:32:18 -0500 Received: from [199.232.76.173] (port=52117 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L0pPu-0002Zj-0X for qemu-devel@nongnu.org; Thu, 13 Nov 2008 22:32:18 -0500 Received: from mail.codesourcery.com ([65.74.133.4]:34879) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1L0pPt-00070I-GA for qemu-devel@nongnu.org; Thu, 13 Nov 2008 22:32:17 -0500 From: Paul Brook Date: Fri, 14 Nov 2008 03:32:13 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811140332.14093.paul@codesourcery.com> Subject: [Qemu-devel] Machine config files 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 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). I haven't entirely figured out how this will interact with user config (in particular user-pluggable devices like PCI NICs), but I think I can come up with something fairly sensible. The code isn't even close to being functional at this point, and I can't give definite timescales, but with a bit of luck I'll have something by the end of the year. Paul