qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Using ISA-PNP for resource management
Date: Mon, 10 May 2004 20:34:03 +0200	[thread overview]
Message-ID: <409FCB1B.2020005@bellard.org> (raw)
In-Reply-To: <1084144380.6742.31.camel@matt>

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.

  reply	other threads:[~2004-05-10 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09 23:13 [Qemu-devel] Using ISA-PNP for resource management Matthew Mastracci
2004-05-10 18:34 ` Fabrice Bellard [this message]
2004-05-10 21:31   ` [Qemu-devel] " Matthew Mastracci
2004-05-10 18:57 ` Matthew Mastracci

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=409FCB1B.2020005@bellard.org \
    --to=fabrice@bellard.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).