More details on my Dark LED problem

Tue Sep 8 12:30:39 1998

I now have some more info about my state of darkness..... which should make
 enlightenment that much easier.

The card in question is a DFE500TX  Rev-C6  - a revision not even mentioned
 on the D-Link website..!

This has a 21140-AF chip

The FULL Duplex LED appears to be connected to pin 89 of the 21140, which
further appears to correspond to general purpose register bit gep7
in the gep7:0 set within CSR12 as detailed in the DEC Datasheet  at
http://developer.intel.com/design/network/new21/techdocs/21140ahm.pdf

The tulip-diag program gives the following:

[root@intranot tulip]# ./tulip-diag -f -e -e -a -m -m -v
tulip-diag.c:v1.05 8/28/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Index #1: Found a Digital DS21140 Tulip adapter at 0xd800.
Unknown PCI device ID bffffb4c.
Digital DS21140 Tulip Tulip chip registers at 0xd800:
  ffa04800 ffffffff ffffffff 00f9f028 00f9f228 fc660000 320e2202 ffffebef
  e0000000 fffd83ff ffffffff fffe0000 ffffff80 ffffffff 1c09fdc0 fffffec8
 The Rx process state is 'Waiting for packets'.
 The Tx process state is 'Idle'.
Transmit started, Receive started, full-duplex.
 The transmit threshold is 128.
 Port selection is MII, full-duplex.
EEPROM contents:
  1186 1100 0000 0000 0000 0000 0000 0000
  00d0 0103 8000 4cc8 ef09 1e00 0000 0800
  0100 018c 0000 0000 e078 0001 0050 0018
  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 9fe7
 ID CRC 0xd0 (vs. 0xd0), complete CRC 18063351.
EEPROM transceiver/media description for the Digital DS21140 Tulip chip.

Leaf node at offset 30, default media type 0800 (Autosense).
 CSR12 direction setting bits 00.
 1 transceiver description blocks:
  Media MII,  block type 1.
   MII interface PHY 0 (media type 11).
 MII PHY found at address 0, status 0x782d.
 MII PHY #0 transceiver registers:
   1000 782d 7810 0001 01e1 41a1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 4000 0000 38c8 0010 0000 0002
   0001 0000 0000 0000 0000 0000 0000 0000.
[root@intranot tulip]#

I note with sadness that the extra info which is apparent from various
system descriptions in the Tulip Database at
http://maximus.bmen.tulane.edu/~siekas/database/index.html is lacking from
this diagnostic output. In particular, some of the database
listings show

              MII PHY #0 transceiver registers:
               1100 782d 7810 0000 01e1 0081 0000 0000
               0000 0000 0000 0000 0000 0000 0000 0000
               0000 0000 4000 0000 28c8 0010 0000 0002
               0001 0000 0000 0000 0000 0000 0000 0000.
             Basic mode control register 0x1100: Auto-negotiation enabled.
             Basic mode status register 0x782d  782d.
              Link status: established.
               Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
              Able to perform Auto-negotiation, auto-negotiation complete.
             Vendor ID is 1e:04:00:--:--:--, model 0 rev. 0.
               I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD
10baseT
              Advertising no additional info pages.
               IEEE 802.3 CSMA/CD protocol.
               Link partner capability is 0081: 100baseTx.

This when running tulip-diag.c:v0.24 1/6/98 Donald Becker
(becker@cesdis.gsfc.nasa.gov)....

i.e. the diagnostic output shows the current intimate state of the
Autonegotiation.

What's worse, this code seems to have been entirely stripped from
tulip-diag.c - any ideas why?

But back to the Duplex LED... Given that D-link appears to be implementing
the Duplex LED function in software, how can one modify tulip.c to update
the LED at each media selection tick????

Ted Rule,

Flextech Television