xref: /freebsd/share/man/man4/vge.4 (revision 63f9a4cb2684a303e3eb2ffed39c03a2e2b28ae0)
1.\" Copyright (c) 2004
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.\"
33.Dd November 24, 2004
34.Dt VGE 4
35.Os
36.Sh NAME
37.Nm vge
38.Nd "VIA Networking Technologies VT6122 PCI Gigabit Ethernet adapter driver"
39.Sh SYNOPSIS
40.Cd "device miibus"
41.Cd "device vge"
42.Sh DESCRIPTION
43The
44.Nm
45driver provides support for various NICs and embedded Ethernet interfaces
46based on the VIA Networking Technologies VT6122 Gigabit Ethernet
47controller chips.
48.Pp
49The VT6122 is a 33/66Mhz 64-bit PCI device which combines a tri-speed MAC with
50an integrated 10/100/1000 copper PHY. (Some older cards use an external
51PHY.)
52The MAC supports TCP/IP hardware
53checksums (IPv4 only), TCP large send, VLAN tag insertion and stripping,
54as well as VLAN filtering, a 64-entry CAM filter and a 64-entry VLAN filter,
5564-bit multicast hash filter, 4 separate transmit DMA queues, flow control
56and jumbo frames up to 16K in size.
57The VT6122 has a 16K receive FIFO and 48K transmit FIFO.
58.Pp
59The
60.Nm
61driver takes advantage of the VT6122's checksum offload and VLAN
62tagging features, as well as the jumbo frame and CAM filter support.
63The CAM filter is used for multicast address filtering to provide
6464 perfect multicast address filter support.
65If it is necessary for the interface to join more than 64 multicast
66groups, the driver will switch over to using the hash filter.
67.Pp
68The jumbo frame support can be enabled by setting the interface MTU
69to any value larger than the default of 1500 bytes, up to a maximum
70of 9000 bytes.
71The receive and transmit checksum offload support
72can be toggled on and off using the
73.Xr ifconfig 8
74utility.
75.Pp
76The
77.Nm
78driver supports the following media types:
79.Bl -tag -width 10baseTXUTP
80.It Cm autoselect
81Enable autoselection of the media type and options.
82The user can manually override
83the autoselected mode by adding media options to
84.Xr rc.conf 5 .
85.It Cm 10baseT/UTP
86Set 10Mbps operation.
87The
88.Xr ifconfig 8
89.Ic mediaopt
90option can also be used to select either
91.Cm full-duplex
92or
93.Cm half-duplex
94modes.
95.It Cm 100baseTX
96Set 100Mbps (Fast Ethernet) 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 1000baseTX
106Set 1000baseTX operation over twisted pair.
107.Cm full-duplex
108and
109.Cm half-duplex
110modes are supported.
111.El
112.Pp
113The
114.Nm
115driver supports the following media options:
116.Bl -tag -width full-duplex
117.It Cm full-duplex
118Force full duplex operation.
119.It Cm half-duplex
120Force half duplex operation.
121.El
122.Pp
123The
124.Nm
125driver also supports one special link option for 1000baseTX cards:
126.Bl -tag -width link0
127.It Cm link0
128With 1000baseTX cards, establishing a link between two ports requires
129that one port be configured as a master and the other a slave.
130With autonegotiation,
131the master/slave settings will be chosen automatically.
132However when manually selecting the link state, it is necessary to
133force one side of the link to be a master and the other a slave.
134The
135.Nm
136driver configures the ports as slaves by default.
137Setting the
138.Cm link0
139flag with
140.Xr ifconfig 8
141will set a port as a master instead.
142.El
143.Pp
144For more information on configuring this device, see
145.Xr ifconfig 8 .
146.Sh HARDWARE
147The
148.Nm
149driver supports VIA Networking VT3119 and VT6122 based
150Gigabit Ethernet adapters including:
151.Pp
152.Bl -bullet -compact
153.It
154VIA Networking LAN-on-motherboard Gigabit Ethernet
155.It
156ZyXEL GN650-T 64-bit PCI Gigabit Ethernet NIC (ZX1701)
157.It
158ZyXEL GN670-T 32-bit PCI Gigabit Ethernet NIC (ZX1702)
159.El
160.Sh DIAGNOSTICS
161.Bl -diag
162.It "vge%d: couldn't map memory"
163A fatal initialization error has occurred.
164.It "vge%d: couldn't map ports"
165A fatal initialization error has occurred.
166.It "vge%d: couldn't map interrupt"
167A fatal initialization error has occurred.
168.It "vge%d: failed to enable memory mapping!"
169The driver failed to initialize PCI shared memory mapping.
170This might
171happen if the card is not in a bus-master slot.
172.It "vge%d: watchdog timeout"
173The device has stopped responding to the network, or there is a problem with
174the network connection (cable).
175.El
176.Sh SEE ALSO
177.Xr arp 4 ,
178.Xr miibus 4 ,
179.Xr netintro 4 ,
180.Xr ng_ether 4 ,
181.Xr polling 4 ,
182.Xr vlan 4 ,
183.Xr ifconfig 8
184.Sh HISTORY
185The
186.Nm
187device driver first appeared in
188.Fx 5.3 .
189.Sh AUTHORS
190The
191.Nm
192driver was written by
193.An Bill Paul Aq wpaul@windriver.com .
194