> 2) tulip.c appears to be ok, perhaps by luck, even though it doesn't
> disable interrupts explicitly. Although I have seen cases where
> adding interrupt disabling to the transmit routine made bugs in
> this driver go away even in 2.0.x on the Cobalt machines...
But one thing still remains, the tulip driver is broken on my machine and
as Linus pointed out due to
timing problems (and the new tulip.c fixed them for me ). Lucky me has an
alternative de4x5.c but the
bug in tulip AND de4x5.c s still is there. For a bug description of tulip
see my postings last month.
I have 2 machines now, which do not run with de4x5.c EOR tulip.c. "Does
not run" means the driver
works for 1-2 days/hours and then sucks. I'm willing to test any patches
to get this drivers stable.
Regards
Dietmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html