Return to BSD News archive
#! rnews 1654 bsd Newsgroups: comp.unix.bsd.bsdi.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!vtc.tacom.army.mil!ulowell.uml.edu!europa.chnt.gtegsc.com!news.mathworks.com!udel!rochester!bukys From: Liudvikas Bukys <bukys@cs.rochester.edu> Subject: IRQ question Message-ID: <199508171551.LAA18592@otter.cs.rochester.edu> Sender: bukys@cs.rochester.edu (Liudvikas Bukys) Organization: University of Rochester Computer Science Dept Date: Thu, 17 Aug 1995 11:51:14 -0400 Lines: 36 I had the following experience. Can someone tell me how this is _supposed_ to work? I have a HP Netserver/LC (PCI/EISA machine), with a PCI BusLogic BT946C SCSI controller (not relevant to this discussion), and a 3COM 3C579TP (EISA ethernet controller). The automatic EISA setup assigned IRQ 5 to the 3C579. (It had an onboard Adaptec SCSI controller that it assigned IRQ 15 to.) BSDI 2.0 booted up, but the Ethernet driver assigned IRQ 15 to the board. It didn't work. It worked when I used the EISA setup program to change the 3C579's IRQ to 15, to match the kernel's expectations. I took a quick look at the driver code, but I'm not sure what's supposed to happen. I'm still a bit PC-ignorant. Is the kernel supposed to ask the board what IRQ it will use, or does the kernel try tell the board what IRQ it will use? Is there some simple explanation for why the board and the kernel initially chose different values? [Incomplete EISA support in BSDI?] Liudvikas Bukys University of Rochester Computer Science Department 734 Computer Studies Building Rochester, NY 14627-0226 tel# 716-275-7747 fax# 716-461-2018 <bukys@cs.rochester.edu>