From owner-freebsd-hackers  Thu Sep 11 22:11:43 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA03299
          for hackers-outgoing; Thu, 11 Sep 1997 22:11:43 -0700 (PDT)
Received: from word.smith.net.au (word.smith.net.au [202.0.75.3])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA03282
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 11 Sep 1997 22:11:32 -0700 (PDT)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA01205;
	Fri, 12 Sep 1997 14:39:18 +1000 (EST)
Message-Id: <199709120439.OAA01205@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Terry Lambert <tlambert@primenet.com>
cc: gurney_j@resnet.uoregon.edu, luigi@labinfo.iet.unipi.it, mike@smith.net.au,
        perhaps@yes.no, freebsd-hackers@FreeBSD.ORG
Subject: Re: PnP support 
In-reply-to: Your message of "Thu, 11 Sep 1997 22:45:48 GMT."
             <199709112245.PAA17225@usr03.primenet.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 12 Sep 1997 14:39:15 +1000
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I was actually thinking about a "dummy" driver that pretended to be
> a device driver for the devices.  This would actually allow a boot -c
> (if it could edit the irq/io/base) to be used to configure dummy
> devices into the conflict space so that nothing gets located on top
> of them.

See the PnP spec, section 4.3 on the I/O Range Check register for the 
major solution to this problem.  See your BIOS for the IRQ/DRQ 
allocation configuration options (ISA/PnP toggle).  

The only losing case now is a system with no ECSD support, ie. "legacy" 
hardware.  A userconfig-level "list of available IRQ/DRQ" option sounds 
pretty good here.

mike