Deleted Added
full compact
re.4 (126579) re.4 (131530)
1.\" Copyright (c) 2003
2.\" Bill Paul <wpaul@windriver.com>. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 14 unchanged lines hidden (view full) ---

23.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
24.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
25.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
26.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
28.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
29.\" THE POSSIBILITY OF SUCH DAMAGE.
30.\"
1.\" Copyright (c) 2003
2.\" Bill Paul <wpaul@windriver.com>. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.

--- 14 unchanged lines hidden (view full) ---

23.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
24.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
25.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
26.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
28.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
29.\" THE POSSIBILITY OF SUCH DAMAGE.
30.\"
31.\" $FreeBSD: head/share/man/man4/re.4 126579 2004-03-04 06:42:46Z sanpei $
31.\" $FreeBSD: head/share/man/man4/re.4 131530 2004-07-03 18:29:24Z ru $
32.\"
33.Dd September 4, 2003
34.Dt RE 4
35.Os
36.Sh NAME
37.Nm re
38.Nd "RealTek 8139C+/8169/8169S/8110S PCI ethernet adapter driver"
39.Sh SYNOPSIS

--- 9 unchanged lines hidden (view full) ---

49.Bl -bullet -compact
50.It
51Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)
52.It
53Compaq Evo N1015v Integrated Ethernet (8139C+)
54.It
55Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)
56.It
32.\"
33.Dd September 4, 2003
34.Dt RE 4
35.Os
36.Sh NAME
37.Nm re
38.Nd "RealTek 8139C+/8169/8169S/8110S PCI ethernet adapter driver"
39.Sh SYNOPSIS

--- 9 unchanged lines hidden (view full) ---

49.Bl -bullet -compact
50.It
51Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)
52.It
53Compaq Evo N1015v Integrated Ethernet (8139C+)
54.It
55Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)
56.It
57PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)
57PLANEX COMMUNICATIONS Inc.\& GN-1200TC (8169S)
58.It
59Xterasys XN-152 10/100/1000 NIC (8169)
60.El
61.Pp
62NICs based on the 8139C+ are capable of 10 and 100Mbps speeds over CAT5
58.It
59Xterasys XN-152 10/100/1000 NIC (8169)
60.El
61.Pp
62NICs based on the 8139C+ are capable of 10 and 100Mbps speeds over CAT5
63cable. NICs based on the 8169, 8169S and 8110S are capable of 10, 100 and
63cable.
64NICs based on the 8169, 8169S and 8110S are capable of 10, 100 and
641000Mbps operation.
65.Pp
66All NICs supported by the
67.Nm
68driver have TCP/IP checksum offload and hardware VLAN tagging/insertion
651000Mbps operation.
66.Pp
67All NICs supported by the
68.Nm
69driver have TCP/IP checksum offload and hardware VLAN tagging/insertion
69features, and use a descriptor-based DMA mechanism. They are also
70features, and use a descriptor-based DMA mechanism.
71They are also
70capable of TCP large send (TCP segmentation offload).
71.Pp
72The 8139C+ is a single-chip solution combining both a 10/100 MAC and PHY.
73The 8169 is a 10/100/1000 MAC only, requiring a GMII or TBI external PHY.
74The 8169S and 8110S are single-chip devices containing both a 10/100/1000
72capable of TCP large send (TCP segmentation offload).
73.Pp
74The 8139C+ is a single-chip solution combining both a 10/100 MAC and PHY.
75The 8169 is a 10/100/1000 MAC only, requiring a GMII or TBI external PHY.
76The 8169S and 8110S are single-chip devices containing both a 10/100/1000
75MAC and 10/100/1000 copper PHY. Standalone 10/100/1000 cards are available
76in both 32-bit PCI and 64-bit PCI models. The 8110S is designed for
77MAC and 10/100/1000 copper PHY.
78Standalone 10/100/1000 cards are available
79in both 32-bit PCI and 64-bit PCI models.
80The 8110S is designed for
77embedded LAN-on-motherboard applications.
78.Pp
79The 8169, 8169S and 8110S also support jumbo frames, which can be configured
80via the interface MTU setting.
81Selecting an MTU larger than 1500 bytes with the
82.Xr ifconfig 8
83utility configures the adapter to receive and transmit jumbo frames.
84.Pp

--- 93 unchanged lines hidden (view full) ---

178.Sh AUTHORS
179The
180.Nm
181driver was written by
182.An Bill Paul Aq wpaul@windriver.com .
183.Sh BUGS
184The Xterasys XN-152 32-bit PCI NIC, which uses the RTL8169 MAC and
185Marvell 88E1000 PHY, has a defect that causes DMA corruption
81embedded LAN-on-motherboard applications.
82.Pp
83The 8169, 8169S and 8110S also support jumbo frames, which can be configured
84via the interface MTU setting.
85Selecting an MTU larger than 1500 bytes with the
86.Xr ifconfig 8
87utility configures the adapter to receive and transmit jumbo frames.
88.Pp

--- 93 unchanged lines hidden (view full) ---

182.Sh AUTHORS
183The
184.Nm
185driver was written by
186.An Bill Paul Aq wpaul@windriver.com .
187.Sh BUGS
188The Xterasys XN-152 32-bit PCI NIC, which uses the RTL8169 MAC and
189Marvell 88E1000 PHY, has a defect that causes DMA corruption
186if the board is plugged into a 64-bit PCI slot. The defect
190if the board is plugged into a 64-bit PCI slot.
191The defect
187lies in the board design, not the chip itself: the PCI REQ64# and ACK64#
192lies in the board design, not the chip itself: the PCI REQ64# and ACK64#
188lines should be pulled high, but they are not. The result is that the
193lines should be pulled high, but they are not.
194The result is that the
1898169 chip is tricked into performing 64-bit DMA transfers even though
190a 64-bit data path between the NIC and the bus does not actually exist.
191.Pp
192Unfortunately, it is not possible to correct this problem in software,
1958169 chip is tricked into performing 64-bit DMA transfers even though
196a 64-bit data path between the NIC and the bus does not actually exist.
197.Pp
198Unfortunately, it is not possible to correct this problem in software,
193however it is possible to detect it. When the
199however it is possible to detect it.
200When the
194.Nm
195driver is loaded, it will run a diagnostic routine designed to
196validate DMA operation by placing the chip in digital loopback mode
201.Nm
202driver is loaded, it will run a diagnostic routine designed to
203validate DMA operation by placing the chip in digital loopback mode
197and initiating a packet transmission. If the card functions properly,
204and initiating a packet transmission.
205If the card functions properly,
198the transmitted data will
206the transmitted data will
199be echoed back unmodified. If the echoed data is corrupt, the driver
200will print an error message on the console and abort the device attach. The
207be echoed back unmodified.
208If the echoed data is corrupt, the driver
209will print an error message on the console and abort the device attach.
210The
201user should insure the NIC is installed in a 32-bit PCI slot to
202avoid this problem.
203.Pp
204The RealTek 8169, 8169S and 8110S chips appear to only be capable of
205transmitting jumbo frames up to 7.5K in size.
211user should insure the NIC is installed in a 32-bit PCI slot to
212avoid this problem.
213.Pp
214The RealTek 8169, 8169S and 8110S chips appear to only be capable of
215transmitting jumbo frames up to 7.5K in size.