From: Michael Mueller <malware@t-online.de>
To: netdev@vger.kernel.org
Subject: Re: [PATCH] Making de2104x working with BNC connection on 21040 chipset
Date: Fri, 13 Jan 2012 22:30:47 +0100 [thread overview]
Message-ID: <4F10A287.2070008@t-online.de> (raw)
In-Reply-To: <CAP=VYLpWbcBae11fcQPcuPmdfvir7N6F9QMdzXip=i4mMHjxsQ@mail.gmail.com>
Hi Paul,
you wrote [copy to you]:
>> 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.
In 2.4.x the tulip driver was present and did work for me when selecting
the transceiver by module parameter.
The original de4x5 does not exist in 3.0. The comments at the top of
de2104x.c suggest it had been consolidated into this one. The de2104x
driver is the one autoloaded due to the PCI id of the device, see bottom
for lspci output. So it seems to be the obvious candidate to get
running. Selecting the transceiver using ethtool might to be sufficient
for this corner case. Otherwise the media auto dectection sheme would
have to be changed too which may cause trouble to users of the currently
about exclusively used twisted pair cabling. The way I solved the
problem I see no harm taken.
When trying the de4x5 using 2.6.32 - which is what I can boot into
without too much problems - it did lock the machine while starting the
interface (ifconfig up). Sorry, but I do not feel like digging into this
just now.
A comment in the de4x5 driver source suggest that for the 21040 chipset
it is a choice of the board maker to connect a BNC, an AUI port or both
selectable by jumper. Mine has no AUI, probably because two of them
would not fit onto the slot plate together with 2 TP ports while there
is enough space for 2 TP and 2 BNC.
Michael
00:11.0 0604: 1011:0001 (rev 02) (prog-if 00 [Normal decode])
Flags: bus master, medium devsel, latency 64
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 00009000-00009fff
Memory behind bridge: cfe00000-cfefffff
Prefetchable memory behind bridge: cdb00000-cdbfffff
[AGP left out]
02:04.0 0200: 1011:0002 (rev 23)
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 9c00 [size=128]
Memory at cfefff80 (32-bit, non-prefetchable) [size=128]
Kernel driver in use: de2104x
02:05.0 0200: 1011:0002 (rev 23)
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 9800 [size=128]
Memory at cfefff00 (32-bit, non-prefetchable) [size=128]
Kernel driver in use: de2104x
next prev parent reply other threads:[~2012-01-13 21:31 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
2012-01-13 21:30 ` Michael Mueller [this message]
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=4F10A287.2070008@t-online.de \
--to=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).