xref: /dragonfly/share/man/man4/re.4 (revision 43b4d1bd)
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.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by Bill Paul.
15.\" 4. Neither the name of the author nor the names of any co-contributors
16.\"    may be used to endorse or promote products derived from this software
17.\"   without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22.\" ARE DISCLAIMED.  IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
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$
32.\" $DragonFly: src/share/man/man4/re.4,v 1.1 2004/07/07 09:47:27 joerg Exp $
33.\"
34.Dd September 4, 2003
35.Dt RE 4
36.Os
37.Sh NAME
38.Nm re
39.Nd "RealTek 8139C+/8169/8169S/8110S PCI ethernet adapter driver"
40.Sh SYNOPSIS
41.Cd "device miibus"
42.Cd "device re"
43.Sh DESCRIPTION
44The
45.Nm
46driver provides support for various NICs based on the RealTek RTL8139C+,
47RTL8169, RTL8169S and RTL8110S PCI ethernet controllers, including
48the following:
49.Pp
50.Bl -bullet -compact
51.It
52Alloy Computer Products EtherGOLD 1439E 10/100 (8139C+)
53.It
54Compaq Evo N1015v Integrated Ethernet (8139C+)
55.It
56Gigabyte 7N400 Pro2 Integrated Gigabit Ethernet (8110S)
57.It
58PLANEX COMMUNICATIONS Inc. GN-1200TC (8169S)
59.It
60Xterasys XN-152 10/100/1000 NIC (8169)
61.El
62.Pp
63NICs based on the 8139C+ are capable of 10 and 100Mbps speeds over CAT5
64cable. NICs based on the 8169, 8169S and 8110S are capable of 10, 100 and
651000Mbps operation.
66.Pp
67All NICs supported by the
68.Nm
69driver have TCP/IP checksum offload and hardware VLAN tagging/insertion
70features, and use a descriptor-based DMA mechanism. They are also
71capable of TCP large send (TCP segmentation offload).
72.Pp
73The 8139C+ is a single-chip solution combining both a 10/100 MAC and PHY.
74The 8169 is a 10/100/1000 MAC only, requiring a GMII or TBI external PHY.
75The 8169S and 8110S are single-chip devices containing both a 10/100/1000
76MAC and 10/100/1000 copper PHY. Standalone 10/100/1000 cards are available
77in both 32-bit PCI and 64-bit PCI models. The 8110S is designed for
78embedded LAN-on-motherboard applications.
79.Pp
80The 8169, 8169S and 8110S also support jumbo frames, which can be configured
81via the interface MTU setting.
82Selecting an MTU larger than 1500 bytes with the
83.Xr ifconfig 8
84utility configures the adapter to receive and transmit jumbo frames.
85.Pp
86The
87.Nm
88driver supports the following media types:
89.Bl -tag -width 10baseTXUTP
90.It Cm autoselect
91Enable autoselection of the media type and options.
92The user can manually override
93the autoselected mode by adding media options to
94.Xr rc.conf 5 .
95.It Cm 10baseT/UTP
96Set 10Mbps operation.
97The
98.Xr ifconfig 8
99.Ic mediaopt
100option can also be used to select either
101.Cm full-duplex
102or
103.Cm half-duplex
104modes.
105.It Cm 100baseTX
106Set 100Mbps (fast ethernet) operation.
107The
108.Xr ifconfig 8
109.Ic mediaopt
110option can also be used to select either
111.Cm full-duplex
112or
113.Cm half-duplex
114modes.
115.It Cm 1000baseTX
116Set 1000baseTX operation over twisted pair.
117The RealTek gigE chips support 1000Mbps in
118.Cm full-duplex
119mode only.
120.\" .It Cm 1000baseSX
121.\" Set 1000Mbps (gigabit ethernet) operation.
122.\" Both
123.\" .Cm full-duplex
124.\" and
125.\" .Cm half-duplex
126.\" modes are supported.
127.El
128.Pp
129The
130.Nm
131driver supports the following media options:
132.Bl -tag -width full-duplex
133.It Cm full-duplex
134Force full duplex operation.
135.It Cm half-duplex
136Force half duplex operation.
137.El
138.Pp
139For more information on configuring this device, see
140.Xr ifconfig 8 .
141.Sh DIAGNOSTICS
142.Bl -diag
143.It "re%d: couldn't map memory"
144A fatal initialization error has occurred.
145.It "re%d: couldn't map ports"
146A fatal initialization error has occurred.
147.It "re%d: couldn't map interrupt"
148A fatal initialization error has occurred.
149.It "re%d: no memory for softc struct!"
150The driver failed to allocate memory for per-device instance information
151during initialization.
152.It "re%d: failed to enable memory mapping!"
153The driver failed to initialize PCI shared memory mapping.
154This might
155happen if the card is not in a bus-master slot.
156.It "re%d: no memory for jumbo buffers!"
157The driver failed to allocate memory for jumbo frames during
158initialization.
159.It "re%d: watchdog timeout"
160The device has stopped responding to the network, or there is a problem with
161the network connection (cable).
162.El
163.Sh SEE ALSO
164.Xr arp 4 ,
165.Xr miibus 4 ,
166.Xr netintro 4 ,
167.Xr ng_ether 4 ,
168.Xr vlan 4 ,
169.Xr ifconfig 8
170.Rs
171.%T RealTek Semiconductor RTL8139C+, RTL8169, RTL8169S and RTL8110S datasheets
172.%O http://www.realtek.com.tw
173.Re
174.Sh HISTORY
175The
176.Nm
177device driver first appeared in
178.Fx 5.2
179and
180.Dx 1.0 .
181.Sh AUTHORS
182The
183.Nm
184driver was written by
185.An Bill Paul Aq wpaul@windriver.com .
186.Sh BUGS
187The Xterasys XN-152 32-bit PCI NIC, which uses the RTL8169 MAC and
188Marvell 88E1000 PHY, has a defect that causes DMA corruption
189if the board is plugged into a 64-bit PCI slot. The defect
190lies in the board design, not the chip itself: the PCI REQ64# and ACK64#
191lines should be pulled high, but they are not. The result is that the
1928169 chip is tricked into performing 64-bit DMA transfers even though
193a 64-bit data path between the NIC and the bus does not actually exist.
194.Pp
195Unfortunately, it is not possible to correct this problem in software,
196however it is possible to detect it. When the
197.Nm
198driver is loaded, it will run a diagnostic routine designed to
199validate DMA operation by placing the chip in digital loopback mode
200and initiating a packet transmission. If the card functions properly,
201the transmitted data will
202be echoed back unmodified. If the echoed data is corrupt, the driver
203will print an error message on the console and abort the device attach. The
204user should insure the NIC is installed in a 32-bit PCI slot to
205avoid this problem.
206.Pp
207The RealTek 8169, 8169S and 8110S chips appear to only be capable of
208transmitting jumbo frames up to 7.5K in size.
209