1.\" $NetBSD: mii.4,v 1.14 2002/04/02 20:45:40 augustss Exp $ 2.\" 3.\" Copyright (c) 1998 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, 8.\" NASA Ames Research Center. 9.\" 10.\" Redistribution and use in source and binary forms, with or without 11.\" modification, are permitted provided that the following conditions 12.\" are met: 13.\" 1. Redistributions of source code must retain the above copyright 14.\" notice, this list of conditions and the following disclaimer. 15.\" 2. Redistributions in binary form must reproduce the above copyright 16.\" notice, this list of conditions and the following disclaimer in the 17.\" documentation and/or other materials provided with the distribution. 18.\" 3. All advertising materials mentioning features or use of this software 19.\" must display the following acknowledgement: 20.\" This product includes software developed by the NetBSD 21.\" Foundation, Inc. and its contributors. 22.\" 4. Neither the name of The NetBSD Foundation nor the names of its 23.\" contributors may be used to endorse or promote products derived 24.\" from this software without specific prior written permission. 25.\" 26.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 27.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 28.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 29.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 30.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 31.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 32.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 33.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 34.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 35.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 36.\" POSSIBILITY OF SUCH DAMAGE. 37.\" 38.Dd November 3, 1998 39.Dt MII 4 40.Os 41.Sh NAME 42.Nm mii 43.Nd IEEE 802.3 Media Independent Interface network bus 44.Sh SYNOPSIS 45.Cd "acphy* at mii? phy ? # Altima AC101 10/100 PHY" 46.Cd "amhphy* at mii? phy ? # AMD 79c901 PHY (10BASE-T part)" 47.Cd "bmtphy* at mii? phy ? # Broadcom BCM5201/5202 PHYs" 48.Cd "brgphy* at mii? phy ? # Broadcom BCM5400/5401 Gig-E PHYs" 49.Cd "dmphy* at mii? phy ? # Davicom DM9101 PHYs" 50.Cd "exphy* at mii? phy ? # 3Com internal PHYs" 51.Cd "gentbi* at mii? phy ? # Generic ten-bit 1000BASE-X PHYs" 52.Cd "glxtphy* at mii? phy ? # Level One LXT-1000 Gig-E PHYs" 53.Cd "gphyter* at mii? phy ? # NatSemi DP83861 Gig-E PHYs" 54.Cd "icsphy* at mii? phy ? # Integrated Circuit Systems ICS1890 PHYs" 55.Cd "inphy* at mii? phy ? # Intel 82555 PHYs" 56.Cd "iophy* at mii? phy ? # Intel 82553 PHYs" 57.Cd "lxtphy* at mii? phy ? # Level One LXT-970 PHYs" 58.Cd "makphy* at mii? phy ? # Marvel 88E1000 Gig-E PHYs" 59.Cd "nsphy* at mii? phy ? # NatSemi DP83840 PHYs" 60.Cd "nsphyter* at mii? phy ? # NatSemi DP83843/DP83815 PHYs" 61.Cd "pnaphy* at mii? phy ? # Generic HomePNA PHYs" 62.Cd "qsphy* at mii? phy ? # Quality Semiconductor QS6612 PHYs" 63.Cd "sqphy* at mii? phy ? # Seeq 80220/80221/80223/80225 PHYs" 64.Cd "tlphy* at mii? phy ? # ThunderLAN internal PHYs" 65.Cd "tqphy* at mii? phy ? # TSC Semiconductor 78Q2120 PHYs" 66.Cd "ukphy* at mii? phy ? # Generic/unknown PHYs" 67.Cd "urlphy* at mii? phy ? # Realtek RTL8150L internal PHYs" 68.Sh DESCRIPTION 69Media Independent Interface is an IEEE standard serial bus for 70connecting MACs (network controllers) to PHYs (physical media 71interfaces). The 72.Nm 73layer allows network device drivers to share support code for 74various PHY models, and allows unused support for PHYs which 75are not present in a system to be removed from the kernel. 76.Pp 77Network device drivers which use the 78.Nm 79layer carry the 80.Dq mii 81autoconfiguration attribute. This allows kernel configuration 82files to simply specify PHYs as described above in the synopsis. 83.Pp 84The following is an example of the messages displayed when a network 85interface with an attached PHY is detected by the kernel: 86.Bd -literal -offset indent 87epic0 at pci0 dev 12 function 0: SMC EPIC/100 Fast Ethernet 88epic0: interrupting at kn20aa irq 4 89epic0: SMC9432TX, Ethernet address 00:e0:29:07:17:c4 90qsphy0 at epic0 phy 3: QS6612 10/100 media interface, rev. 1 91qsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto 92.Ed 93.Pp 94All PHY drivers display the media types supported by the PHY when it 95is detected by the kernel. These media types are valid media keywords 96for use with the 97.Xr ifconfig 8 98program. 99.Sh SEE ALSO 100.Xr acphy 4 , 101.Xr amhphy 4 , 102.Xr bmtphy 4 , 103.Xr brgphy 4 , 104.Xr dmphy 4 , 105.Xr exphy 4 , 106.Xr gentbi 4 , 107.Xr glxtphy 4 , 108.Xr gphyter 4 , 109.Xr icsphy 4 , 110.Xr ifmedia 4 , 111.Xr inphy 4 , 112.Xr intro 4 , 113.Xr iophy 4 , 114.Xr lxtphy 4 , 115.Xr makphy 4 , 116.Xr nsphy 4 , 117.Xr nsphyter 4 , 118.Xr pnaphy 4 , 119.Xr qsphy 4 , 120.Xr sqphy 4 , 121.Xr tlphy 4 , 122.Xr tqphy 4 , 123.Xr ukphy 4 , 124.Xr urlphy 4 , 125.Xr ifconfig 8 126