Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.hawaii.edu!ames!usenet.kornet.nm.kr!usenet.hana.nm.kr!usenet.seri.re.kr!news.kreonet.re.kr!news.dacom.co.kr!nntp.coast.net!frankensun.altair.com!wlbr!sms From: sms@wlv.iipo.gtegsc.com (Steven M. Schultz) Subject: Two 946Cs sharing IRQ 11 revisited Sender: news@wlbr.iipo.gtegsc.com (Steven M. Schultz) Organization: GTE Government Systems, Thousand Oaks CA USA Message-ID: <DLzF99.Fr6@wlbr.iipo.gtegsc.com> X-Nntp-Posting-Host: wlv.iipo.gtegsc.com Date: Tue, 30 Jan 1996 06:55:56 GMT Lines: 63 > From: se@ZPR.Uni-Koeln.DE (Stefan Esser) > > 2.1R does support shared interrupts for PCI. > The EISA code in -current has recently been > reworked, and it will get that feature, too, > and in fact winterrupt sharing between PCI > and EISA cards will be possible. > > |> I did use the 'conflicts' clause in the kernel config file - without > |> that the second 946C isn't probed due to the IRQ conflict. > > The 946C was only detected as an ISA device > in 2.0.5. In 2.1R it has become a Plug'n'Play > PCI device (i.e. you won't have to specify an > IRQ in the kernel config file, the IRQ assigned > to the PCI slot will automatically be used.). > > > Just try 2.1R, it ought to have got it right :) Alas, I have to report that apparently that is not the case. It's quite possible I've messed up and overlooked the magic config file phraseology but there didn't appear to be anything special needed. Over this last weekend I bought the Walnut Creek FreeBSD 2.1 CD and installed it tonight. The Buslogic 946C is apparently not being detected as a PCI device. The PCI probing logic does report two entries with "Buslogic" but both have "[no driver assigned]". I did try leaving off all other information in the kernel config file lines: controller bt0 controller bt1 but that caused the kernel to skip completely the two 946C cards. Entries of the form: controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr controller bt1 at isa? port "0x334" bio irq ? vector btintr produce a "conflict" on IRQ11 and the second one is not probed at all. But at least the devices on the first SCSI chain are useable. Entries of the form: controller bt0 at isa? port "IO_BT0" bio irq ? vector btintr controller bt1 at isa? port "0x334" bio conflicts irq ? vector btintr cause a successful probe of both SCSI chains (finding all devices), but the system hangs when accessing the devices later because ISA devices can't share IRQs. Is there a limitation on which devices are probed for in the PCI space? "ncr0", "de0" and so on are the only ones listed in the "LINT" (sample) configure file - perhaps the 'bt' driver isn't PCI aware? Would seem likely judging from what I'm seeing. Steven Schultz sms@wlv.iipo.gtegsc.com