From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gbi2z-00045Y-Ix
	for qemu-devel@nongnu.org; Sun, 22 Oct 2006 14:27:45 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gbi2w-000433-Gz
	for qemu-devel@nongnu.org; Sun, 22 Oct 2006 14:27:45 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gbi2w-00042w-D0
	for qemu-devel@nongnu.org; Sun, 22 Oct 2006 14:27:42 -0400
Received: from [65.74.133.4] (helo=mail.codesourcery.com)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Gbi2w-0008Ez-74
	for qemu-devel@nongnu.org; Sun, 22 Oct 2006 14:27:42 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Config file support
Date: Sun, 22 Oct 2006 19:27:33 +0100
References: <OFC1EB4E10.63CD3677-ON8525720D.00622299-8525720D.00627058@us.ibm.com>
	<453BA3D2.1080006@zipman.it>
	<56d259a00610221019pcc7ba3bv4510d1a7b447b0f9@mail.gmail.com>
In-Reply-To: <56d259a00610221019pcc7ba3bv4510d1a7b447b0f9@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610221927.34528.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> Would that be enough to be able to move the emulated system
> description into config files rather than having the set of hard-coded
> machine alternatives we have at present? If so it would be a boon to
> anyone wanting to emulate, frinstance, any ARM board other than those
> manufactured by ARM Corp.

To a first approximation the machine description probably wants to be separate 
from the user config file. There is some overlap and interlinking, but they 
tend to be aimed at different users. eg. the machine description will specify 
a particular scsi HBA with a MMIO address and wired to a particular IRQ, 
whereas the user just specifies they want a cdrom using a particular image.

I've been considering a machine config file for a while, but haven't come up 
with a coherent way of representing everything yet.

Paul