[tulip] Re: tulip + 2.4

Dave Turner dkturner@qwest.net
Wed, 31 Jan 2001 09:47:50 -0800


Try compiling using kgcc rather than gcc and see if that makes a difference.
Also, put -I/usr/src/linux/include in your compile command line.  I had
similar errors and those two changes got the source to compile.  FWIW, this
information is on the scyld.com site under "Redhat 7.0 Instructions" or
somesuch.  I didn't see it the first time around either, but it is there in
plain site.

Dave
----- Original Message -----
From: <tulip-admin@scyld.com>
To: <tulip@scyld.com>
Sent: Wednesday, January 31, 2001 9:00 AM
Subject: tulip digest, Vol 1 #192 - 2 msgs


>
> Send tulip mailing list submissions to
> tulip@scyld.com
>
> To subscribe or unsubscribe via the web, visit
> http://www.scyld.com/mailman/listinfo/tulip
> or, via email, send a message with subject or body 'help' to
> tulip-request@scyld.com
> You can reach the person managing the list at
> tulip-admin@scyld.com
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of tulip digest..."
>
>
> Today's Topics:
>
>   1. tulip + 2.4? (Matthew S. Eaton)
>   2. Re: tulip + 2.4? (Matthew)
>
> --__--__--
>
> Message: 1
> Date: Tue, 30 Jan 2001 21:00:30 -0500
> From: "Matthew S. Eaton" <matthewe@virginia.edu>
> Organization: University of Virginia
> To: tulip@scyld.com
> Subject: [tulip] tulip + 2.4?
>
> 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 :-)
>
> --
> Matthew S. Eaton
> Undergraduate
> University of Virginia
> School of Engineering and Applied Science
>
>
> --__--__--
>
> Message: 2
> From: Matthew <matthew@psychohorse.com>
> Reply-To: matthew@psychohorse.com
> To: "Matthew S. Eaton" <matthewe@virginia.edu>, tulip@scyld.com
> Subject: Re: [tulip] tulip + 2.4?
> Date: Tue, 30 Jan 2001 19:35:27 -0800
> charset="us-ascii"
>
> 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 :-)
>
>
>
> --__--__--
>
> _______________________________________________
> tulip mailing list
> tulip@scyld.com
> http://www.scyld.com/mailman/listinfo/tulip
>
>
> End of tulip Digest
>