public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcus Sundberg <marcus@ingate.com>
To: Matthew Hall <matt@ecsc.co.uk>
Cc: Kernel <linux-kernel@vger.kernel.org>, jgarzik@mandrakesoft.com
Subject: Re: [PROBLEM] sundance on d-link dfe-580tx
Date: 14 Jun 2002 12:15:12 +0200	[thread overview]
Message-ID: <vesn3q2mkv.fsf@inigo.ingate.se> (raw)
In-Reply-To: <1023799395.3064.49.camel@smelly.dark.lan>

Matthew Hall <matt@ecsc.co.uk> writes:

> I have been testing the D-Link DFE-580TX Quad channel server card (4
> port nic), on kernel 2.4.18 with little success. 

[snip]

> I would appreciate being informed if there is a fix in a later
> version,or if any more debugging information is required I would be
> happy to oblige.

I have to define USE_IO_OPS to get the sundance driver to work with
the DFE-580TX. I haven't investigated why.

//Marcus
-- 
---------------------------------------+--------------------------
  Marcus Sundberg <marcus@ingate.com>  | Firewalls with SIP & NAT
 Firewall Developer, Ingate Systems AB |  http://www.ingate.com/

  parent reply	other threads:[~2002-06-14 10:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11 12:43 [PROBLEM] sundance on d-link dfe-580tx Matthew Hall
2002-06-12  3:39 ` Donald Becker
2002-06-13 14:57   ` Matthew Hall
2002-06-13 15:34     ` Ben Greear
2002-06-13 16:12     ` Donald Becker
2002-06-14 16:06       ` Matthew Hall
2002-06-14 21:52         ` Donald Becker
2002-06-21  5:27     ` Jeff Garzik
2002-06-21 12:17       ` Matthew Hall
2002-07-12  2:41   ` kwijibo
2002-06-14 10:15 ` Marcus Sundberg [this message]
     [not found]   ` <1024070521.973.48.camel@smelly.dark.lan>
     [not found]     ` <vevg8l25uq.fsf@inigo.ingate.se>
2002-06-17 14:58       ` Matthew Hall

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=vesn3q2mkv.fsf@inigo.ingate.se \
    --to=marcus@ingate.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@ecsc.co.uk \
    /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