Date: Wed, 2 Apr 2008 09:36:46 -0700 From: Marcel Moolenaar <xcllnt@mac.com> To: Nathan Whitehorn <nathanw@uchicago.edu> Cc: freebsd-ppc@freebsd.org Subject: Re: BMAC Ethernet Driver Message-ID: <C83E8810-B68B-49B5-A7F4-8B72A4FFFFDA@mac.com> In-Reply-To: <47F39EF4.8040800@uchicago.edu> References: <47E06B23.7060400@uchicago.edu> <20080325023040.ab0daa19.stas@FreeBSD.org> <47E8527B.2050002@uchicago.edu> <47F39EF4.8040800@uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 2, 2008, at 7:57 AM, Nathan Whitehorn wrote: > I've refreshed the BMAC tarball at http://home.physics.wisc.edu/~nwhitehorn/bm.tgz > . > > It supports multicast and full-duplex operation now, the code is a > little more style(9) compliant, and I don't think I have anything > left to do unless someone finds some bugs. The patch to macio is > also now included in the tarball. > > To support full-duplex operation, I had to do a hack to reset > autonegotiation on the PHY (firmware puts the PHY in a weird state > where its registers claim it did autonegotiation, but it always ends > up in half-duplex mode). This is done in this way: > > sc->sc_mii = device_get_softc(sc->sc_miibus); > LIST_FOREACH(child, &sc->sc_mii->mii_phys, mii_list) { > mii_phy_auto(child); > } > > Is a better course to modify lxtphy's attach routine to do this > there? Or should this stay in bm? I lean towards putting it in the PHY driver itself. I expect a PHY reset to do the right thing and in this case it doesn't seem to do that. From what you say it seems that the driver is commitable at this time. I can't test it, but I can definitely commit. Just let me know... -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C83E8810-B68B-49B5-A7F4-8B72A4FFFFDA>