public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Lunz <lunz@reflexsecurity.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DFE-580TX problems you posted on 05-24-02
Date: Wed, 24 Jul 2002 11:25:48 -0400	[thread overview]
Message-ID: <20020724152548.GA3967@reflexsecurity.com> (raw)
In-Reply-To: <3D3DCD2C.1050004@candelatech.com>

In gmane.linux.kernel, you wrote:
> The fix for the DFE-580tx in Linux is to either download the driver
> from dlink's site (I don't have the exact URL, but you can find it if
> you look.), or perhaps use Becker's latest driver from www.scyld.com.

That's not the whole story.

All the drivers I've tried will work if compiled with USE_IO_OPS
defined, but will behave badly under load. That is, when heavily loaded
they will lock up and reset after a several-second timeout expires. This
is true for Becker's 1.09 driver, the latest in-kernel driver, and
Edward Peng's napi sundance driver. (With the exception that the napi
driver doesn't recover after it locks up). Peng's driver is at
http://edward_peng.tripod.com/, and his email address from the dl2k
driver indicates that he works for Dlink.

I looked on dlink's web and ftp sites, but was unable to find any linux
driver for the DFE-580TX. How did you find it?

-- 
Jason Lunz			Reflex Security
lunz@reflexsecurity.com		http://www.reflexsecurity.com/

  reply	other threads:[~2002-07-24 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020723203037.GA29459@pobox.com>
2002-07-23 21:39 ` DFE-580TX problems you posted on 05-24-02 Ben Greear
2002-07-24 15:25   ` Jason Lunz [this message]
2002-09-05 21:35   ` Ryan S. Upton
2002-09-09 16:42     ` Stephan von Krawczynski

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=20020724152548.GA3967@reflexsecurity.com \
    --to=lunz@reflexsecurity.com \
    --cc=greearb@candelatech.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