Hi Haavard Skinnemoen wrote: > On Fri, 22 Feb 2008 12:27:48 +0000 (GMT) > Michael Trimarchi <[EMAIL PROTECTED]> wrote: > > >> When I read to my id u-boot report 0xffff and fail, but >> the device works pretty well skipping this testing. >> If I remember linux report the same issue. >> > > Is the MII address of your PHY set correctly? > > All MII-capable PHYs should have a working PHYSID1 register. If it > doesn't, something is broken. > > So I think the CONFIG_GENERIC_PHY name is misleading -- the test is > generic enough as is. CONFIG_BROKEN_PHY would be better, if there's > really no way to get your PHY to behave. > > But note that if MDIO communication isn't working, autonegotiation > won't work, and the speed and duplex settings will most likely be > wrong. So I don't think simply #ifdefing out that sanity check is > really going to solve any problems. > > Yes I know but this is the situation:
- dm9161a - at91sam9260 When I try to read at phy id it reports 0xffff and linux too. I suppose that can be related to a broken phy. But seems to be broken on this read. I think that you have more experience, do you have an idea? Regards Michael ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
