Hello,
On Thu, May 18, 2000 at 06:05:59PM -0700, Dragan Stancevic wrote:
> From looking at the error messages that you are getting I second Andrey's
> mail, this is happening because the driver is experiencing problems when
> reading the eeprom and fails to detect you PHY. Unless you have no PHY :^)
>
> The driver has issues with reading the eeprom, it doesn't drive the
> eeprom serial clock correctly. By not following clock frequency
> specification it clocks data "into/out of" epprom incorrectly.
It may be some other problems...
Original Donald's driver worked with udelay(100) until Donald himself
replaced the udelay by a delay implemented as a single inw()!
The available Intel's driver uses udelay(100).
NetBSD uses udelay(1).
One of Intel's documents that's slipped the curtain of obscurity mentions
that EEPROM should work at the speed of at least 1us.
I've been given the access to a system with EEPROM reading problems, and
udelay(2) was quite sufficient and cured all problems.
So, if you Dragan have the timing specification, I would appreciate a small
patch fixing do_eeprom_cmd, or any other hint... :-)
But, in any case, I suspect that the timing is not the only problem of
Kamlesh.
Best regards
Andrey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:16 EST