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.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!news.kei.com!nntp.coast.net!frankensun.altair.com!wlbr!sms From: sms@wlv.iipo.gtegsc.com (Steven M. Schultz) Subject: Can Multiple 946Cs share an IRQ? Sender: news@wlbr.iipo.gtegsc.com (Steven M. Schultz) Organization: GTE Government Systems, Thousand Oaks CA USA Message-ID: <DL78Mt.MsA@wlbr.iipo.gtegsc.com> X-Nntp-Posting-Host: wlv.iipo.gtegsc.com Date: Mon, 15 Jan 1996 01:40:05 GMT Lines: 24 I recently added a second Buslogic 946C (the new one is a Rev E card, the original one is a Rev B card from a year ago) because I'd filled up the first SCSI chain. If the problem I'm seeing is fixed in 2.1 that's fine - I'll replace 2.0.5 with that as soon as I order the CD. Basically the system is out of IRQs so I need to share IRQ 11 for both 946C cards. Using 'level triggered' interrupts this should be possible if the underlying system supports it (with BSD/OS everything's happy as a clam sharing IRQ 11). Does FreeBSD 2.0.5 have support for shared IRQs for PCI (EISA too since it can level triggered interrupts)? 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 autoconfig probing does indeed find both 946C cards and all the devices on them. But the first access of any device on the second controller hangs the system completely to the point where mashing the reset button is required. Steven Schultz sms@wlv.iipo.gtegsc.com