Fri, 24 Nov 2000 15:01:03 +0100 (CET)
On Thu, 23 Nov 2000, Berkan Eskikaya wrote:
> > What if the driver gets the MII registers address wrong ?
> > So, can you try running 'mii-diag -p 24 eth1' ?
> We'll there is a definite change; mii-diag now reports link beat, but
> I still cannot ping anywhere.
> $ mii-diag -p 24 eth1
> Using the specified MII PHY index 24.
> Basic registers of MII PHY #24: 3000 7829 0041 6800 05e1 40a1 0007 2801.
Well, I somehow expected that. Page 147 of the documentation says:
"These auto-negotiation registers are accessed through the MII management
interface using a PHY address (PHYAD) of 11000b" = 24.
So on Tornado cards, the internal MII interface (which is always present
according to the docs) is always located at PHYAD = 24. I hope that this
is also true for CardBus devices.
In vortex_probe1(), if MII or NWAY is used, there is a search for the MII
interfaces (there can be more than 1). Why this search suddenly doesn't
work anymore, I don't know; Don, do you have any ideea ? Maybe the
preamble confuses the interface ? Maybe some more checks are needed before
saying "we have a valid MII interface at this PHYAD" ?
A workaround can be a test for IS_TORNADO and always add one interface
with PHYAD = 24, but this still leaves the other 2 (or 4 according to
vortex-diag output) MII interfaces detected. Now I don't understand
something: if there are several MII interfaces and they provide similar
capabilities, how is one of them selected as being the one in use ?
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868