From: John DeGood <nu3e@arrl.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Has anyone got a 2114x ethernet card working under 4th Edition?
Date: Mon, 8 Jul 2002 20:58:12 -0400 [thread overview]
Message-ID: <010901c226e3$b3f1dfc0$1b02a8c0@arnysm01.nj.comcast.net> (raw)
In-Reply-To: <005101c1fa80$94ab59a0$0100a8c0@landra.org>
> From: "Russ Cox" <rsc@plan9.bell-labs.com>
>
> What does
>
> pci
>
> print? The line I care about is the one
> where the second field begins 02., as in
> the three marked below.
I know this is an old thread, but I just ran into this problem today with an
SMC 9332DST card and thought my experience might help others. The broken
detection message was:
#l0: 2114x: 0 Mbps port 0xfc80 irq 10 c0f401000000
Note that the speed and EA are both bogus.
Here's the interesting part: I tried a newer variant of the card, an SMC
9332BDT, and it works perfectly with the 2114x driver.
The output from "pci" for *both* cards is identical:
0.15.0: 02.00.00 1011/0009 10 0:0000fc81 128 1:ffbefc00 128
The Tulip chips on the 2 cards have the following markings:
9332DST (doesn't work with 2114x driver): 21140 / DC1010BA / 21-40673-01
9332BDT (works with 2114x driver): 21140-AE / DC1064B / 21-43864-03
I suspect transceiver or EEPROM differences may be the significant driver
issue in the case of these 2 cards rather than the variant of Tulip chip.
FWIW, I note that Don Becker's Tulip driver for Linux has an entry in
"eeprom_fixups[]" for the (broken in Plan 9) 9332DST, while I don't see
anything similar in ether2114x.c
John
next prev parent reply other threads:[~2002-07-09 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 17:33 Russ Cox
2002-05-13 13:17 ` sdrthomas
2002-07-09 0:58 ` John DeGood [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 1:49 jmk
2002-05-12 17:05 Michael Warnock
2002-05-12 8:04 nigel
2002-05-12 7:34 sdrthomas
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='010901c226e3$b3f1dfc0$1b02a8c0@arnysm01.nj.comcast.net' \
--to=nu3e@arrl.net \
--cc=9fans@cse.psu.edu \
/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).