From owner-freebsd-hackers  Sun Jan 14 14:12:17 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA26831
          for hackers-outgoing; Sun, 14 Jan 1996 14:12:17 -0800 (PST)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA26713
          for <freebsd-hackers@FreeBSD.org>; Sun, 14 Jan 1996 14:11:57 -0800 (PST)
Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id OAA01251; Sun, 14 Jan 1996 14:11:14 -0800
Message-Id: <199601142211.OAA01251@rah.star-gate.com>
X-Mailer: exmh version 1.6.5 12/11/95
To: Terry Lambert <terry@lambert.org>
cc: smpatel@wam.umd.edu (Sujal Patel), freebsd-hackers@FreeBSD.org,
        kashmir@umiacs.umd.edu
Subject: Re: PnP Proposal, Ideas & Issues [Was: PnP problem...] 
In-reply-to: Your message of "Wed, 10 Jan 1996 14:35:00 MST."
             <199601102135.OAA15484@phaeton.artisoft.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 14 Jan 1996 14:11:13 -0800
From: "Amancio Hasty Jr." <hasty@rah.star-gate.com>
Sender: owner-hackers@FreeBSD.org
Precedence: bulk

Yeap, Sujal's solution is not optimal however it is infinitly superior
to your solution 8)

At least Sujal, is making steady progress .

Just because a card is a PnP does not mean that the card is 
fully reconfigurable. Hence, is not too difficult to see how
a PnP system may fail to autoconfigure itself.

Even if we can't probe ISA devices 100% of the times we can 
configure and test the configuration of PnP devices.


	Amancio

>>> Terry Lambert said:
 > > So the first goal was to be able to specify certain resources that a PnP 
 > > card should use:
 > > 
 > > I was hoping that we could strive for something along of the lines of:
 > > device          sio2    at isa? pnp "SUP1310" port "IO_COM3" tty irq 15 ve
     ctor siointr
 > > 
 > > This would be nice and simple-- Say that PnP device "SUP1310" is handled
 > > by driver sio2 and configure the card and the driver for port 0x3e8 and
 > > irq 15.  But unfortunately, the solution is not going to nearly this
 > > simple.  Cards like the GUS PnP and other multi-function cards cannot be
 > > configured like this at all.
 > 
 > This is probably a bad approach.  The idea of PnP is that the devices
 > will fit into an unused space.  This is a difficult (and potentially
 > insoluable without a hack job) problem for non-PnP ISA devices in a
 > standard ISA bus, since if you can't probe them, you can't predict
 > what the conflicts would be.
 > 
 > > I'm sure that we're gonna always need some kind of manual configuration 
 > > of PnP devices (for those really though cards like the GUS).  The 
 > > majority of PnP cards should be very simple to configure (and could 
 > > be done automatically at boot-time).  The problem is that it seems VERY 
 > > difficult to determine exactly what resources are going to be used when 
 > > the system is booting.  
 > 
 > I think you'd need manual configuration of unprobeable hardware to set
 > up the intersects for it.  Other than that, I don't think you *really*
 > have to manually config the cards.
 > 
 > 
 > 					Terry Lambert
 > 					terry@lambert.org
 > ---
 > Any opinions in this posting are my own and not those of my present
 > or previous employers.
 >