Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

get_phy_id(9) [centos man page]

GET_PHY_ID(9)						      Network device support						     GET_PHY_ID(9)

NAME
get_phy_id - reads the specified addr for its ID. SYNOPSIS
int get_phy_id(struct mii_bus * bus, int addr, u32 * phy_id, bool is_c45, struct phy_c45_device_ids * c45_ids); ARGUMENTS
bus the target MII bus addr PHY address on the MII bus phy_id where to store the ID retrieved. is_c45 If true the PHY uses the 802.3 clause 45 protocol c45_ids where to store the c45 ID information. DESCRIPTION
In the case of a 802.3-c22 PHY, reads the ID registers of the PHY at addr on the bus, stores it in phy_id and returns zero on success. In the case of a 802.3-c45 PHY, get_phy_c45_ids is invoked, and its return value is in turn returned. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 GET_PHY_ID(9)

Check Out this Related Man Page

MII(4)							   BSD Kernel Interfaces Manual 						    MII(4)

NAME
mii -- IEEE 802.3 Media Independent Interface network bus SYNOPSIS
acphy* at mii? phy ? # Altima AC101 10/100 PHY amhphy* at mii? phy ? # AMD 79c901 PHY (10BASE-T part) bmtphy* at mii? phy ? # Broadcom BCM5201/5202 PHYs brgphy* at mii? phy ? # Broadcom BCM5400/5401 Gig-E PHYs ciphy* at mii? phy ? # Cicada CS8201 Gig-E PHYs dmphy* at mii? phy ? # Davicom DM9101 PHYs exphy* at mii? phy ? # 3Com internal PHYs gentbi* at mii? phy ? # Generic ten-bit 1000BASE-X PHYs glxtphy* at mii? phy ? # Level One LXT-1000 Gig-E PHYs gphyter* at mii? phy ? # NatSemi DP83861 Gig-E PHYs icsphy* at mii? phy ? # Integrated Circuit Systems ICS1890 PHYs ikphy* at mii? phy ? # Intel 82563 PHYs inphy* at mii? phy ? # Intel 82555 PHYs iophy* at mii? phy ? # Intel 82553 PHYs lxtphy* at mii? phy ? # Level One LXT-970 PHYs makphy* at mii? phy ? # Marvel 88E1000 Gig-E PHYs nsphy* at mii? phy ? # NatSemi DP83840 PHYs nsphyter* at mii? phy ? # NatSemi DP83843/DP83815 PHYs pnaphy* at mii? phy ? # Generic HomePNA PHYs qsphy* at mii? phy ? # Quality Semiconductor QS6612 PHYs rgephy* at mii? phy ? # Realtek 8169S/8110S internal PHYs rlphy* at mii? phy ? # Realtek 8139/8201L PHYs sqphy* at mii? phy ? # Seeq 80220/80221/80223/80225 PHYs tlphy* at mii? phy ? # ThunderLAN internal PHYs tqphy* at mii? phy ? # TSC Semiconductor 78Q2120 PHYs ukphy* at mii? phy ? # Generic/unknown PHYs urlphy* at mii? phy ? # Realtek RTL8150L internal PHYs options MIIVERBOSE DESCRIPTION
Media Independent Interface is an IEEE standard serial bus for connecting MACs (network controllers) to PHYs (physical media interfaces). The mii layer allows network device drivers to share support code for various PHY models, and allows unused support for PHYs which are not present in a system to be removed from the kernel. Network device drivers which use the mii layer carry the ``mii'' autoconfiguration attribute. This allows kernel configuration files to sim- ply specify PHYs as described above in the synopsis. The following is an example of the messages displayed when a network interface with an attached PHY is detected by the kernel: epic0 at pci0 dev 12 function 0: SMC EPIC/100 Fast Ethernet epic0: interrupting at kn20aa irq 4 epic0: SMC9432TX, Ethernet address 00:e0:29:07:17:c4 qsphy0 at epic0 phy 3: QS6612 10/100 media interface, rev. 1 qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto All PHY drivers display the media types supported by the PHY when it is detected by the kernel. These media types are valid media keywords for use with the ifconfig(8) program. SEE ALSO
acphy(4), amhphy(4), bmtphy(4), brgphy(4), ciphy(4), dmphy(4), exphy(4), gentbi(4), glxtphy(4), gphyter(4), icsphy(4), ifmedia(4), ikphy(4), inphy(4), iophy(4), lxtphy(4), makphy(4), nsphy(4), nsphyter(4), pnaphy(4), qsphy(4), rgephy(4), rlphy(4), sqphy(4), tlphy(4), tqphy(4), ukphy(4), urlphy(4), ifconfig(8) The OUI assignments list can be found at: http://standards.ieee.org/regauth/oui/index.shtml BSD
October 13, 2006 BSD
Man Page