Any Workaround For Non-Standard SROM?

[Don Gray]

At 01:47 AM 11/7/98 -0500, Donald Becker wrote:
>On Fri, 6 Nov 1998, Don Gray wrote:
>
>> I've been trying to get my Compex FL-100Tx PCI card to work w/ Linux for
>> a long, long time and just haven't had any success.  It has a DEC 21143
>> chip; the MII address is listed as '0' which I know is not supposed to
>
>What does the detection message report?
>
>What does 'tulip-diag -e -e' report?
>What does 'tulip-diag -f -a -m' report while the card is running?
>
>   http://cesdis.gsfc.nasa.gov/linux/diag/index.html
>

Manually inserting the tulip driver with options=11 produces the following
detection message:

Found Digital DS21143 Tulip at PCI I/O address 0xe400.
tulip.c:v0.90 10/20/98 becker@cesdis.gsfc.nasa.gov
eth0: Digital DS21143 Tulip at 0xe400, 00 80 48 e7 0f 25, IRQ 9.
read_eeprom:
11f6 0113 0000 0000 0000 0000 0000 0000
0003 0103 8000 e748 250f 1e00 0000 0800
8c03 4002 ec01 7f3f 0008 08ab 0001 028c
0144 3dec 087f ab00 0108 9100 0003 ab02
0108 0000 6000 01e0 5000 0180 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0001 0000 0000 0000 0000 0000 3c0b
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2)
block.
eth0:  MII interface PHY 0, setup/reset sequences 2/0 long, capabilities 00 01.
eth0:  Index #2 - Media MII (#11) described by a 21142 MII PHY (3) block.
eth0:  MII transceiver #0 config 3100 status 782d advertising 0001.
eth0:  Advertising 01e1 on PHY 0, previously advertising 0001.
-------------------------------------

tulip-diag -e -e produces:

tulip-diag.c:v1.06 9/18/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0xe400.
EEPROM contents:
  11f6 0113 0000 0000 0000 0000 0000 0000
  0003 0103 8000 e748 250f 1e00 0000 0800
  8c03 4002 ec01 7f3f 0008 08ab 0001 028c
  0144 3dec 087f ab00 0108 9100 0003 ab02
  0108 0000 6000 01e0 5000 0180 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0001 0000 0000 0000 0000 0000 3c0b
 ID CRC 0x03 (vs. 0x03), complete CRC 2fc342a1.
EEPROM transceiver/media description for the Digital DS21143 Tulip chip.

Leaf node at offset 30, default media type 0800 (Autosense).
 3 transceiver description blocks:
  Media 10baseT,  block type 2.
   Serial transceiver for 10baseT (media type 64).
    CSR13 ec01  CSR14 7f3f  CSR15 0008.
    GP pin direction 08ab  GP pin data 0001.
  Media 10baseT-Full Duplex,  block type 2.
   Serial transceiver for 10baseT-Full Duplex (media type 68).
    CSR13 ec01  CSR14 7f3d  CSR15 0008.
    GP pin direction 08ab  GP pin data 0001.
  Media MII,  block type 3.
   MII interface PHY 0 (media type 11).
 MII PHY found at address 0, status 0x782d.
---------------------------------------------------------------

tulip-diag -f -a -m (while running) produces:

tulip-diag.c:v1.06 9/18/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21143 Tulip adapter at 0xe400.
Digital DS21143 Tulip Tulip chip registers at 0xe400:
  ffa04800 ffffffff ffffffff 00fff820 00fffa20 f0660000 320e2002 fbfffbff
  e0000000 fffd83ff ffffffff fffe0000 000000c6 ffff0000 ffffffff 8ff50000
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Idle'.
Transmit started, Receive started, half-duplex.
 The transmit threshold is 128.
 Port selection is MII, half-duplex.
 MII PHY found at address 0, status 0x782d.
  Internal autonegotiation state is 'Autonegotiation disabled'.
----------------------------------------------------

I hope this is helpful.  Thank you for your quick reply.  The board has a
Digital chip with the number 21143-PA (dated 1996) [if this is meaningful].
 It is wired with a crossover to a 10baseT ne2k clone.  Tried it through a
hub, but same results.  Pinging produces nothing; sometimes 'eth0 transmit
timeout'.

Don Gray