John P. Looney wrote:
> On Thu, Mar 07, 2002 at 11:32:05PM +0000, Niall O Broin mentioned:
>>>The only thing that bugs me is that I keep running into these EEpro NICs
>>(you know where I first encountered them, John) and they cause me various
>>problems which I wouldn't have if Intel would just contribute their code to
>>>> Their licence is BSD. That means that if they kernel lads want to, they
> can take the Intel driver code, stamp a GPL on it, stick it into the
> kernel, and call it something else, as long as they leave the "Written by
> intel" notices there. But I've seen some of the networking lads, not just
> Alan Cox, say "the e100 driver is crap. That's why we don't use it".
>>>>Incidentally, the bizarre problem I had whereby the machine in question
>>crashes if I attempt to ssh to it is NOT resolved by using the Intel
>>driver, although as mentioned it has been resolved by moving to 2.4.18
>>>> The eepro100 had a big overhaul in 2.4.17 and 2.4.18. What version of the
> e100 driver were you using ?
Jeff Garzik is merging the good bits out of Intel's driver (e100)
into eepro100. Note e100 has various latency issues and is generally
different enough from the "standard" that they wont use it by default.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!