FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F7 2011-09-11T20:25:57Z 2011-09-11T20:25:57Z Marius Strobl marius@FreeBSD.org 2011-09-11T20:25:57Z urn:sha1:99e4ce3e7b07bcdeca71fdffa04401cb54e795aa - Let mii_phy_add_media() also announce the support of IFM_NONE. - Add a PHY-specific reset routine is for lxtphy(4) which disables MII interrupts. - Remove redundant checks in NIC drivers for mii->mii_instance not being zero before calling the reset routines because as soon as one PHY driver attaches mii->mii_instance is incremented and we hardly can end up in their media change callbacks etc if no PHY driver has attached as mii_attach() would have failed in that case and not attach a miibus(4) instance. - Convert the mebers of the MII data structure to unsigned where appropriate. This is partly inspired by NetBSD/OpenBSD. - Add MIIF_NOMANPAUSE and mii_phy_flowstatus() calls to drivers that weren't explicitly converted to support flow control before. It's unclear whether flow control actually works with these but typically it should and their net behavior should be more correct with these changes in place than without if the MAC driver sets MIIF_DOPAUSE. Obtained from: NetBSD (partially) 2011-01-21T00:53:37Z Marius Strobl marius@FreeBSD.org 2011-01-21T00:53:37Z urn:sha1:87493022c00a4a86ed6c4012de9fb27e4a8f2f51 - Even after masking the media with IFM_GMASK the result may have bits besides the duplex ones set so just comparing it with IFM_FDX may lead to false negatives. - Just let the default case handle all unsupported media types. - In pnphy_status() don't unnecessarily read a register twice. - Remove unnused macros. 2010-10-24T13:42:03Z Marius Strobl marius@FreeBSD.org 2010-10-24T13:42:03Z urn:sha1:afe353da1ec684bab95b0a511a55fce03e1ea626 Consistently always explicitly set IFM_HDX for half-duplex. Obtained from: OpenBSD (mostly) 2010-10-24T13:39:26Z Marius Strobl marius@FreeBSD.org 2010-10-24T13:39:26Z urn:sha1:079faf2109d575402f4ab1ac8c90b173bdbbbf24 - In the spirit of previous simplifications factor out the checks for a different PHY instance being selected and isolation out into the wrappers around the service methods rather than duplicating them over and over again (besides, a PHY driver shouldn't need to care about which instance it actually is). - Centralize the check for the need to isolate a non-zero PHY instance not supporting isolation in mii_mediachg() and just ignore it rather than panicing, which should sufficient given that a) things are likely to just work anyway if one doesn't plug in more than one port at a time and b) refusing to attach in this case just leaves us in a unknown but most likely also not exactly correct configuration (besides several drivers setting MIIF_NOISOLATE didn't care about these anyway, probably due to setting this flag for no real reason). - Minor fixes like removing unnecessary setting of sc->mii_anegticks, using sc->mii_anegticks instead of hardcoded values etc. 2010-10-17T12:30:01Z Marius Strobl marius@FreeBSD.org 2010-10-17T12:30:01Z urn:sha1:127507f415ca1b93e01b87bef2934c34b2118d59 Use the mii_data provided via mii_attach_args and mii_pdata respectively instead of reaching out for the softc of the parent. 2009-03-22T22:08:30Z Marius Strobl marius@FreeBSD.org 2009-03-22T22:08:30Z urn:sha1:23027986a5dff811a6be8e1276cd29725a03d14c - Set MIIF_NOLOOP and don't add IFM_LOOP as loopback apparently isn't supported with these pseudo-PHYs. The MIIF_NOLOOP flag currently triggers nothing but hopefully will be respected by mii_phy_setmedia() later on. - Don't add IFM_NONE as isolation isn't supported by these pseudo-PHYs. - Use mii_phy_add_media() instead of mii_add_media() so the latter can be eventually retired. 2009-03-19T15:16:05Z Marius Strobl marius@FreeBSD.org 2009-03-19T15:16:05Z urn:sha1:f6dc6d1b8b98248ab410e605b398b230421ea0e6 cosmetic changes and style fixes 2008-02-03T04:12:06Z Pyun YongHyeon yongari@FreeBSD.org 2008-02-03T04:12:06Z urn:sha1:97096c313d42d07b4ca1d5b14f99afa1cfcf303b IEEE 802.3 Annex 28B.3 explicitly specifies the following relative priorities of the technologies supported by 802.3 Selector Field value. 1000BASE-T full duplex 1000BASE-T 100BASE-T2 full duplex 100BASE-TX full duplex 100BASE-T2 100BASE-T4 100BASE-TX 10BASE-T full duplex 10BAST-T However PHY drivers didn't honor the order such that 100BASE-T4 had higher priority than 100BASE-TX full duplex. Fix that long standing bugs such that have PHY drivers choose the highest common denominator ability. Fix a bug in dcphy which inadvertently aceepts 100BASE-T4. PR: 92599 2006-08-02T05:28:52Z Pyun YongHyeon yongari@FreeBSD.org 2006-08-02T05:28:52Z urn:sha1:07c4a8dfa6cf0eba07eb281b96db66f0f3faf8b5 (BUS_PROBE_DEFAULT, BUS_PROBE_GENERIC etc). These pseudo PHY drivers were forgotten from the conversion due to the repo copy to dc driver location. 2006-06-03T20:37:56Z John Baldwin jhb@FreeBSD.org 2006-06-03T20:37:56Z urn:sha1:344823993bf31d22dc1a4bccb3b6cc20c7e10781 get the subvendor device id.