xref: /freebsd/share/man/man4/ti.4 (revision 23f282aa31e9b6fceacd449020e936e98d6f2298)
1.\" Copyright (c) 1997, 1998, 1999
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$
32.\"
33.Dd March 4, 1999
34.Dt TI 4
35.Os FreeBSD
36.Sh NAME
37.Nm ti
38.Nd
39Alteon Networks Tigon I and Tigon II gigabit ethernet driver
40.Sh SYNOPSIS
41.Cd "device ti"
42.Sh DESCRIPTION
43The
44.Nm
45driver provides support for PCI gigabit ethernet adapters based on
46the Alteon Networks Tigon gigabit ethernet controller chip.
47The Tigon
48contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and
49a PCI interface unit.
50The Tigon II contains two R4000 CPUs and other
51refinements.
52Either chip can be used in either a 32-bit or 64-bit PCI
53slot.
54Communication with the chip is achieved via PCI shared memory
55and bus master DMA.
56The Tigon I and II support hardware multicast
57address filtering, VLAN tag extraction and insertion, and jumbo
58ethernet frames sizes up to 9000 bytes.
59Note that the Tigon I chipset
60is no longer in active production: all new adapters should come equipped
61with Tigon II chipsets.
62.Pp
63There are several PCI boards available from both Alteon and other
64vendors that use the Tigon chipset under OEM contract.
65The
66.Nm
67driver has been tested with the following Tigon-based adapters:
68.Bl -bullet -offset indent
69.It
70The Alteon AceNIC V gigabit ethernet adapter
71.It
72The 3Com 3c985-SX gigabit ethernet adapter
73.It
74The Netgear GA620 gigabit ethernet adapter
75.El
76.Pp
77The following should also be supported but have not yet been tested:
78.Bl -bullet -offset indent
79.It
80The Digital EtherWORKS 1000SX PCI Gigabit Adapter
81.It
82Silicon Graphics PCI gigabit ethernet adapter
83.El
84.Pp
85While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for
8610 and 100Mbps speeds is only available on boards with the proper
87transceivers.
88Most adapters are only designed to work at 1000Mbps,
89however the driver should support those NICs that work at lower speeds
90as well.
91.Pp
92Support for jumbo frames is provided via the interface MTU setting.
93Selecting an MTU larger than 1500 bytes with the
94.Xr ifconfig 8
95utility configures the adapter to receive and transmit jumbo frames.
96Using jumbo frames can greatly improve performance for certain tasks,
97such as file transfers and data streaming.
98.Pp
99Support for vlans is also available using the
100.Xr vlan 4
101mechanism.
102See the
103.Xr vlan 4
104man page for more details.
105.Pp
106The
107.Nm
108driver supports the following media types:
109.Pp
110.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
111.It autoselect
112Enable autoselection of the media type and options.
113The user can manually override
114the autoselected mode by adding media options to the
115.Pa /etc/rc.conf
116file.
117.It 10baseT/UTP
118Set 10Mbps operation.
119The
120.Ar mediaopt
121option can also be used to select either
122.Ar full-duplex
123or
124.Ar half-duplex modes.
125.It 100baseTX
126Set 100Mbps (fast ethernet) operation.
127The
128.Ar mediaopt
129option can also be used to select either
130.Ar full-duplex
131or
132.Ar half-duplex
133modes.
134.It 1000baseSX
135Set 1000Mbps (gigabit ethernet) operation.
136Only full
137.Ar full-duplex
138mode is supported at this speed.
139.El
140.Pp
141The
142.Nm
143driver supports the following media options:
144.Pp
145.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
146.It full-duplex
147Force full duplex operation
148.It half-duplex
149Force half duplex operation.
150.El
151.Pp
152For more information on configuring this device, see
153.Xr ifconfig 8 .
154.Sh DIAGNOSTICS
155.Bl -diag
156.It "ti%d: couldn't map memory"
157A fatal initialization error has occurred.
158.It "ti%d: couldn't map interrupt"
159A fatal initialization error has occurred.
160.It "ti%d: no memory for softc struct!"
161The driver failed to allocate memory for per-device instance information
162during initialization.
163.It "ti%d: failed to enable memory mapping!"
164The driver failed to initialize PCI shared memory mapping.
165This might
166happen if the card is not in a bus-master slot.
167.It "ti%d: no memory for jumbo buffers!"
168The driver failed to allocate memory for jumbo frames during
169initialization.
170.It "ti%d: bios thinks we're in a 64 bit slot, but we aren't"
171The BIOS has programmed the NIC as though it had been installed in
172a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot.
173This happens
174as a result of a bug in some BIOSes.
175This can be worked around on the
176Tigon II, but on the Tigon I initialization will fail.
177.It "ti%d: board self-diagnostics failed!"
178The ROMFAIL bit in the CPU state register was set after system
179startup, indicating that the on-board NIC diagnostics failed.
180.It "ti%d: unknown hwrev"
181The driver detected a board with an unsupported hardware revision.
182The
183.Nm
184driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips
185and has firmware only for those devices.
186.It "ti%d: watchdog timeout"
187The device has stopped responding to the network, or there is a problem with
188the network connection (cable).
189.El
190.Sh SEE ALSO
191.Xr arp 4 ,
192.Xr netintro 4 ,
193.Xr vlan 4 ,
194.Xr ifconfig 8 ,
195.Xr ng_ether 8
196.Rs
197.%T Alteon Gigabit Ethernet/PCI NIC manuals
198.%O http://www.alteon.com/support/openkits
199.Re
200.Sh HISTORY
201The
202.Nm
203device driver first appeared in
204.Fx 3.0 .
205.Sh AUTHORS
206The
207.Nm
208driver was written by
209.An Bill Paul Aq wpaul@ctr.columbia.edu .
210