From: Peter Bieringer <pb@bieringer.de>
To: Maillist netdev <netdev@oss.sgi.com>
Subject: Re: sundance driver does not work with D-Link DFE-580TX
Date: Thu, 19 Jun 2003 14:43:53 +0200 [thread overview]
Message-ID: <57880000.1056026633@worker.muc.bieringer.de> (raw)
In-Reply-To: <200305261604.h4QG4iQY020725@sandelman.ottawa.on.ca>
--On Monday, May 26, 2003 12:04:43 PM -0400 Michael Richardson
<mcr@sandelman.ottawa.on.ca> wrote:
>
>>>>>> "Peter" == Peter Bieringer <pb@bieringer.de> writes:
> Peter> pls. take a look into:
>
> Peter> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=69000
>
> Peter> Looks like current included "sundance.c" driver doesn't work
> proper Peter> together with current "mii.c" on a D-Link DFE-580TX.
>
> This is a redhat bug. Stock kernels do not have this problem.
> Nor does pure-Becker code.
I (also others independed) finally find the bug:
RHL uses CONFIG_SUNDANCE_MMIO=y on kernel building which causes the
problem.
Looks like this option should be removed or the driver should be improved
(perhaps autodetection?). Imho it doesn't make much sense to add an compile
option which (in case of enabled) break usages of already available NICs.
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
next prev parent reply other threads:[~2003-06-19 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 14:27 sundance driver does not work with D-Link DFE-580TX Dr. Peter Bieringer
2003-05-26 16:04 ` Michael Richardson
2003-06-19 12:43 ` Peter Bieringer [this message]
2003-06-19 17:19 ` Jeff Garzik
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=57880000.1056026633@worker.muc.bieringer.de \
--to=pb@bieringer.de \
--cc=netdev@oss.sgi.com \
/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).