From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQRiN-00085N-Qx for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:29:15 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQRiM-00085B-EB for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:29:15 -0500 Received: from [199.232.76.173] (port=45013 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQRiM-000858-Af for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:29:14 -0500 Received: from mail-qy0-f20.google.com ([209.85.221.20]:49649) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQRiL-0005Cq-Vy for qemu-devel@nongnu.org; Fri, 23 Jan 2009 14:29:14 -0500 Received: by qyk13 with SMTP id 13so7699106qyk.10 for ; Fri, 23 Jan 2009 11:29:13 -0800 (PST) Message-ID: <497A1A7B.8030300@codemonkey.ws> Date: Fri, 23 Jan 2009 13:28:59 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC PATCH 0/9] Configurable PCI device addresses References: <87ocxzrvqb.fsf@pike.pond.sub.org> <4978D1B0.5040500@codemonkey.ws> <200901231906.08178.paul@codesourcery.com> In-Reply-To: <200901231906.08178.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; 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: Paul Brook Cc: qemu-devel@nongnu.org Paul Brook wrote: >> 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. > Can you post what you have? > 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. > A user level config file can come later. Regards, Anthony Liguori > Paul >