From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Michael Mueller <malware@t-online.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] Making de2104x working with BNC connection on 21040 chipset
Date: Fri, 13 Jan 2012 13:43:58 -0500 [thread overview]
Message-ID: <CAP=VYLpWbcBae11fcQPcuPmdfvir7N6F9QMdzXip=i4mMHjxsQ@mail.gmail.com> (raw)
In-Reply-To: <4F0F641B.5090407@t-online.de>
On Thu, Jan 12, 2012 at 5:52 PM, Michael Mueller <malware@t-online.de> wrote:
> Hi,
>
> while I recently updated an older machine to the latest Debian
> distribution which included updating the kernel from 2.4.x to 3.0 the
> tulip driver did stop working for my network card. The replacement
> driver de2104x did initialize the network interfaces but no transmission
> was possible.
Did you try the original de4x5.c driver? I believe it was all that existed
back in the 2.4 vintage, and I think it was kept around just to keep old
cards that didn't like the "new" tulip driver working.
Paul.
>
> Digging into it I found the de2104x driver just assumes there is no BNC
> transceiver on a card using the 21040 chipset. So I extracted the
> correct configuration values from the old tulip driver and removed some
> sanity checking which denied setting the transceiver to BNC. Now I can
> use the driver by just setting the correct transceiver using ethtool.
>
> A patch against 3.0 is appended. It should apply against more recent
> versions too since there was not the lot happening for this old driver,
> but for the relocation of the files from drivers/net/tulip to
> drivers/net/ethernet/dec/tulip.
>
>
> Michael
>
next prev parent reply other threads:[~2012-01-13 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 22:52 [PATCH] Making de2104x working with BNC connection on 21040 chipset Michael Mueller
2012-01-13 18:43 ` Paul Gortmaker [this message]
2012-01-13 21:30 ` Michael Mueller
2012-01-14 9:51 ` de4x5 (was Re: [PATCH] Making de2104x working with BNC connection on 21040 chipset) Michael Mueller
2012-01-14 17:55 ` de4x5 Michael Mueller
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='CAP=VYLpWbcBae11fcQPcuPmdfvir7N6F9QMdzXip=i4mMHjxsQ@mail.gmail.com' \
--to=paul.gortmaker@windriver.com \
--cc=malware@t-online.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).