Vortex Woes...

[Donald Becker]

On Mon, 1 Feb 1999, Chris J. Richards wrote:

> >Your SCSI driver isn't sharing the interrupt properly.
> >Check /proc/interrupts to confirm this.
> >
> >No driver should use SA_INTERRUPT -- see the bottom of irq-conflict.html
> 
> Hrm.  That must be the case.  I tried a LinkSys (ne2k-pci) and received the
> same SIOCSIFFLAGS message.  I can't say that I know enough to interpret the
> /proc/interrupts to say that the SCSI driver isn't being nice.
..
> In the end, I will have three cards all on IRQ 11 plus the other PCI
> devices.  Right now, I am just trying to get the Vortex or ne2k-pci to work
> as the second before attempting the third.
> 
> Time to figure out what I can do about the SA_INTERUPT with my particular
> SCSI driver.

I shouldn't tell you this, but...
The ethernet drivers will work with SA_INTERRUPT in place of SA_SHIRQ, but
it's EVIL for the rest of the system.

It's easy to write a device driver if you do sleazy things like disable
interrupts for the rest of the system (SA_INTERRUPT) or do software timing
loops (udelay() ) .  The user will blame erratic mouse movement, dropped PPP
packets, sound with clicks and an unreliable clock on the other device
drivers.

Donald Becker					  becker@cesdis.gsfc.nasa.gov
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
301-286-0882	     http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html