From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQRM9-000623-IF for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:06:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQRM7-00061Q-O5 for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:06:16 -0500 Received: from [199.232.76.173] (port=59212 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQRM7-00061F-JI for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:06:15 -0500 Received: from mx20.gnu.org ([199.232.41.8]:29638) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LQRM4-000299-Vl for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:06:13 -0500 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQRM2-000701-IS for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:06:10 -0500 From: Paul Brook Subject: Re: [Qemu-devel] [RFC PATCH 0/9] Configurable PCI device addresses Date: Fri, 23 Jan 2009 19:06:07 +0000 References: <87ocxzrvqb.fsf@pike.pond.sub.org> <4978D1B0.5040500@codemonkey.ws> In-Reply-To: <4978D1B0.5040500@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901231906.08178.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: qemu-devel@nongnu.org > I think we're starting to get to the tipping point where we really just > need to introduce a machine config file. > > Paul, you mentioned you were working on something before? Care to > update us on the status? > > I know there was a fair bit of support before for a FDT based machine > config. I have a FDT based machine descriptions working locally. Currently it's only capable of generating a small subset ARM embedded boards. There are a few issues that need to be resolved before it can replace most of the current qemu machines: - How to handle "plug-n-play" busses like PCI. The FDT provided to the kernel generally just describes the host bridge, and the kernel/bios figures everything else out using the normal PCI config mechanisms. - How it will interact with commandline options like -nic that modify which hardware is present. One possibility is to remove these options (remove -net nic, but leave -net tap, etc.). If users want different numbers/types of NICs they should use a different machine config. - How to handle GPIO pins, and other interconnects like I2S, SSI and I2C. I guess this is mainly coming up with suitable FDT representations. I have not implemented a user level config file. My work effectively just replaces integratorcp_init and friends. Paul