[tulip] tulip + 2.4?

[Matthew]

No problems here at the moment....However I had to build the module into the 
kernel, which I should do anyway I guess. The tulip.o module ended up in its 
own directory under net. Was that normal? I have no idea what normal is 
though with this kernel.

What distribution are you using??

Matt
On Tuesday 30 January 2001 06:00 pm, Matthew S. Eaton wrote:
> Hi all,
>
> Should the tulip driver compile/run on 2.4 kernels?
>
> Compilation with 2.4.1 :
>
> tulip.c: In function `tulip_open':
> tulip.c:1488: structure has no member named `tbusy'
> tulip.c:1489: structure has no member named `start'
> tulip.c: In function `tulip_start_xmit':
> tulip.c:2607: structure has no member named `tbusy'
> tulip.c:2640: structure has no member named `tbusy'
> tulip.c: In function `tulip_interrupt':
> tulip.c:2659: structure has no member named `interrupt'
> tulip.c:2663: structure has no member named `interrupt'
> tulip.c:2744: structure has no member named `tbusy'
> tulip.c:2748: structure has no member named `tbusy'
> tulip.c:2749: `NET_BH' undeclared (first use in this function)
> tulip.c:2749: (Each undeclared identifier is reported only once
> tulip.c:2749: for each function it appears in.)
> tulip.c:2845: structure has no member named `interrupt'
> tulip.c: In function `tulip_close':
> tulip.c:2991: structure has no member named `start'
> tulip.c:2992: structure has no member named `tbusy'
> tulip.c: In function `tulip_get_stats':
> tulip.c:3031: structure has no member named `start'
> tulip.c: In function `set_rx_mode':
> tulip.c:3303: structure has no member named `tbusy'
>
>
> I would use the native 2.4.1 tulip driver included with the kernel. but:
> i get a bunch of these:
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status fc664010, CSR12 00000000, resetting...
>
> so I prefer the high performance one's here better :-)