New version of 'tulip-diag' available

[KOGAN_VADIM]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



> vadim-note:/home/vadim/pcmcia# ./tulip-diagn -ee   
> tulip-diag.c:v1.09 4/9/99 Donald Becker
(becker@cesdis.gsfc.nasa.gov)
> Index #1: Found a Digital DS21143 Tulip adapter at 0x400.
>  Port selection is 10mpbs-serial, half-duplex.
>  Transmit stopped, Receive stopped, half-duplex.
>   The Rx process state is 'Stopped'.
>   The Tx process state is 'Stopped'.
>   The transmit threshold is 72.
> EEPROM contents:
>   8086 0001 0087 0000 0000 0000 0000 0000
>   00c4 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 4448
>  ID CRC 0xc4 (vs. 0xc4), complete CRC eddd19c7.
>  A simplifed EEPROM data table was found.
>  The EEPROM does not contain transceiver control information.

Well... I looked around and figured that
a) this must be an empty EEPROM (CRC is Ok + I was unable to find
anything usable - not after this 128 bytes, not w/ 8 bit addressing)
b) As far as I understand, this kind of "totally empty, nothing but
the checksum" EEPROM is not documented anywhere. And there is probably
no info leafs at all. (I hope I'm wrong)
c) There is a DOS test program that all by itself is able to read info
from this card (not interesing) and (!) go into promisc mode and show
packets going on the net.
d) I understand that if there is nothing in the card, the driver has
to have kinda its own version of EEPROM for this card. So does this
little test program.
e) And now comes the real question - what if I get a disasm and try to
see what's happening? Can that help? Or that would be PITA to track?

Vadim.


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2

iQA/AwUBNxBHd4sB3WHoGn03EQL/7wCgkmhLwV1P6JOAcXtRirXJFGWXLmoAn0mh
zCX3/9Ljx7+lxOs0dbbIRiZV
=4B8P
-----END PGP SIGNATURE-----