> Adam Heath wrote:
>
> > The tulip driver will only work with my cards(macronix) for 4 secs. I start a
> > ping from a remote machine, get no response, ifconfig eth0 up, get 4 pings,
> > then the card goes down. A simple ifconfig down/up cycle lets it work again,
> > but it still errors out. Even without any traffic, the card will still
> > disable itself.
>
> The issue seems to be the tulip v0.90 is said to have problems
> on machines where the older ones work.
>
> But also a known issue is that tulips older than v0.90 do not
> work reasonably at all for several clone chipsets, including
> Macronix. At least in the Macronix case this is only
> an issue about correctly initializing some of the chips registers.
>
> So a moderate low risk solution would be to "backport"
> the clone init business to the older tulip. Risk should
> be low as only the init routines need to be touched.
>
> But since noone commented on that I didn't do anything.
Another solution, which is hackish at best, is to include BOTH 0.89 and 0.90
in the kernel. tulip.c = .89, tulip2.c = .90. Modify tulip2.c to reports its
different name, and modify config.in to fit. And make a BIG FAT WARNING(TM)
noting the problems with both versions of the driver.
Adam
-
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/