From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34)
	id 1BNFqF-00024R-KX
	for qemu-devel@nongnu.org; Mon, 10 May 2004 14:49:31 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34)
	id 1BNFjg-0000YF-53
	for qemu-devel@nongnu.org; Mon, 10 May 2004 14:43:18 -0400
Received: from [193.252.22.28] (helo=mwinf0301.wanadoo.fr)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNFa6-0005Ul-IZ
	for qemu-devel@nongnu.org; Mon, 10 May 2004 14:32:50 -0400
Received: from bellard.org (ATuileries-112-1-4-36.w81-53.abo.wanadoo.fr
	[81.53.133.36])
	by mwinf0301.wanadoo.fr (SMTP Server) with ESMTP id E6BAE400382
	for <qemu-devel@nongnu.org>; Mon, 10 May 2004 20:31:48 +0200 (CEST)
Message-ID: <409FCB1B.2020005@bellard.org>
Date: Mon, 10 May 2004 20:34:03 +0200
From: Fabrice Bellard <fabrice@bellard.org>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Using ISA-PNP for resource management
References: <1084144380.6742.31.camel@matt>
In-Reply-To: <1084144380.6742.31.camel@matt>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.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://mail.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Matthew Mastracci wrote:
> I was looking at how much work it would take to switch to using ISA-PNP
> for resource management.  I believe that it might simplify some of the
> QEMU internals, as well as make things like having multiple
> network/other devices much easier.  It may make moving to PCI (or having
> an option to boot with either ISAPNP or PCI on the fly) much easier.
> 
> For anyone interested, the ISAPNP spec page is at:
> 
>  http://osdev.neopages.net/docs/PNP-ISA-v1.0a.pdf?the_id=54
> 
> I believe the best way to implement ISA-PNP would be for each device to
> register an ISA-PNP context, then add specific resource requirements to
> the context as necessary.  The ISAPNP manager would then interact with
> the operating system and call the isapnp_configure method whenever the
> OS changes the setup.
> 
> Perhaps something like this.  I would imagine that the ISAPNP resource
> manager would clear the IO port range back to the default IO port
> manager before calling the *_isapnp_configure routine:

OK for ISAPNP, but it should just indicate what is the hardcoded 
configuration. I don't want to use it to set the exact ioports and irqs. 
Moreover PCI is about to be integrated in QEMU, so it may not be worth 
the effort.

Fabrice.