From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K97ak-00063K-RW
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 20:01:30 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K97aj-00061e-99
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 20:01:30 -0400
Received: from [199.232.76.173] (port=50781 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K97aj-00061b-3h
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 20:01:29 -0400
Received: from mail.codesourcery.com ([65.74.133.4]:55728)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1K97ai-0007W5-FO
	for qemu-devel@nongnu.org; Wed, 18 Jun 2008 20:01:28 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] QEMU configuration files
Date: Thu, 19 Jun 2008 01:01:24 +0100
References: <48595024.7050400@bellard.org>
	<200806190049.37955.paul@codesourcery.com>
In-Reply-To: <200806190049.37955.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200806190101.25295.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

[I apparently missed out a paragraph from my first mail, so the paragraph 
quoted below didn't make a whole lot of sense.]

One issue is whether/how much it's desirable to decouple the emulated hardware 
configuration from the host interface configuration. e.g. should we always 
create N serial ports, regardless of how many -serial options are specified.

> This is maybe slightly different between emulating embedded boards and
> workstation/server class machines. For workstation/server emulation it's
> entirely reasonable to arbitrarily add/remove serial and network devices
> from a "PC" machine based on the user config. For embedded SoC devices you
> tend to want to emulate a fixed number of devices (matching those present
> on real hardware) and leave them present but disconnected if the user does
> not specify appropriate net/serial options.

Paul