From owner-freebsd-hackers Wed Jan 10 18:30:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA22173 for hackers-outgoing; Wed, 10 Jan 1996 18:30:07 -0800 (PST) Received: from sl-015.sl.cybercomm.net (sl-015.sl.cybercomm.net [199.171.196.143]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA22142 for ; Wed, 10 Jan 1996 18:29:55 -0800 (PST) Received: from sl-015.sl.cybercomm.net (localhost [127.0.0.1]) by sl-015.sl.cybercomm.net (8.6.12/8.6.12) with SMTP id VAA11155; Wed, 10 Jan 1996 21:22:30 -0500 Date: Wed, 10 Jan 1996 21:22:30 -0500 (EST) From: Sujal Patel X-Sender: smpatel@sl-015.sl.cybercomm.net To: "Justin T. Gibbs" cc: Neil Bradley , Terry Lambert , hasty@rah.star-gate.com, freebsd-hackers@freebsd.org Subject: Re: PnP problem... In-Reply-To: <199601110207.SAA20869@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Wed, 10 Jan 1996, Justin T. Gibbs wrote: > Yes, it would require a lot of work in the ISA area, but the PCI and EISA > code could be changed to work this way rather easily. My init order > is slightly different though: [...] > The listing is not complete, but you get the idea. You should keep this > in mind while doing your PnP work since I think this is the approach > we should be shooting for. I have been keeping this in mind while I was coding. To change over to a scheme that you described would be very simple. Right now, I just gather the PnP configuration information from the kernel configuration; this would simply change to information from PCI/EISA/ISA probes, after the ISA code was cleaned up. A couple of quick questions: Is there a unified structure where one can access the information from PCI/EISA/ISA probes? How well can the ISA code non-invasively probe devices (currently)? Sujal