Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Media-independent interface
open-in-new
<h2 id="standard-mii">Standard MII</h2> <p>The standard MII features a small set of registers:<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a>: Section 22.2.4 "Management functions" </p> <ul><li>Basic Mode Configuration (#0)</li> <li>Status Word (#1)</li> <li>PHY Identifier (#2, #3)</li> <li>Auto-Negotiation Advertisement (#4)</li> <li>Auto-Negotiation Link Partner Base Page Ability (#5)</li> <li>Auto-Negotiation Expansion (#6)</li> <li>Auto-Negotiation Next Page Transmit (#7)</li> <li>Auto-Negotiation Link Partner Received Next Page (#8)</li> <li>MASTER-SLAVE Control Register (#9)</li> <li>MASTER-SLAVE Status Register (#10)</li> <li>PSE Control register (#11)</li> <li>PSE Status register (#12)</li> <li>MMD Access Control Register (#13)</li> <li>MMD Access Address Data Register (#14)</li></ul> <p>Register #15 is reserved; registers #16 through #31 are vendor-specific. The registers are used to configure the device and to query the current operating mode. </p><p>The MII Status Word is the most useful datum, since it may be used to detect whether an <a href="/facts/Ethernet_NIC/wyf5FR29">Ethernet NIC</a> is connected to a network. It contains a <a href="/facts/Bit_field/fWgTjqvX">bit field</a> with the following information:<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a>: Section 22.2.4.2.2 "100BASE-X full duplex ability" </p> <table><tbody><tr><th>Bit value</th><th>Meaning</th></tr><tr><td>0x8000</td><td>Capable of <a href="/facts/100BASE-T4/YM5HjX0C">100BASE-T4</a></td></tr><tr><td>0x6000</td><td>Capable of <a href="/facts/100BASE-TX/YM5HjX0C">100BASE-TX</a> full/half duplex</td></tr><tr><td>0x1800</td><td>Capable of <a href="/facts/Classic_Ethernet/EQCN6yqx">10BASE-T</a> full/half duplex</td></tr><tr><td>0x0600</td><td>Capable of <a href="/facts/100BASE-T2/YM5HjX0C">100BASE-T2</a> full/half duplex</td></tr><tr><td>0x0100</td><td>Extended status (<a href="/facts/Gigabit_Ethernet/1ItIoV2w">Gigabit Ethernet</a>) register exists</td></tr><tr><td>0x0080</td><td>Capable of unidirectional operation</td></tr><tr><td>0x0040</td><td>Management frame preamble suppression permitted</td></tr><tr><td>0x0020</td><td><a href="/facts/Autonegotiation/dHFQJDEs">Autonegotiation</a> complete</td></tr><tr><td>0x0010</td><td>Remote fault</td></tr><tr><td>0x0008</td><td>Capable of Autonegotiation</td></tr><tr><td>0x0004</td><td>Link established</td></tr><tr><td>0x0002</td><td><a href="/facts/Jabber_(networking)/nMfhU8tU">Jabber</a> detected</td></tr><tr><td>0x0001</td><td>Extended MII registers exist</td></tr></tbody></table> <h3>Transmitter signals</h3> <table><tbody><tr><th>Signal name</th><th>Description</th><th>Direction</th></tr><tr><td>TX_CLK</td><td>Transmit clock</td><td>PHY to MAC</td></tr><tr><td>TXD0</td><td>Transmit data bit 0 (transmitted first)</td><td>MAC to PHY</td></tr><tr><td>TXD1</td><td>Transmit data bit 1</td><td>MAC to PHY</td></tr><tr><td>TXD2</td><td>Transmit data bit 2</td><td>MAC to PHY</td></tr><tr><td>TXD3</td><td>Transmit data bit 3</td><td>MAC to PHY</td></tr><tr><td>TX_EN</td><td>Transmit enable</td><td>MAC to PHY</td></tr><tr><td>TX_ER</td><td>Transmit error (optional)</td><td>MAC to PHY</td></tr></tbody></table> <p>The transmit clock is a free-running clock generated by the PHY based on the link speed (25 MHz for 100 Mbit/s, 2.5 MHz for 10 Mbit/s). The remaining transmit signals are driven by the MAC synchronously on the rising edge of TX_CLK. This arrangement allows the MAC to operate without having to be aware of the link speed. The transmit enable signal is held high during frame transmission and low when the transmitter is idle. </p><p>Transmit error may be raised for one or more clock periods during frame transmission to request the PHY to deliberately corrupt the frame in some visible way that precludes it from being received as valid. This may be used to abort a frame when some problem is detected after transmission has already started. The MAC may omit the signal if it has no use for this functionality, in which case the signal should be tied low for the PHY. </p><p>More recently, raising transmit error <i>outside</i> frame transmission is used to indicate the transmit data lines are being used for special-purpose signalling. Specifically, the data value 0b0001 (held continuously with TX_EN low and TX_ER high) is used to request an <a href="/facts/Energy-Efficient_Ethernet/a2BDt7Cz">EEE</a>-capable PHY to enter low power mode. </p> <h3>Receiver signals</h3> <table><tbody><tr><th>Signal name</th><th>Description</th><th>Direction</th></tr><tr><td>RX_CLK</td><td>Receive clock</td><td>PHY to MAC</td></tr><tr><td>RXD0</td><td>Receive data bit 0 (received first)</td><td>PHY to MAC</td></tr><tr><td>RXD1</td><td>Receive data bit 1</td><td>PHY to MAC</td></tr><tr><td>RXD2</td><td>Receive data bit 2</td><td>PHY to MAC</td></tr><tr><td>RXD3</td><td>Receive data bit 3</td><td>PHY to MAC</td></tr><tr><td>RX_DV</td><td>Receive data valid</td><td>PHY to MAC</td></tr><tr><td>RX_ER</td><td>Receive error</td><td>PHY to MAC</td></tr><tr><td>CRS</td><td>Carrier sense</td><td>PHY to MAC</td></tr><tr><td>COL</td><td>Collision detect</td><td>PHY to MAC</td></tr></tbody></table> <p>The first seven receiver signals are entirely analogous to the transmitter signals, except RX_ER is not optional and used to indicate the received signal could not be decoded to valid data. The receive clock is recovered from the incoming signal during frame reception. When no clock can be recovered (i.e. when the medium is silent), the PHY must present a free-running clock as a substitute. </p><p>The receive data valid signal (RX_DV) is not required to go high immediately when the frame starts, but must do so in time to ensure the "start of frame delimiter" byte is included in the received data. Some of the preamble nibbles may be lost. </p><p>Similar to transmit, raising RX_ER outside a frame is used for special signalling. For receive, two data values are defined: 0b0001 to indicate the link partner is in EEE low power mode, and 0b1110 for a <i>false carrier</i> indication. </p><p>The CRS and COL signals are asynchronous to the receive clock, and are only meaningful in half-duplex mode. Carrier sense is high when transmitting, receiving, or the medium is otherwise sensed as being in use. If a collision is detected, COL also goes high while the collision persists. </p><p>In addition, the MAC may weakly pull-up the COL signal, allowing the combination of COL high with CRS low (which a PHY will never produce) to serve as indication of an absent/disconnected PHY. </p> <h3>Management signals</h3> <p class="note">Main article: <a href="/facts/Management_Data_Input/Output/sl8lAs2n">Management Data Input/Output</a></p> <table><tbody><tr><th>Signal name</th><th>Description</th><th>Direction</th></tr><tr><td>MDIO</td><td>Management data</td><td>Bidirectional</td></tr><tr><td>MDC</td><td>Management data clock</td><td>MAC to PHY</td></tr></tbody></table> <p>MDC and MDIO constitute a synchronous serial data interface similar to <a href="/facts/I%C2%B2C/dKBBhs4U">I²C</a>. As with I²C, the interface is a <a href="/facts/Multidrop_bus/2SMRsccq">multidrop bus</a> so MDC and MDIO can be shared among multiple PHYs. </p> <h3>Limitations</h3> <p>The interface requires 18 signals, out of which only two (MDIO and MDC) can be shared among multiple PHYs. This presents a problem, especially for multiport devices; for example, an eight-port switch using MII would need 8 × 16 + 2 = 130 signals. </p> <h2 id="reduced-media-independent-interface">Reduced media-independent interface</h2> <p class="note">"RMII" redirects here; not to be confused with <a href="/facts/RM2_(disambiguation)/h0oDnSeN">RM2</a>.</p> <p>Reduced media-independent interface (RMII) is a standard which was developed to reduce the number of signals required to connect a PHY to a MAC. This helps reduce cost and complexity for network hardware, especially in the context of <a href="/facts/Microcontroller/MKrnAhnm">microcontrollers</a> with built-in MAC, <a href="/facts/FPGA/M8LSGcAU">FPGAs</a>, multiport switches or repeaters, and PC motherboard chipsets. The following changes from the MII standard cut the number of required signals from 18 in half to only 9: </p> <ul><li>MII's two clocks (TXCLK and RXCLK) are replaced by a single clock (REF_CLK) used as a reference for both receiver and transmitter signals.</li> <li>The clock frequency is doubled from 25 MHz to 50 MHz, while both data paths are halved from 4 bits to 2 bits. Data is clocked out 2 bits at a time (vs 4 bits at a time in MII) or 1 bit at a time for SNI (10 Mbit/s only). Data is still sampled on the rising edge only (i.e. it is <i>not</i> <a href="/facts/Double-pumped/xqM0kTfk">double-pumped</a>).</li> <li>RXDV and CRS signals are multiplexed into one signal.</li> <li>The COL signal is removed.</li> <li>RX_ER became optional.</li></ul> <p>Additionally on multiport devices (such as a switch), MDIO, MDC, and REF_CLK may be shared, leaving 6 or 7 pins per port. </p> Reduced media-independent interface (RMII) signals<table><tbody><tr><th>Signal name</th><th>Description</th><th>Direction</th></tr><tr><td>REF_CLK</td><td>Continuous 50 MHz reference clock</td><td>Reference clock may be an input on both devices from an external clock source, or may be driven from the MAC to the PHY, or may be driven from the PHY to the MAC</td></tr><tr><td>TXD0</td><td>Transmit data bit 0 (transmitted first)</td><td>MAC to PHY</td></tr><tr><td>TXD1</td><td>Transmit data bit 1</td><td>MAC to PHY</td></tr><tr><td>TX_EN</td><td>When high, clock data on TXD0 and TXD1 to the transmitter</td><td>MAC to PHY</td></tr><tr><td>RXD0</td><td>Receive data bit 0 (received first)</td><td>PHY to MAC</td></tr><tr><td>RXD1</td><td>Receive data bit 1</td><td>PHY to MAC</td></tr><tr><td>CRS_DV</td><td>Carrier Sense (CRS) and RX_Data Valid (RX_DV) multiplexed on alternate clock cycles. In 10 Mbit/s mode, it alternates every 10 clock cycles.</td><td>PHY to MAC</td></tr><tr><td>RX_ER</td><td>Receive error (optional)</td><td>PHY to MAC</td></tr><tr><td>MDIO</td><td>Management data</td><td>Bidirectional</td></tr><tr><td>MDC</td><td>Management data clock.</td><td>MAC to PHY</td></tr></tbody></table> <p>Note: the REF_CLK operates at 50 MHz in both 100 Mbit/s mode and 10 Mbit/s mode. The transmitting side (PHY or MAC) must keep all signals valid for 10 clock cycles in 10 Mbit/s mode. The receiver (PHY or MAC) samples the input signals only every 10 cycles in 10 Mbit/s mode. </p> <h3>Limitations</h3> <p>There is no signal which defines whether the interface is in full or half duplex mode, but both the MAC and the PHY need to agree. This must instead be communicated over the serial MDIO/MDC interface. There is also no signal which defines whether the interface is in 10 or 100 Mbit/s mode, so this must also be handled using the MDIO/MDC interface. Version 1.2 of the RMII Consortium specification states that its MDIO/MDC interface is identical to that specified for MII in IEEE 802.3u. Current revisions of IEEE 802.3 specify a standard MDIO/MDC mechanism for negotiating and configuring the link's speed and duplex mode, but it is possible that older PHY devices might have been designed against obsolete versions of the standard, and may therefore use proprietary methods to set speed and duplex. </p><p>The lack of the RX_ER signal which is not connected on some MACs (such as multiport switches) is dealt with by data replacement on some PHYs to invalidate the <a href="/facts/Cyclic_redundancy_check/u2exo4sv">CRC</a>. The missing COL signal is derived from AND-ing together the TX_EN and the decoded CRS signal from the CRS_DV line in half duplex mode. This means a slight modification of the definition of CRS: On MII, CRS is asserted for both Rx and Tx frames; on RMII only for Rx frames. This has the consequence that on RMII the two error conditions <i>no carrier</i> and <i>lost carrier</i> cannot be detected, and it is difficult or impossible to support shared media such as <a href="/facts/10BASE2/FfgUgSUz">10BASE2</a> or <a href="/facts/10BASE5/vxgB15fH">10BASE5</a>. </p><p>Since the RMII standard neglected to stipulate that TX_EN should only be sampled on alternate clock cycles, it is not symmetric with CRS_DV and two RMII PHY devices cannot be connected back to back to form a repeater; this is possible, however, with the National DP83848 which supplies the decoded RX_DV as a supplemental signal in RMII mode.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> </p> <h3>Signal levels</h3> <p>TTL <a href="/facts/Logic_level/aa9GrAPg">logic levels</a> are used for 5 V or 3.3 V logic. Input high threshold is 2.0 V and low is 0.8 V. The specification states that inputs should be 5 V tolerant, however, some popular chips with RMII interfaces are not 5 V tolerant. Newer devices may support 2.5 V and 1.8 V logic. </p><p>The RMII signals are treated as <a href="/facts/Lumped-element_model/Nqtt18v5">lumped signals</a> rather than <a href="/facts/Transmission_line/cYlqaPo3">transmission lines</a>. However, the IEEE version of the related MII standard specifies 68 Ω trace impedance.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> National recommends running 50 Ω traces with 33 Ω <a href="/facts/Series_termination/MatLrePo">series termination</a> resistors for either MII or RMII mode to reduce reflections. National also suggests that traces be kept under 0.15 m long and matched within 0.05 m on length to minimize skew.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a>: 5 </p> <h2 id="gigabit-media-independent-interface">Gigabit media-independent interface</h2> <p>The gigabit media-independent interface (GMII) is an interface between the <a href="/facts/Medium_access_control/hFpNzFFD">medium access control</a> (MAC) device and the physical layer (<a href="/facts/PHY/tkEaBnt9">PHY</a>). The interface operates at speeds up to 1000 Mbit/s, implemented using a data interface clocked at 125 MHz with separate eight-bit data paths for receive and transmit, and is backwards compatible with the MII specification and can operate on fall-back speeds of 10 or 100 Mbit/s. </p><p>The GMII interface was first defined for 1000BASE-X in IEEE 802.3z-1998 as clause 35, and subsequently incorporated into IEEE 802.3-2000 onwards.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a>: Clause 35 </p> <h3>Transmitter signals</h3> <table><tbody><tr><th>Signal name</th><th>Description</th></tr><tr><td>GTXCLK</td><td>Clock signal for gigabit TX signals (125 MHz)</td></tr><tr><td>TXCLK</td><td>Clock signal for 10/100 Mbit/s signals</td></tr><tr><td>TXD[7..0]</td><td>Data to be transmitted</td></tr><tr><td>TXEN</td><td>Transmitter enable</td></tr><tr><td>TXER</td><td>Transmitter error (used to intentionally corrupt a packet, if necessary)</td></tr></tbody></table> <p>There are two transmitter clocks. The clock used depends on whether the PHY is operating at gigabit or 10/100 Mbit/s speeds. For gigabit operation, the GTXCLK is supplied to the PHY and the TXD, TXEN, TXER signals are synchronized to this. For 10 or 100 Mbit/s operation, the TXCLK is supplied by the PHY and is used for synchronizing those signals. This operates at either 25 MHz for 100 Mbit/s or 2.5 MHz for 10 Mbit/s connections. In contrast, the receiver uses a single clock signal recovered from the incoming data. </p> <h3>Receiver signals</h3> <table><tbody><tr><th>Signal name</th><th>Description</th></tr><tr><td>RXCLK</td><td>Received <a href="/facts/Clock_signal/9UfTzGHx">clock signal</a> (recovered from incoming received data)</td></tr><tr><td>RXD[7..0]</td><td>Received data</td></tr><tr><td>RXDV</td><td>Signifies data received is valid</td></tr><tr><td>RXER</td><td>Signifies data received has errors</td></tr><tr><td>COL</td><td>Collision detect (half-duplex connections only)</td></tr><tr><td>CS</td><td>Carrier sense (half-duplex connections only)</td></tr></tbody></table> <h3>Management signals</h3> <table><tbody><tr><th>Signal name</th><th>Description</th></tr><tr><td>MDC</td><td>Management interface clock</td></tr><tr><td><a href="/facts/MDIO/sl8lAs2n">MDIO</a></td><td>Management interface I/O bidirectional pin.</td></tr></tbody></table> <p>The management interface controls the behavior of the PHY. It has the same set of registers as the MII, except that register #15 is the Extended Status register.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a>: Section 22.2.4 "Management functions" </p> <h2 id="reduced-gigabit-media-independent-interface">Reduced gigabit media-independent interface</h2> Supported Ethernet speeds<table><tbody><tr><th>[Mbit/s]</th><th>[<a href="/facts/MHz/6Wshj5qm">MHz</a>]</th><th>Bits/clock cycle</th></tr><tr><td>10</td><td>2.5</td><td>4</td></tr><tr><td>100</td><td>25 </td><td>4</td></tr><tr><td>1000</td><td>125 </td><td>8</td></tr></tbody></table> <p>The reduced gigabit media-independent interface (RGMII) uses half the number of data pins as are used in the GMII interface. This reduction is achieved by running half as many data lines at double speed, time multiplexing signals and by eliminating non-essential carrier-sense and collision-indication signals. Thus RGMII consists only of 14 pins, as opposed to GMII's 24 to 27. </p><p>Data is clocked on rising and falling edges for 1000 Mbit/s, and on rising edges only for 10/100 Mbit/s.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> The RX_CTL signal carries RXDV (data valid) on the rising edge, and (RXDV xor RXER) on the falling edge. The TX_CTL signal likewise carries TXEN on rising edge and (TXEN xor TXER) on the falling edge. This is the case for both 1000 Mbit/s and 10/100 Mbit/s.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> </p><p>The transmit clock signal is always provided by the MAC on the TXC line. The receive clock signal is always provided by the PHY on the RXC line. <a href="/facts/Source-synchronous/vqdgIfhx">Source-synchronous</a> clocking is used: the clock signal that is output (by either the PHY or the MAC) is synchronous with the data signals. This requires the PCB to be designed to add a 1.5–2 ns delay to the clock signal to meet the setup and hold times on the sink. RGMII v2.0 specifies an optional internal delay, obviating the need for the PCB designer to add delay; this is known as RGMII-ID. </p> RGMII signals<table><tbody><tr><th>Signal name</th><th>Description</th><th>Direction</th></tr><tr><td>TXC</td><td>Clock signal</td><td>MAC to PHY</td></tr><tr><td>TXD[3..0]</td><td>Data to be transmitted</td><td>MAC to PHY</td></tr><tr><td>TX_CTL</td><td>Multiplexing of transmitter enable and transmitter error</td><td>MAC to PHY</td></tr><tr><td>RXC</td><td>Received <a href="/facts/Clock_signal/9UfTzGHx">clock signal</a> (recovered from incoming received data)</td><td>PHY to MAC</td></tr><tr><td>RXD[3..0]</td><td>Received data</td><td>PHY to MAC</td></tr><tr><td>RX_CTL</td><td>Multiplexing of data received is valid and receiver error</td><td>PHY to MAC</td></tr><tr><td>MDC</td><td>Management interface clock</td><td>MAC to PHY</td></tr><tr><td><a href="/facts/MDIO/sl8lAs2n">MDIO</a></td><td>Management interface I/O</td><td>Bidirectional</td></tr></tbody></table> <p>RGMII version 1.3<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a> uses 2.5V CMOS,<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a> whereas RGMII version 2 uses 1.5V <a href="/facts/High-speed_transceiver_logic/HAhn3cEc">HSTL</a>.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a> </p> <h2 id="serial-gigabit-media-independent-interface">Serial gigabit media-independent interface</h2> <p>The serial gigabit media-independent interface (SGMII) is a variant of MII used for <a href="/facts/Gigabit_Ethernet/1ItIoV2w">Gigabit Ethernet</a> but can also carry 10/100 Mbit/s Ethernet. </p><p>It uses differential pairs at 625 MHz clock frequency DDR for TX and RX data and TX and RX clocks. It differs from <a href="/facts/GMII/CKB7edH3">GMII</a> by its low-power and low pin-count <a href="/facts/8b/10b/bxnMBwaC">8b/10b</a>-coded <a href="/facts/SerDes/tzVeKyyV">SerDes</a>. Transmit and receive path each use one differential pair for data and another differential pair for clock. The TX/RX clocks must be generated on device output but are optional on device input (<a href="/facts/Clock_recovery/hrTr6rlS">clock recovery</a> may be used alternatively). 10/100 Mbit/s Ethernet is carried by duplicating data words 100/10 times each, so the clock is always at 625 MHz. </p> <h2 id="high-serial-gigabit-media-independent-interface">High serial gigabit media independent interface</h2> <p>The high serial gigabit media-independent interface (HSGMII) is functionally similar to the SGMII but supports link speeds of up to 2.5 Gbit/s. </p> <h2 id="quad-serial-gigabit-media-independent-interface">Quad serial gigabit media-independent interface</h2> <p>The quad serial gigabit media-independent interface (QSGMII) is a method of combining four SGMII lines into a 5 Gbit/s interface. QSGMII, like SGMII, uses <a href="/facts/Low-voltage_differential_signaling/RsEysH9H">low-voltage differential signaling</a> (LVDS) for the TX and RX data, and a single LVDS clock signal. QSGMII uses significantly fewer signal lines than four separate SGMII connections. </p><p>QSGMII predates <a href="/facts/NBASE-T/REWNhYIf">NBASE-T</a> and is used to connect multi-port PHYs to MACs, for example in network routers.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a> </p><p>The PSGMII (penta serial gigabit media-independent interface) uses the same signal lines as QSGMII, but operates at 6.25 Gbit/s, which supports five 1 gigabit/s ports through one MII. </p> <h2 id="10-gigabit-media-independent-interface">10 gigabit media-independent interface</h2> <p>10 gigabit media-independent interface (XGMII) is a standard defined in <a href="/facts/IEEE_802.3/Q9jxNSNT">IEEE 802.3</a> designed for connecting full duplex <a href="/facts/10_Gigabit_Ethernet/FvxUohpf">10 Gigabit Ethernet</a> (10GbE) ports to each other and to other electronic devices on a <a href="/facts/Printed_circuit_board/muSR2p43">printed circuit board</a> (PCB). It is now typically used for on-chip connections. PCB connections are now mostly accomplished with <a href="/facts/XAUI/9wyTc2Yl">XAUI</a>. XGMII features two 32-bit datapaths (Rx & Tx) and two four-bit control flows (Rxc and Txc), operating at 156.25 MHz <a href="/facts/Double_data_rate/xqM0kTfk">DDR</a> (312.5 <a href="/facts/MT/s/fgBCc5U9">MT/s</a>).<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a> </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Attachment_Unit_Interface/TMg2ru43">Attachment Unit Interface</a> (AUI)</li> <li><a href="/facts/G.hn/Tf9P5x7s">G.hn</a>, an <a href="/facts/ITU-T/9nJwkPYx">ITU-T</a> recommendation that uses the term MII to refer to the interface between the <a href="/facts/Data_link_layer/K9yPufbt">data link layer</a> and the <a href="/facts/Physical_layer/WuATCrVw">physical layer</a>.</li> <li><a href="/facts/Gigabit_interface_converter/x4oAvlDA">Gigabit interface converter</a> (GBIC)</li> <li><a href="/facts/List_of_interface_bit_rates/RJzvfP0g">List of interface bit rates</a></li> <li><a href="/facts/Medium-dependent_interface/JFKPSq67">Medium-dependent interface</a> (MDI)</li> <li><a href="/facts/Small_form-factor_pluggable_transceiver/bp1RTekJ">Small form-factor pluggable transceiver</a> (SFP)</li> <li><a href="/facts/XAUI/9wyTc2Yl">XAUI</a> – 10 Gigabit Attachment Unit Interface</li> <li><a href="/facts/XFP_transceiver/743mGJ3o">XFP transceiver</a></li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="http://www.ti.com/lit/an/snla076a/snla076a.pdf">Texas Instruments – AN-1405 DP83848 RMII</a></li> <li><a href="http://www.ti.com.cn/cn/lit/ds/symlink/dp83848c.pdf">Texas Instruments – DP83848C PHY Data Sheet</a></li> <li><a href="https://web.archive.org/web/20160303171328/http://www.hp.com/rnd/pdfs/RGMIIv2_0_final_hp.pdf">hp.com – RGMIIv2_0_final_hp.pdf RGMII 2002-04-01 Version 2.0 </a></li> <li><a href="https://web.archive.org/web/20150714164353/http://www.angelfire.com/electronic2/sharads/protocols/MII_Protocols/sgmii.pdf"><i>Serial-GMII Specification Revision 1.7 (ENG-46158)</i></a> (PDF), archived from <a href="http://www.angelfire.com/electronic2/sharads/protocols/MII_Protocols/sgmii.pdf">the original</a> (PDF) on 2015-07-14</li> <li><a href="https://web.archive.org/web/20061211171613/http://www.parthus.com/products/platforms/sgmii.php">"CEVA implementation documentation"</a>. Archived from <a href="http://www.parthus.com/products/platforms/sgmii.php">the original</a> on 2006-12-11.</li> <li><a href="https://web.archive.org/web/20110903061926/http://www.altera.com/support/refdesigns/ip/interface/ref-10gbe.html">Altera 10 Gb Ethernet IP with XGMII and XAUI interfaces </a></li> <li><a href="http://www.ieee802.org/3/z/public/presentations/nov1996/AIgmitim.pdf">GMII Timing and Electrical Specification </a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"KSZ8001L/S 1.8V, 3.3V 10/100BASE-T/TX/FX Physical Layer Transceiver" (PDF). <a href="http://ww1.microchip.com/downloads/en/DeviceDoc/KSZ8001L-S-Data-Sheet-DS00003062A.pdf" target="_blank">http://ww1.microchip.com/downloads/en/DeviceDoc/KSZ8001L-S-Data-Sheet-DS00003062A.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>IEEE Standard for Ethernet. IEEE 802.3. 31 August 2018. doi:10.1109/IEEESTD.2018.8457469. ISBN 978-1-5044-5090-4. <a href="978-1-5044-5090-4" target="_blank">978-1-5044-5090-4</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>IEEE Standard for Ethernet. IEEE 802.3. 31 August 2018. doi:10.1109/IEEESTD.2018.8457469. ISBN 978-1-5044-5090-4. <a href="978-1-5044-5090-4" target="_blank">978-1-5044-5090-4</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>AN-1405 schematic <a href="http://www.ti.com/lit/an/snla076a/snla076a.pdf" target="_blank">http://www.ti.com/lit/an/snla076a/snla076a.pdf</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>AN-1469 datasheet <a href="http://www.ti.com/lit/an/snla079d/snla079d.pdf" target="_blank">http://www.ti.com/lit/an/snla079d/snla079d.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>AN-1469 datasheet <a href="http://www.ti.com/lit/an/snla079d/snla079d.pdf" target="_blank">http://www.ti.com/lit/an/snla079d/snla079d.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>IEEE Standard for Ethernet. IEEE 802.3. 31 August 2018. doi:10.1109/IEEESTD.2018.8457469. ISBN 978-1-5044-5090-4. <a href="978-1-5044-5090-4" target="_blank">978-1-5044-5090-4</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>IEEE Standard for Ethernet. IEEE 802.3. 31 August 2018. doi:10.1109/IEEESTD.2018.8457469. ISBN 978-1-5044-5090-4. <a href="978-1-5044-5090-4" target="_blank">978-1-5044-5090-4</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"Reduced Gigabit Media Independent Interface (RGMII) Version 2.0" (PDF). 2002-04-01. Archived from the original on 2016-03-03.{{cite web}}: CS1 maint: bot: original URL status unknown (link) <a href="https://web.archive.org/web/20160303171328/http://www.hp.com/rnd/pdfs/RGMIIv2_0_final_hp.pdf" target="_blank">https://web.archive.org/web/20160303171328/http://www.hp.com/rnd/pdfs/RGMIIv2_0_final_hp.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>"XWAY PHY11G" (PDF). Archived from the original (PDF) on 2014-04-13. Retrieved 2014-04-11. <a href="https://web.archive.org/web/20140413125523/http://www.we-online.de/web/en/index.php/show/media/07_electronic_components/produkte_3/lantiq/Data_Sheet_XWAY_PHY11G_V15_UM_HD_Rev10_VQFN48.pdf" target="_blank">https://web.archive.org/web/20140413125523/http://www.we-online.de/web/en/index.php/show/media/07_electronic_components/produkte_3/lantiq/Data_Sheet_XWAY_PHY11G_V15_UM_HD_Rev10_VQFN48.pdf</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>"Reduced Gigabit Media Independent Interface (RGMII) Version 1.3" (PDF). 2000-12-10. Archived from the original (PDF) on 2016-03-03. <a href="https://web.archive.org/web/20160303212629/http://www.hp.com/rnd/pdfs/RGMIIv1_3.pdf" target="_blank">https://web.archive.org/web/20160303212629/http://www.hp.com/rnd/pdfs/RGMIIv1_3.pdf</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>"2.5 V ± 0.2 V (Normal Range) and 1.8 V – 2.7 V (Wide Range) Power Supply Voltage and Interface Standard for Nonterminated Digital Integrated Circuits, JESD8-5A.01" (PDF). 2006-06-01. <a href="http://www.jedec.org/sites/default/files/docs/JESD8-5A-01.pdf" target="_blank">http://www.jedec.org/sites/default/files/docs/JESD8-5A-01.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>"High Speed Transceiver Logic (HSTL). A 1.5V Output Buffer Supply Voltage Based Interface Standard for Digital Integrated Circuits, JESD8-6" (PDF). 1995-08-01. <a href="http://www.jedec.org/sites/default/files/docs/jesd8-6.pdf" target="_blank">http://www.jedec.org/sites/default/files/docs/jesd8-6.pdf</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>"QSGMII Specification" (PDF). Cisco. 2009-08-03. Retrieved 2024-10-01. <a href="https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/powerquicc/3546/1/qsgmii%20specification.pdf" target="_blank">https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/powerquicc/3546/1/qsgmii%20specification.pdf</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>IEEE 802.3 clauses 46 & 47 <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> </ol>