From: Ben Greear <greearb@candelatech.com>
To: Jurgen Botz <jurgen@botz.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: eepro100.c & Intel integrated MBs
Date: Mon, 29 Oct 2001 10:16:28 -0700 [thread overview]
Message-ID: <3BDD8EEC.6DFE6BA5@candelatech.com> (raw)
In-Reply-To: <11361.1004374395@nova.botz.org>
Jurgen Botz wrote:
> 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
next prev parent reply other threads:[~2001-10-29 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 16:53 eepro100.c & Intel integrated MBs Jurgen Botz
2001-10-29 17:16 ` Ben Greear [this message]
2001-10-29 17:33 ` Arjan van de Ven
2001-10-29 17:49 ` Ben Greear
2001-10-29 18:01 ` Alan Cox
2001-10-29 18:52 ` J Sloan
2001-10-29 18:05 ` Alan Cox
2001-10-29 17:29 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BDD8EEC.6DFE6BA5@candelatech.com \
--to=greearb@candelatech.com \
--cc=jurgen@botz.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox