MX Chipset

[Hiroki Minematu]

Dear Developers

 I'm now under developing for FreeBSD-2.2.7 about MX98713, MX98715
and LC82C169 chips. Of course, for Linux, it is in planning stage.
 Last, I was running patched tulip-diag and get result this.
 MX98713 board (HE-32 MX) have MX98702, MX98704 PHY chips, and
no MII. So, tulip.c 0.89K successfully found this board, but
didn't run.
 MX98715 board (HE-32 PLUS) was only detect by same driver code.

# I wonder, why vender ID is 0000? So, I forced that to set '0x10d9'
# into internal 'vendor_id' variable. :-)
------------------
[root@methan /root]# ./tulip-diag -p e400 -aeD
tulip-diag.c:v1.05 8/28/98 Donald Becker (becker@cesdis.gsfc.nasa.gov)
vendor ID = 0000
Digital DC21040 Tulip Tulip chip registers at 0xe400:
  fff84800 ffffffff ffffffff 00fff028 00fff228 fc205510 38600000 fffe5410
  fffe0000 fff0dff0 ffffffff fffe0000 fffffeff ffffffff 1c09fdc0 fffffec8
 The Rx process state is 'Stopped'.
 The Tx process state is 'Waiting for Tx to finish'.
Transmit stopped, Receive stopped, half-duplex.
 The transmit unit is set to store-and-forward.
 Port selection is 10mpbs-serial, half-duplex.
EEPROM contents:
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 e000 1125 e600 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
  0014 0100 0000 0000 0000 0512 10d9 a5f0
 ID CRC 0xe3 (vs. 00), complete CRC f05a400d.
 A simplifed EEPROM data table was found.
 The EEPROM does not contain transceiver control information.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Nicholas Edwards wrote:
>A few weeks ago, there was some correspondance with a Mr. Chen from
>Macronix in regard to better supporting the EEPROM and media selection for
>his company's clone of the Tulip chip. 
>
>I was wondering if there are any patches yet available that incorporate
>this new information, if it was at all helpful.

------------------------+
minematu@aimcom.co.jp   |