*BSD News Article 2112


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!swrinde!cs.utexas.edu!hellgate.utah.edu!fcom.cc.utah.edu!gateway.univel.com!gateway.novell.com!thisbe!terry
From: terry@thisbe.npd.Novell.COM (Terry Lambert)
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd 0.1 - ne2000 problem work-around
Keywords: 386bsd ne2000
Message-ID: <1992Jul20.162728.8188@gateway.novell.com>
Date: 20 Jul 92 16:27:28 GMT
References: <greg.711512526@hibp1.ecse.rpi.edu>
Sender: terry@thisbe (Terry Lambert)
Organization: Novell NPD -- Sandy, UT
Lines: 26
Nntp-Posting-Host: thisbe.eng.sandy.novell.com

In article <greg.711512526@hibp1.ecse.rpi.edu>, greg@ecse.rpi.edu (Greg) writes:
|>      After I loaded the source, and deleted enough so that I could actually 
|> compile something on my 100MB disk, I rebuilt the kernel. I assigned the
|> ne2000 to use irq2, sacrificing com2. The kernal build was uneventfull except 
|> that I need to apply the "version patch" posted recently. I restrapped the
|> ne2000 to irq3 and away we go! It seems to work.
|> 
|>     Perhaps someone has some insight into why in can't use the irq2 
|> configuration.

Most likely, the "do-it-all" card you mentioned has either an IRQ2 -OR-
one of the higher interrupts.  IRQ2 is the "cascade" interrupt for getting
things like IRQ15.  Generally, unless the software has a real good idea of
how the interrupt controller works, it's bad form to use IRQ2.  I haven't
had a chance to get into the interrupt controller code yet, but I'll see
what I can do.  I suggest that anyone else using IRQ2 be discouraged.  The
same can probably be said of "shared interrupt" devices, like Com1 and Com3
or Com2 and Com4, or a Com2 and a multiport board in the same box, etc.

					Regards,
					Terry Lambert
					terry_lambert@gateway.novell.com
					terry@icarus.weber.edu
---
Disclaimer:  Any opinions in this posting are my own and not those of
my present or previous employers.