mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mroczek, Joseph T" <joseph.t.mroczek@intel.com>
To: linux-kernel@vger.kernel.org
Subject: RE: EEPRO100/S support
Date: Fri, 22 Jun 2001 15:46:34 -0700	[thread overview]
Message-ID: <10C8636AE359D4119118009027AE998709BE50E3@FMSMSX34> (raw)

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]



>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.
>

A temporary workaround for e100-1.6.6 that works in most cases is to
disable the CPUSaver features by using the ucode=0 option.

>
>I've no idea if the e100 works on anything other than ia32/ia64.

Yes it does. At this point it should be platform independent, I see all
the required changes for both big and little endian support. 

~joe

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2199 bytes --]

             reply	other threads:[~2001-06-22 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 22:46 Mroczek, Joseph T [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-18  4:27 J.S.Peatfield
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=10C8636AE359D4119118009027AE998709BE50E3@FMSMSX34 \
    --to=joseph.t.mroczek@intel.com \
    --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

all inboxes | Powered by JetHome®