From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Dennis <dennis@etinc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: intel etherpro100 on 2.2.18p21 vs 2.2.18p17
Date: Fri, 17 Nov 2000 17:06:50 +0800 [thread overview]
Message-ID: <20001117170650.A27444@saw.sw.com.sg> (raw)
In-Reply-To: <93BA6BFC5E48D4118A8200508B6BBC4924AB7A@sf1-mail01.hamquist.com> <Pine.LNX.4.10.10011111111390.18876-100000@pmcl.ph.utexas.e du> <5.0.0.25.0.20001114171416.01f7b8f0@mail.etinc.com>
In-Reply-To: <5.0.0.25.0.20001114171416.01f7b8f0@mail.etinc.com>; from "Dennis" on Tue, Nov 14, 2000 at 05:18:25PM
Hello,
On Tue, Nov 14, 2000 at 05:18:25PM -0500, Dennis wrote:
> There is a flaw in the eepro100 driver that apparently doesnt initialise
> something properly. The problem is exasperated by the fact that the
If one want to say it politely, the driver and the hardware sometimes
disagree about the initializing sequence.
Without full documentation, it's hard to say if the driver doesn't follow the
specification or it is a faulty hardware.
For example, I've never observed these problems on hardware except 82559ER.
> eepro100 driver doesn handle the buffer problem properly. We've corrected
> it by (effectively) resetting the card (by calling close and then open)
> when the first out of resources event occurs. Its not elegant, but it seems
> to work.
Best regards
Andrey V.
Savochkin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-17 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10011111111390.18876-100000@pmcl.ph.utexas.e du>
2000-11-11 0:24 ` Allen, David B
2000-11-11 17:15 ` michael
2000-11-13 9:31 ` Andrey Savochkin
2000-11-14 22:18 ` Dennis
2000-11-17 9:06 ` Andrey Savochkin [this message]
2000-11-10 17:00 michael
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=20001117170650.A27444@saw.sw.com.sg \
--to=saw@saw.sw.com.sg \
--cc=dennis@etinc.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®