1.\" Copyright (c) 1997, 1998 2.\" Bill Paul <wpaul@ctr.columbia.edu>. 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: src/share/man/man4/vr.4,v 1.11.2.5 2003/02/17 21:20:39 trhodes Exp $ 32.\" $DragonFly: src/share/man/man4/vr.4,v 1.8 2008/07/11 10:38:50 thomas Exp $ 33.\" 34.Dd November 22, 1998 35.Dt VR 4 36.Os 37.Sh NAME 38.Nm vr 39.Nd "VIA Technologies VT3043 and VT86C100A ethernet device driver" 40.Sh SYNOPSIS 41.Cd "device miibus" 42.Cd "device vr" 43.Sh DESCRIPTION 44The 45.Nm 46driver provides support for PCI ethernet adapters and embedded 47controllers based on the VIA Technologies VT3043 Rhine I and 48VT86C100A Rhine II fast ethernet controller chips. 49This includes 50the D-Link DFE530-TX, the Hawking Technologies PN102TX, the 51AOpen/Acer ALN-320, and various other commodity fast ethernet 52cards. 53.Pp 54The VIA Rhine chips use bus master DMA and have a descriptor layout 55designed to resemble that of the DEC 21x4x "tulip" chips. 56The register 57layout is different however and the receive filter in the Rhine chips 58is much simpler and is programmed through registers rather than by 59downloading a special setup frame through the transmit DMA engine. 60Transmit and receive DMA buffers must be longword 61aligned. 62The Rhine chips are meant to be interfaced with external 63physical layer devices via an MII bus. 64They support both 6510 and 100Mbps speeds in either full or half duplex. 66.Pp 67The 68.Nm 69driver supports the following media types: 70.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 71.It autoselect 72Enable autoselection of the media type and options. 73The user can manually override 74the autoselected mode by adding media options to the 75.Pa /etc/rc.conf 76file. 77.It 10baseT/UTP 78Set 10Mbps operation. 79The 80.Ar mediaopt 81option can also be used to select either 82.Ar full-duplex 83or 84.Ar half-duplex 85modes. 86.It 100baseTX 87Set 100Mbps (fast ethernet) operation. 88The 89.Ar mediaopt 90option can also be used to select either 91.Ar full-duplex 92or 93.Ar half-duplex 94modes. 95.El 96.Pp 97The 98.Nm 99driver supports the following media options: 100.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 101.It full-duplex 102Force full duplex operation 103.It half-duplex 104Force half duplex operation. 105.El 106.Pp 107Note that the 100baseTX media type is only available if supported 108by the adapter. 109.Pp 110For more information on configuring this device, see 111.Xr ifconfig 8 . 112The 113.Nm 114driver supports 115.Xr polling 4 . 116.Sh DIAGNOSTICS 117.Bl -diag 118.It "vr%d: couldn't map memory" 119A fatal initialization error has occurred. 120.It "vr%d: couldn't map interrupt" 121A fatal initialization error has occurred. 122.It "vr%d: watchdog timeout" 123The device has stopped responding to the network, or there is a problem with 124the network connection (cable). 125.It "vr%d: no memory for rx list" 126The driver failed to allocate an mbuf for the receiver ring. 127.It "vr%d: no memory for tx list" 128The driver failed to allocate an mbuf for the transmitter ring when 129allocating a pad buffer or collapsing an mbuf chain into a cluster. 130.It "vr%d: chip is in D3 power state -- setting to D0" 131This message applies only to adapters which support power 132management. 133Some operating systems place the controller in low power 134mode when shutting down, and some PCI BIOSes fail to bring the chip 135out of this state before configuring it. 136The controller loses all of 137its PCI configuration in the D3 state, so if the BIOS does not set 138it back to full power mode in time, it won't be able to configure it 139correctly. 140The driver tries to detect this condition and bring 141the adapter back to the D0 (full power) state, but this may not be 142enough to return the driver to a fully operational condition. 143If 144you see this message at boot time and the driver fails to attach 145the device as a network interface, you will have to perform second 146warm boot to have the device properly configured. 147.Pp 148Note that this condition only occurs when warm booting from another 149operating system. 150If you power down your system prior to booting 151.Dx , 152the card should be configured correctly. 153.El 154.Sh SEE ALSO 155.Xr arp 4 , 156.Xr ifmedia 4 , 157.Xr miibus 4 , 158.Xr netintro 4 , 159.Xr ng_ether 4 , 160.Xr polling 4 , 161.Xr ifconfig 8 162.Rs 163.%T The VIA Technologies VT86C100A data sheet 164.%O http://www.via.com.tw 165.Re 166.Sh HISTORY 167The 168.Nm 169device driver first appeared in 170.Fx 3.0 . 171.Sh AUTHORS 172The 173.Nm 174driver was written by 175.An Bill Paul Aq wpaul@ctr.columbia.edu . 176.Sh BUGS 177The 178.Nm 179driver always copies transmit mbuf chains into longword-aligned 180buffers prior to transmission in order to pacify the Rhine chips. 181If buffers are not aligned correctly, the chip will round the 182supplied buffer address and begin DMAing from the wrong location. 183This buffer copying impairs transmit performance on slower systems but can't 184be avoided. 185On faster machines (e.g. a Pentium II), the performance 186impact is much less noticeable. 187