Date: Thu, 24 Sep 2009 22:39:18 +0200 From: Kristof Provost <kristof@sigsegv.be> To: Pyun YongHyeon <pyunyh@gmail.com> Cc: current@freebsd.org Subject: Re: mge, mii/e1000phy Message-ID: <20090924203918.GI19069@nereid> In-Reply-To: <20090923214011.GE1099@michelle.cdnetworks.com> References: <20090922211012.GE19069@nereid> <20090922235350.GB1520@michelle.cdnetworks.com> <20090923184149.GF19069@nereid> <20090923202448.GD1099@michelle.cdnetworks.com> <20090923205535.GG19069@nereid> <20090923214011.GE1099@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-09-23 14:40:11 (-0700), Pyun YongHyeon <pyunyh@gmail.com> wrote: > Oh, this question may not be related with your link issue. I wanted > to know why mge(4) had to check media type in its ioctl handler. > The advertised capability has nothing to do with link partner's > capability. The advertised capability is used in auto-negotiation > process and the PHY will choose the highest common denominator > capability. So if we want to disable 1000baseT/half-duplex for > whatever reason, it can be achieved by not advertising 1000baseT/ > half-duplex capability to mii layer. > I think it's advertising the following: 10baseT 10baseT-FDX 100baseTX 100baseTX-FDX 1000baseT 1000baseT-FDX auto In any case, the values used during mii_phy_add_media are sc->mii_capabilities 0x7949 and sc->mii_extcapabilities 0x3000. Regards, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090924203918.GI19069>