From owner-freebsd-current Wed Jul 23 11:13:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04269 for current-outgoing; Wed, 23 Jul 1997 11:13:48 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA04263 for ; Wed, 23 Jul 1997 11:13:44 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA15921; Wed, 23 Jul 1997 11:07:25 -0700 From: Terry Lambert Message-Id: <199707231807.LAA15921@phaeton.artisoft.com> Subject: Re: I am contemplating the following change... To: louie@TransSys.COM (Louis A. Mamakos) Date: Wed, 23 Jul 1997 11:07:25 -0700 (MST) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, imp@rover.village.org, sef@kithrup.com, current@FreeBSD.ORG In-Reply-To: <199707230244.WAA24038@whizzo.TransSys.COM> from "Louis A. Mamakos" at Jul 22, 97 10:44:38 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Specifically: > > > > o Not all cards will be on different interrupts > > The ones on an ISA bus ought to be. Certainly I understand how > PCI cards share interrupts. On the other hand, the current PCI > seem to discover the interrupts used already. I was referring to the fact that there is no hardware-based keying that kept the IRQ's from being set the same on cards. Or memory address ranges. Basically, it's a pain in the ass. > Ok, not a 100% solution. > > I was just suggesting that an approach whereby all the ISA interrupts > are preset during autoconfig time to a routine which could note if it > was invoked as a result of a driver's probe activity. Yes, having one > driver poke an unrelated card during probe is a problem, but this > situation really isn't any different than the UNIBUS situation. There's > at least the possibility of a sanity check. Yeah; this is at least moderately useful; it would make the LANCE probes less ambiguous, at least (LANCE chips must be made to squawk to detect them). I'm sure there is some other hardware it might help as well. It's just nowhere near the Unibus soloution; it's unfortunate. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.