> I'm now using the e100 driver from the Intel web site, which works
> perfectly, and light testing shows the Scyld (Don Becker) driver
> to work as well. The Intel driver seems to have an incompatible
> license (noxious advertising clause?), but the Scyld drivers don't...
> at least there isn't any license mentioned and of course many
> of the net drivers in the current kernel are just earlier versions
> of the Scyld drivers.
The Scyld drivers have only recently started working with the 2.4 series,
and there is some unholly war between Becker and the rest of the kernel
hackers...so I don't think you'll ever see his drivers in the standard
kernel again... RH usually tries to load the e100 (Intel's driver)
instead of the eepro100. The e100's license is close to compatible
with the kernel, and I've heard rumors that the remaining issues may
be worked out... I've also heard the code is ugly as hell...but it
does seem to work. If only the e100 supported MII IOCTLs then I'd
use it all the time!
-- Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/