1 .\" Copyright (c) 1997, 1998
2 .\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
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.
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.
38 .Nd "VIA Technologies Rhine I/II/III Ethernet device driver"
40 To compile this driver into the kernel,
41 place the following lines in your
42 kernel configuration file:
43 .Bd -ragged -offset indent
48 Alternatively, to load the driver as a
49 module at boot time, place the following line in
51 .Bd -literal -offset indent
57 driver provides support for PCI Ethernet adapters and embedded
58 controllers based on the VIA Technologies VT3043 Rhine I,
59 VT86C100A Rhine II, and VT6105/VT6105M Rhine III Fast Ethernet
62 The VIA Rhine chips use bus master DMA and have a descriptor layout
63 designed to resemble that of the DEC 21x4x
67 layout is different however and the receive filter in the Rhine chips
68 is much simpler and is programmed through registers rather than by
69 downloading a special setup frame through the transmit DMA engine.
70 Transmit and receive DMA buffers must be longword
72 The Rhine chips are meant to be interfaced with external
73 physical layer devices via an MII bus.
75 10 and 100Mbps speeds in either full or half duplex.
79 driver supports the following media types:
81 .Bl -tag -width xxxxxxxxxxxxxxxxxxxx
83 Enable autoselection of the media type and options.
84 The user can manually override
85 the autoselected mode by adding media options to the
92 option can also be used to select either
98 Set 100Mbps (Fast Fthernet) operation.
101 option can also be used to select either
110 driver supports the following media options:
112 .Bl -tag -width xxxxxxxxxxxxxxxxxxxx
114 Force full duplex operation
116 Force half duplex operation.
119 Note that the 100baseTX media type is only available if supported
121 For more information on configuring this device, see
126 driver supports VIA Technologies Rhine I, Rhine II, and Rhine III based
127 Fast Ethernet adapters including:
135 Hawking Technologies PN102TX
139 .It "vr%d: couldn't map memory"
140 A fatal initialization error has occurred.
141 .It "vr%d: couldn't map interrupt"
142 A fatal initialization error has occurred.
143 .It "vr%d: watchdog timeout"
144 The device has stopped responding to the network, or there is a problem with
145 the network connection (cable).
146 .It "vr%d: no memory for rx list"
147 The driver failed to allocate an mbuf for the receiver ring.
148 .It "vr%d: no memory for tx list"
149 The driver failed to allocate an mbuf for the transmitter ring when
150 allocating a pad buffer or collapsing an mbuf chain into a cluster.
151 .It "vr%d: chip is in D3 power state -- setting to D0"
152 This message applies only to adapters which support power
154 Some operating systems place the controller in low power
155 mode when shutting down, and some PCI BIOSes fail to bring the chip
156 out of this state before configuring it.
157 The controller loses all of
158 its PCI configuration in the D3 state, so if the BIOS does not set
159 it back to full power mode in time, it will not be able to configure it
161 The driver tries to detect this condition and bring
162 the adapter back to the D0 (full power) state, but this may not be
163 enough to return the driver to a fully operational condition.
165 you see this message at boot time and the driver fails to attach
166 the device as a network interface, you will have to perform second
167 warm boot to have the device properly configured.
169 Note that this condition only occurs when warm booting from another
171 If you power down your system prior to booting
173 the card should be configured correctly.
184 .%T The VIA Technologies VT86C100A data sheet
185 .%O http://www.via.com.tw
190 device driver first appeared in
195 driver was written by
196 .An Bill Paul Aq wpaul@ctr.columbia.edu .
200 driver always copies transmit mbuf chains into longword-aligned
201 buffers prior to transmission in order to pacify the Rhine chips.
202 If buffers are not aligned correctly, the chip will round the
203 supplied buffer address and begin DMAing from the wrong location.
204 This buffer copying impairs transmit performance on slower systems but cannot
206 On faster machines (e.g.\& a Pentium II), the performance
207 impact is much less noticeable.