[tulip-bug] Problem with Xircom Realport 10/100 Cardbus adapter
Hidvegi
hzoli@austin.ibm.com
Sat, 12 Aug 2000 18:40:55 -0500 (CDT)
This adapter does not work with the latest tulip.c driver, but it
works with the driver in pcmcia_cs, which has a copy of tulip_cb.c,
which apparently has some modifications for Xircom cards. Is it
possible, to merge things together?
Here is the tulip-debug output from the card:
# ~/tulip/tulip-diag -t 4 -p 0x280
-f -mm -ee -aa
tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Assuming a Digital DS21143 Tulip adapter at 0x280.
Digital DS21143 Tulip chip registers at 0x280:
fea08000 ffffffff ffffffff 00695810 00695a10 60660000 324c2002 ebffe1e7
e0000000 fffc8384 00000000 fffe0000 000000c4 ffff0000 ffffffff a80f0000
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 72.
The NWay status register is 000000c4.
EEPROM size is 6.
* An old-style EEPROM layout was found.
* The old-style layout does not contain transceiver control information.
* This board may not work, or may work only with a subset of transceiver
* options or data rates.
EEPROM contents:
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
ID block CRC 0xe3 (vs. 00).
Full contents CRC 0x6523 (read as 0x0000).
MII PHY found at address 0, status 0x783d.
MII PHY #0 transceiver registers:
3100 782d 0300 e54a 01e1 41e1 000b 0000
0000 0000 0000 0000 0000 0000 0000 0000
0140 002f 0e00 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000.
Internal autonegotiation state is 'Autonegotiation disabled'.
Thanks,
Zoli