| vr.4 (56612) | vr.4 (57676) |
|---|---|
| 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. --- 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) 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. --- 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/vr.4 56612 2000-01-25 20:34:43Z archie $ | 31.\" $FreeBSD: head/share/man/man4/vr.4 57676 2000-03-01 14:50:24Z sheldonh $ |
| 32.\" 33.Dd November 22, 1998 34.Dt VR 4 35.Os FreeBSD 36.Sh NAME 37.Nm vr 38.Nd 39VIA 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 | 32.\" 33.Dd November 22, 1998 34.Dt VR 4 35.Os FreeBSD 36.Sh NAME 37.Nm vr 38.Nd 39VIA 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. This includes | 48VT86C100A Rhine II fast ethernet controller chips. 49This includes |
| 49the D-Link DFE530-TX, the Hawking Technologies PN102TX, the 50AOpen/Acer ALN-320, and various other commodity fast ethernet 51cards. 52.Pp 53The VIA Rhine chips use bus master DMA and have a descriptor layout | 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 |
| 54designed to resemble that of the DEC 21x4x "tulip" chips. The register | 55designed to resemble that of the DEC 21x4x "tulip" chips. 56The register |
| 55layout is different however and the receive filter in the Rhine chips 56is much simpler and is programmed through registers rather than by 57downloading a special setup frame through the transmit DMA engine. 58Transmit and receive DMA buffers must be longword | 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 |
| 59aligned. The Rhine chips are meant to be interfaced with external 60physical layer devices via an MII bus. They support both | 61aligned. 62The Rhine chips are meant to be interfaced with external 63physical layer devices via an MII bus. 64They support both |
| 6110 and 100Mbps speeds in either full or half duplex. 62.Pp 63The 64.Nm 65driver supports the following media types: 66.Pp 67.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 68.It autoselect 69Enable autoselection of the media type and options. 70The user can manually override 71the autoselected mode by adding media options to the 72.Pa /etc/rc.conf 73file. 74.It 10baseT/UTP | 6510 and 100Mbps speeds in either full or half duplex. 66.Pp 67The 68.Nm 69driver supports the following media types: 70.Pp 71.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 72.It autoselect 73Enable autoselection of the media type and options. 74The user can manually override 75the autoselected mode by adding media options to the 76.Pa /etc/rc.conf 77file. 78.It 10baseT/UTP |
| 75Set 10Mbps operation. The | 79Set 10Mbps operation. 80The |
| 76.Ar mediaopt 77option can also be used to select either 78.Ar full-duplex 79or 80.Ar half-duplex modes. 81.It 100baseTX | 81.Ar mediaopt 82option can also be used to select either 83.Ar full-duplex 84or 85.Ar half-duplex modes. 86.It 100baseTX |
| 82Set 100Mbps (fast ethernet) operation. The | 87Set 100Mbps (fast ethernet) operation. 88The |
| 83.Ar mediaopt 84option can also be used to select either 85.Ar full-duplex 86or 87.Ar half-duplex 88modes. 89.El 90.Pp --- 23 unchanged lines hidden (view full) --- 114the network connection (cable). 115.It "vr%d: no memory for rx list" 116The driver failed to allocate an mbuf for the receiver ring. 117.It "vr%d: no memory for tx list" 118The driver failed to allocate an mbuf for the transmitter ring when 119allocating a pad buffer or collapsing an mbuf chain into a cluster. 120.It "vr%d: chip is in D3 power state -- setting to D0" 121This message applies only to adapters which support power | 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 --- 23 unchanged lines hidden (view full) --- 120the network connection (cable). 121.It "vr%d: no memory for rx list" 122The driver failed to allocate an mbuf for the receiver ring. 123.It "vr%d: no memory for tx list" 124The driver failed to allocate an mbuf for the transmitter ring when 125allocating a pad buffer or collapsing an mbuf chain into a cluster. 126.It "vr%d: chip is in D3 power state -- setting to D0" 127This message applies only to adapters which support power |
| 122management. Some operating systems place the controller in low power | 128management. 129Some operating systems place the controller in low power |
| 123mode when shutting down, and some PCI BIOSes fail to bring the chip | 130mode when shutting down, and some PCI BIOSes fail to bring the chip |
| 124out of this state before configuring it. The controller loses all of | 131out of this state before configuring it. 132The controller loses all of |
| 125its PCI configuration in the D3 state, so if the BIOS does not set 126it back to full power mode in time, it won't be able to configure it | 133its PCI configuration in the D3 state, so if the BIOS does not set 134it back to full power mode in time, it won't be able to configure it |
| 127correctly. The driver tries to detect this condition and bring | 135correctly. 136The driver tries to detect this condition and bring |
| 128the adapter back to the D0 (full power) state, but this may not be | 137the adapter back to the D0 (full power) state, but this may not be |
| 129enough to return the driver to a fully operational condition. If | 138enough to return the driver to a fully operational condition. 139If |
| 130you see this message at boot time and the driver fails to attach 131the device as a network interface, you will have to perform second 132warm boot to have the device properly configured. 133.Pp 134Note that this condition only occurs when warm booting from another | 140you see this message at boot time and the driver fails to attach 141the device as a network interface, you will have to perform second 142warm boot to have the device properly configured. 143.Pp 144Note that this condition only occurs when warm booting from another |
| 135operating system. If you power down your system prior to booting | 145operating system. 146If you power down your system prior to booting |
| 136.Fx , 137the card should be configured correctly. 138.El 139.Sh SEE ALSO 140.Xr arp 4 , 141.Xr netintro 4 , 142.Xr ifconfig 8 , 143.Xr ng_ether 8 --- 14 unchanged lines hidden (view full) --- 158.Sh BUGS 159The 160.Nm 161driver always copies transmit mbuf chains into longword-aligned 162buffers prior to transmission in order to pacify the Rhine chips. 163If buffers are not aligned correctly, the chip will round the 164supplied buffer address and begin DMAing from the wrong location. 165This buffer copying impairs transmit performance on slower systems but can't | 147.Fx , 148the card should be configured correctly. 149.El 150.Sh SEE ALSO 151.Xr arp 4 , 152.Xr netintro 4 , 153.Xr ifconfig 8 , 154.Xr ng_ether 8 --- 14 unchanged lines hidden (view full) --- 169.Sh BUGS 170The 171.Nm 172driver always copies transmit mbuf chains into longword-aligned 173buffers prior to transmission in order to pacify the Rhine chips. 174If buffers are not aligned correctly, the chip will round the 175supplied buffer address and begin DMAing from the wrong location. 176This buffer copying impairs transmit performance on slower systems but can't |
| 166be avoided. On faster machines (e.g. a Pentium II), the performance | 177be avoided. 178On faster machines (e.g. a Pentium II), the performance |
| 167impact is much less noticable. | 179impact is much less noticable. |