Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

phy(4) [netbsd 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

Check Out this Related Man Page

DE(4)							   BSD Kernel Interfaces Manual 						     DE(4)

NAME
de -- DECchip 21040, 21140, 21141, 21142, and 21143 PCI Ethernet interface driver SYNOPSIS
de* at pci? dev ? function ? Configuration of PHYs may also be necessary. See mii(4). DESCRIPTION
The de driver supports Ethernet and Fast Ethernet interfaces based on the Digital Equipment Corporation DECchip 21040, 21140, 21141, 21142, and 21143 model controllers for PCI bus. 21040 10BASE-T and AUI/BNC 21140 10BASE-T and 100BASE-TX 21141 10BASE-T and 100BASE-TX 21142 10BASE-T and 100BASE-TX 21143 10BASE-T and 100BASE-TX Supported Network Interface Cards (NIC) include, but are not limited to: Accton EN1207i Cogent EM100 Asante AsanteFAST DEC DE435 DEC DE450 DEC DE500 SMC 9332 Znyx NetBlaster ZX340 series (345, 348, 346) Generally, if the NIC is for PCI bus, and the major controller chip has the DIGITAL logo on it, with one of the model numbers above, the de driver should recognize and control it. Beware, however, that many NIC manufacturers change the Ethernet controller chip without changing the product model number, and a physical inspection of the NIC, or a probe of the NIC with a PCI diagnostic tool is the only way to tell if a real DEC TULIP controller is present. Multi-port interfaces are typically configured as a PCI-PCI bridge with multiple de instances on the PCI bus on the other side of the bridge. DEC sold its semiconductor division to Intel. In addition, there are many "knock-offs" of the DEC TULIP Ethernet controller chips; NICs based on these chips are handled by the tlp(4) driver. This de driver should not be confused with the NetBSD VAX de driver for the DEC DEUNA/DELUA Ethernet controller for UniBus. SEE ALSO
ifmedia(4), intro(4), mii(4), pci(4), tlp(4), ifconfig(8) http://www.adaptec.com/, http://www.asante.com/, http://www.smc.com/, http://www.znyx.com/ HISTORY
The de driver first appeared in NetBSD 1.1 AUTHORS
Matt Thomas <matt@3am-software.com>. BSD
February 11, 2000 BSD
Man Page