From owner-freebsd-hackers Wed Jan 10 17:35:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA19262 for hackers-outgoing; Wed, 10 Jan 1996 17:35:01 -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 RAA19249 for ; Wed, 10 Jan 1996 17:34:41 -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 UAA10672; Wed, 10 Jan 1996 20:27:14 -0500 Date: Wed, 10 Jan 1996 20:27:14 -0500 (EST) From: Sujal Patel X-Sender: smpatel@sl-015.sl.cybercomm.net To: Neil Bradley cc: Terry Lambert , hasty@rah.star-gate.com, freebsd-hackers@FreeBSD.org Subject: Re: PnP problem... In-Reply-To: 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, Neil Bradley wrote: > You mean to say that the GUS uses two interrupts for one ISA card? Now > that is stupid. The GUS PnP uses *3* interrupts :) As Amancio explained earlier, it's unavoidable since each "logical" part of the card is handled by a different driver. > 1) Disable all PNP devices > 2) Probe for ISA > 3) Obtain EISA information - report conflicts with ISA devices > 4) Initialize EISA devices > 5) Init PnP devices > 6) Init PCI devices > 7) Boot system ;-) Unfortuantely, this won't work... In FreeBSD, it goes Init PCI Init EISA Init PC-Card Init ISA This seems like a pretty intergal part of the boot process. I really don't see changing this without ripping about huge amounts of code (Which I'm not going to do, just to introduce this minor addition to the kernel). Sujal