>
> I don't claim that the shared interrupt _should_ interfere but do you
> see a specific reason why it would hurt the 8139too driver ?
>
Well, not really
Just surprised me
Aritz
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
Mor
Aritz Bastida <[EMAIL PROTECTED]> :
[...]
> Anyway I don't understand why shared interrupt should interfere. In
> theory nothing would be done if a interface receives a irq triggered
> by another. This is at the beginning of rtl8139_interrupt:
>
> /* shared irq? */
> if (unlikely((
2005/12/30, Francois Romieu <[EMAIL PROTECTED]>:
> Aritz Bastida <[EMAIL PROTECTED]> :
> [...]
I don't understand. Is there any problem with my email address?
>
> Interrupt Status Register bits are always set to 1, if the condition
> if present, regardless of the state of the corresponding mask b
Aritz Bastida <[EMAIL PROTECTED]> :
[...]
Interrupt Status Register bits are always set to 1, if the condition
if present, regardless of the state of the corresponding mask bit.
(courtesy of the 8139C(L)+ manual)
-> The interrupt mask register simply prevents the interrupts.
Can you send the co
Hello,
I think there is some kind of bug or something in the driver 8139too.
Supossedly, receive interrupts are disabled when a hardware interruption
is received, but anyway receive interrupts keep on triggering. Below I show
the two interruption masks are used throughtout the driver. The first is
