linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Robottom Reis <kiko@async.com.br>
To: <eepro100@scyld.com>
Cc: <saw@saw.sw.com.sg>, <linux-kernel@vger.kernel.org>
Subject: Re: eepro100 problems with 2.2.19 _and_ 2.4.0
Date: Sun, 17 Jun 2001 00:40:34 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.32.0106170037020.191-100000@blackjesus.async.com.br> (raw)
In-Reply-To: <Pine.LNX.4.32.0106161923290.339-100000@blackjesus.async.com.br>

On Sat, 16 Jun 2001, Christian Robottom Reis wrote:

> I'm having a ton of problems with a set of boxes that use an onboard
> variant of the eepro100. I'm not sure what version it is (#$@#*&$@ Intel
> documentation - motherboard is model D815EEA2) but eepro100-diag reports:
>
> eepro100-diag.c:v2.05 6/13/2001 Donald Becker (becker@scyld.com)
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Intel i82562 Pro/100 V adapter at 0xdf00.

I've just tested with Intel's epro-1.6.6 driver, and it does work (the
full bonanza works; simultaneous netperf and ftp and whatnot run with no
errors or hangs). This makes my situation a bit easier (and my head a bit
less confused, specially with Andrey pointing out the different versions
to the driver).

I am _very_ willing to devote some time to getting this fixed in both the
kernel and Donald's drivers if anyone is interested in tracking down the
problem. I'm not very familiar with the hardware, but I have a test box I
can use freely, a bit of time spare, and I can reproduce the problem
easily. I'd hate to see somebody else go through what I have just had to,
so it would be nice to see this fixed or documented in an official-ese
place.

Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311


  parent reply	other threads:[~2001-06-17  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-17  2:26 eepro100 problems with 2.2.19 _and_ 2.4.0 Christian Robottom Reis
2001-06-17  2:43 ` Christian Robottom Reis
2001-06-17 15:49   ` Jeff Chua
2001-06-17 19:09     ` Christian Robottom Reis
2001-06-18  8:48       ` Jeff Chua
2001-06-17  3:40 ` Christian Robottom Reis [this message]
2001-06-18 19:41   ` Andrey Savochkin

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=Pine.LNX.4.32.0106170037020.191-100000@blackjesus.async.com.br \
    --to=kiko@async.com.br \
    --cc=eepro100@scyld.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    /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).