From: J.S.Peatfield@damtp.cam.ac.uk
To: linux-kernel@vger.kernel.org
Cc: J.S.Peatfield@damtp.cam.ac.uk
Subject: Re: EEPRO100/S support
Date: Mon, 18 Jun 2001 05:27:58 +0100 (BST) [thread overview]
Message-ID: <200106180427.FAA20673.declaim.amtp.cam.ac.uk@damtp.cam.ac.uk> (raw)
> FWIW, I believe Intel's Linux drivers will support this card under
> 2.4, and I believe (not 100% certain on this) that they're GPL. I'll
> have to check on that.
The e100 driver from intel claims to support these cards (the 100 S
desktop adaptor, that is), but in fact the drivers lock up under heavy
UDP load (at least they do for me in 2.2.19). It seems to only be a
problem with these newer cards, the e100 is solid with older cards
(and things like the 100VE which is onboard on many Easterns).
Intel are working on fixing the lockups, they thought it was related
to the checksum offload though turning that off doesn't prevent the
lockups. Version 1.66 is much more stable than 1.55a (1.55a would
lockup after 60-80M of traffic on these cards), I'm awaiting the next
version to see if they have nailed it.
The driver is not GPL (I don't know why it isn't) and doesn't support
the encryption asic on baords which have it (and Intel seem unwilling
to release details of this asic so others can write drivers to use
it).
I've no idea if the e100 works on anything other than ia32/ia64.
next reply other threads:[~2001-06-18 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 4:27 J.S.Peatfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-22 22:46 EEPRO100/S support Mroczek, Joseph T
2001-06-15 20:57 Tim Hockin
2001-06-15 21:54 ` Kelledin Tane
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=200106180427.FAA20673.declaim.amtp.cam.ac.uk@damtp.cam.ac.uk \
--to=j.s.peatfield@damtp.cam.ac.uk \
--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;
as well as URLs for NNTP newsgroup(s).