Messages in this thread | | | Date | Sun, 13 Jul 1997 21:42:19 +0200 | From | Franz Sirl <> | Subject | Re: Tulip driver & 2.0.30-pre-patch-2 |
| |
At 14:33 13.07.97 -0400, Aaron Tiensivu wrote: > >On Sat, Jul 12, 1997 at 11:53:45PM -0700, JDC wrote: >> I recently tried the 2.0.30-pre-patch-2 which was available >> on ftp.kernel.org under davem's directory, and have a little >> "complaint" to make about it. > >Don't mean to be picky, but: > >> Jul 11 05:16:51 aitsu kernel: tulip.c:v0.76 4/22/97 becker@cesdis.gsfc.nasa.go >> Jul 11 05:16:51 aitsu kernel: eth0: DEC 21041 Tulip at 0x6000, 21041 mode, 00 >c0 f0 15 f8 47, IRQ 10 >> Jul 11 05:16:51 aitsu kernel: THIS IS AN ALPHA TEST DRIVER. >> Jul 11 05:16:52 aitsu kernel: eth0:21041 Media information at 30, default medi >a 0800 (Autosense). >> Jul 11 05:16:52 aitsu kernel: eth0: 21041 media 00 (10baseT), csr13 0004 csr1 >4 0000 csr15 0000. >> Jul 11 05:16:52 aitsu kernel: eth0: 21041 media 00 (10baseT), csr13 0000 csr1 >4 0000 csr15 0000. > >It's an alpha test driver.
It still says that, but for most of the people the new driver works better and it should be included into 2.0.31. Take a look at the cleaned up version <http://homepages.munich.netsurf.de/Franz.Sirl/tulip.c-pre-2.0.31-6> if you want to have the message removed.
>It blows out for me under 2.1 also. ??? I don't see a single bug report on linux-tulip[-bug]@cesdis.gsfc.nasa.gov from you, so how can the bugs be found if you don't report them?
>Use de4x5 instead for now. >Or simply copy the old tulip driver from 2.0.30 into 2.0.31. >In all honesty, I don't really think it should be put into 2.0 just yet. >I've got an SMC EtherPower and the new driver doesn't like it at all.
I think it should remain in 2.0.31, for 95% of the people it's more stable than the old one.
Ciao, Franz.
| |