From owner-freebsd-hackers Wed Jul 10 22:18:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA15641 for hackers-outgoing; Wed, 10 Jul 1996 22:18:27 -0700 (PDT) Received: from localhost.my.domain (root@morrison-c09.aa.net [204.157.220.141]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA15635 for ; Wed, 10 Jul 1996 22:18:25 -0700 (PDT) Received: from localhost (smpatel@localhost [127.0.0.1]) by localhost.my.domain (8.7.5/8.6.12) with SMTP id WAA01556; Wed, 10 Jul 1996 22:18:10 -0700 (PDT) Date: Wed, 10 Jul 1996 22:18:09 -0700 (PDT) From: Sujal Patel X-Sender: smpatel@localhost To: Amancio Hasty cc: hackers@freebsd.org Subject: Re: Puting PnP support into -current by default In-Reply-To: <199607101929.MAA09509@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Jul 1996, Amancio Hasty wrote: > > device gus0 at isa? port 0x220 irq 11 drq 5 flags 0x7 vector gusintr > > In this case, the gus driver at probe times calls the PnP routines however > it uses the configuration values pass to the driver to activate and > configure the GUS PnP. Unfortunately, simplify it down to a simple case like this isn't easy AT ALL. There are things like logical devices, multiple irqs/drqs, serial numbers, and zillions of other things that need to be handled. Also, the code needs to be generic enough to handle all ISA PnP devices. I'll try to speed up development on this stuff a bit, but I'm still a bit off from being ready to commit. Unless someone *really* wants to see the stuff "kludged" into -current sooner. Sujal