1.\" $OpenBSD: vr.4,v 1.22 2009/03/16 22:47:45 sobrado Exp $ 2.\" 3.\" Copyright (c) 1997, 1998 4.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by Bill Paul. 17.\" 4. Neither the name of the author nor the names of any co-contributors 18.\" may be used to endorse or promote products derived from this software 19.\" without specific prior written permission. 20.\" 21.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND 22.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 23.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 24.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD 25.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 26.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 29.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 31.\" THE POSSIBILITY OF SUCH DAMAGE. 32.\" 33.\" $FreeBSD: vr.4,v 1.3 1999/03/25 00:52:44 wpaul Exp $ 34.\" 35.Dd $Mdocdate: March 16 2009 $ 36.Dt VR 4 37.Os 38.Sh NAME 39.Nm vr 40.Nd VIA VT3043/VT86C100A/VT6105/VT6105M 10/100 Ethernet device 41.Sh SYNOPSIS 42.Cd "vr* at pci?" 43.Cd "amphy* at mii?" 44.Cd "sqphy* at mii?" 45.Sh DESCRIPTION 46The 47.Nm 48driver provides support for PCI Ethernet adapters and embedded 49controllers based on the VIA Technologies VT3043 Rhine I, 50VT86C100A Rhine II, and VT6105/VT6105M Rhine III Fast Ethernet 51controller chips. 52This includes the D-Link DFE530-TX and various other commodity Fast Ethernet 53cards. 54.Pp 55The VIA Rhine chips use bus master DMA and have a software interface 56designed to resemble that of the DEC 21x4x "tulip" chips. 57The major differences are that the receive filter in the Rhine chips is 58much simpler and is programmed through registers rather than by 59downloading a special setup frame through the transmit DMA engine, 60and that transmit and receive DMA buffers must be longword aligned. 61The Rhine chips are meant to be interfaced with external 62physical layer devices via an MII bus. 63They support both 10 and 100Mbps speeds in either full or half duplex. 64.Pp 65The 66.Nm 67driver supports the following media types: 68.Bl -tag -width full-duplex 69.It autoselect 70Enable autoselection of the media type and options. 71The user can manually override 72the autoselected mode by adding media options to the appropriate 73.Xr hostname.if 5 74file. 75.It 10baseT 76Set 10Mbps operation. 77The 78.Ar mediaopt 79option can also be used to select either 80.Ar full-duplex 81or 82.Ar half-duplex 83modes. 84.It 100baseTX 85Set 100Mbps (Fast Ethernet) operation. 86The 87.Ar mediaopt 88option can also be used to select either 89.Ar full-duplex 90or 91.Ar half-duplex 92modes. 93.El 94.Pp 95The 96.Nm 97driver supports the following media options: 98.Bl -tag -width full-duplex 99.It full-duplex 100Force full duplex operation. 101.It half-duplex 102Force half duplex operation. 103.El 104.Pp 105Note that the 100baseTX media type is only available if supported 106by the adapter. 107For more information on configuring this device, see 108.Xr ifconfig 8 . 109.Sh DIAGNOSTICS 110.Bl -diag 111.It "vr%d: couldn't map memory" 112A fatal initialization error has occurred. 113.It "vr%d: couldn't map interrupt" 114A fatal initialization error has occurred. 115.It "vr%d: watchdog timeout" 116The device has stopped responding to the network, or there is a problem with 117the network connection (cable). 118.It "vr%d: no memory for rx list" 119The driver failed to allocate an mbuf for the receiver ring. 120.It "vr%d: no memory for tx list" 121The driver failed to allocate an mbuf for the transmitter ring when 122allocating a pad buffer or collapsing an mbuf chain into a cluster. 123.It "vr%d: chip is in D3 power state -- setting to D0" 124This message applies only to adapters which support power management. 125Some operating systems place the controller in low power 126mode when shutting down, and some PCI BIOSes fail to bring the chip 127out of this state before configuring it. 128The controller loses all of its PCI configuration in the D3 state, so if the 129BIOS does not set it back to full power mode in time, it won't be able to 130configure it correctly. 131The driver tries to detect this condition and bring 132the adapter back to the D0 (full power) state, but this may not be 133enough to return the driver to a fully operational condition. 134If this message appears at boot time and the driver fails to attach 135the device as a network interface, a second warm boot will have to be 136performed to have the device properly configured. 137.Pp 138Note that this condition only occurs when warm booting from another 139operating system. 140If the system is powered down prior to booting 141.Ox , 142the card should be configured correctly. 143.El 144.Sh SEE ALSO 145.Xr amphy 4 , 146.Xr arp 4 , 147.Xr ifmedia 4 , 148.Xr intro 4 , 149.Xr netintro 4 , 150.Xr pci 4 , 151.Xr sqphy 4 , 152.Xr hostname.if 5 , 153.Xr ifconfig 8 154.Rs 155.%T The VIA Technologies VT86C100A data sheet 156.%O http://www.via.com.tw 157.Re 158.Sh HISTORY 159The 160.Nm 161device driver first appeared in 162.Fx 3.0 . 163.Ox 164support first appeared in 165.Ox 2.5 . 166.Sh AUTHORS 167The 168.Nm 169driver was written by 170.An Bill Paul Aq wpaul@ctr.columbia.edu . 171.Sh BUGS 172The 173.Nm 174driver always copies transmit mbuf chains into longword-aligned 175buffers prior to transmission in order to pacify the Rhine chips. 176If buffers are not aligned correctly, the chip will round the 177supplied buffer address and begin DMAing from the wrong location. 178This buffer copying impairs transmit performance on slower systems but can't 179be avoided. 180On faster machines (e.g., a Pentium II), the performance 181impact is much less noticeable. 182