Skip to contentSkip to conversation

eepro100: wait_for_cmd_done timeout

DISCUSSION Chris Bacott 2 participants 2 messages Mar 28, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 8 lines

Thanks for the suggestion...
I got another one, telling me to have a look at the e100 driver, and this raises a question I have for quite a long time : why does the Kernel have two different supports for the same hardware ? Is this a migration plan, a long run "please switch from eepro100 to e100" ?
Is there a better working one ?

Becuase, IIRC, eepro100 is the original EtherExpress100 Nic driver written by Becker. the e100 Driver is written initially by Intel, and is a obviously newer. Question is, would you want to use a driver written by the manufacturer of the chip itself, or use a driver that has been in use for MANY years, and has been proven solid. I have an eepro in my laptop, and I just bought two IBM Etherjet NICs, all use this chip. I'm currently using the eepro100 driver, as thats the one I've used for years, but from what I've seen. e100 is going to be the one actively updated, as its Intel's driver. This is the info I got from the IBM and Intel site when I was looking up whether those Etherjet cards were supported in Linux before I bought them.

If any of the above is wrong, some one *please* correct me. I'd rather be told I'm wrong rather than be wrong and thinking I'm right.

Signature · 1 line
Chris Bacott
#1 lore raw
Quoted 8 lines · Chris Bacott
Quoted 8 lines

Thanks for the suggestion...
I got another one, telling me to have a look at the e100 driver, and this raises a question I have for quite a long time : why does the Kernel have two different supports for the same hardware ? Is this a migration plan, a long run "please switch from eepro100 to e100" ?
Is there a better working one ?

Quoted 5 lines

Becuase, IIRC, eepro100 is the original EtherExpress100 Nic driver written by Becker. the e100 Driver is written initially by Intel, and is a obviously newer. Question is, would you want to use a driver written by the manufacturer of the chip itself, or use a driver that has been in use for MANY years, and has been proven solid.

This statement is utterly ridiculous, considering that the poster is having problems with the eepro100 driver. It is obviously, provably _NOT_ solid.

In Red Hat's experience, some people find eepro100 very stable for them, some people find e100 very stable for them. There is no driver which is 100% stable for all people at all times.

Jeff