Date: Tue, 19 Jan 2010 11:37:43 -0800 From: Pyun YongHyeon <pyunyh@gmail.com> To: Oliver Fromme <olli@lurza.secnetix.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: bce(4) on IBM BladeCenter HS22 Message-ID: <20100119193743.GC6201@michelle.cdnetworks.com> In-Reply-To: <201001191923.o0JJNDPM064136@lurza.secnetix.de> References: <20100119181518.GA6201@michelle.cdnetworks.com> <201001191923.o0JJNDPM064136@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 19, 2010 at 08:23:13PM +0100, Oliver Fromme wrote: > Pyun YongHyeon <pyunyh@gmail.com> wrote: > > Thanks for the detailed information. I vaguely guess bce(4) used > > wrong PHY address for controller. How about attached patch? > > The patch just reset the PHY address to 1, it's not correct way to > > set it but just wants to know whether brgphy(4) is attached to the > > PHY. > > Unfortunately, it produces almost the same output, > except the registers now read 0xffff instead of 0x0000: > :-( Ok, could you remove the safety belt of bce_miibus_read_reg() to allow accessing all PHY address? You can comment out sc->bce_phy_addr check in bce_miibus_read_reg() to allow mii_phy_probe try to read all 32 possible PHY addresses. Does mii(4) probe manage to read something?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100119193743.GC6201>