xref: /netbsd/share/man/man4/ti.4 (revision bf9ec67e)
1.\"	$NetBSD: ti.4,v 1.7 2001/09/22 16:36:23 wiz Exp $
2.\"
3.\" Copyright (c) 1997, 1998, 1999
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 Id: src/share/man/man4/ti.4,v 1.5 2000/01/23 16:13:24 asmodai Exp
34.\"
35.Dd June 2, 2001
36.Dt TI 4
37.Os
38.Sh NAME
39.Nm ti
40.Nd
41Alteon Networks Tigon I and Tigon II gigabit
42.Tn Ethernet
43driver
44.Sh SYNOPSIS
45.Cd "ti* at pci? dev ? function ?"
46.Sh DESCRIPTION
47The
48.Nm
49driver provides support for PCI gigabit
50.Tn Ethernet
51adapters based on the Alteon Networks Tigon gigabit
52.Tn Ethernet
53controller chip.  The Tigon contains an embedded R4000 CPU, gigabit MAC, dual
54DMA channels and a PCI interface unit.  The Tigon II contains two R4000 CPUs
55and other refinements.  Either chip can be used in either a 32-bit or 64-bit
56PCI slot.  Communication with the chip is achieved via PCI shared memory
57and bus master DMA.  The Tigon I and II support hardware multicast
58address filtering, VLAN tag extraction and insertion, and jumbo
59.Tn Ethernet
60frames sizes up to 9000 bytes.  Note that the Tigon I chipset is no longer in
61active production: all new adapters should come equipped with Tigon II
62chipsets.
63.Pp
64There are several PCI boards available from both Alteon and other
65vendors that use the Tigon chipset under OEM contract.  The
66.Nm
67driver has been tested with the following Tigon-based adapters:
68.Bl -bullet -offset indent
69.It
70The Alteon AceNIC V gigabit (1000baseSX and 1000baseT variants)
71.Tn Ethernet
72adapter
73.It
74The 3Com 3c985-SX gigabit
75.Tn Ethernet
76adapter
77.It
78The Netgear GA620 gigabit (1000baseSX and 1000baseT variants)
79.Tn Ethernet
80adapter
81.It
82The Digital EtherWORKS 1000SX PCI Gigabit Adapter (DEGPA)
83.El
84.Pp
85The following should also be supported but have not yet been tested:
86.Bl -bullet -offset indent
87.It
88Silicon Graphics PCI gigabit
89.Tn Ethernet
90adapter
91.El
92.Pp
93While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for
9410 and 100Mbps speeds is only available on boards with the proper
95transceivers.  Most adapters are only designed to work at 1000Mbps,
96however the driver should support those NICs that work at lower speeds
97as well.
98.Pp
99Support for jumbo frames is provided via the interface MTU setting.
100Selecting an MTU larger than 1500 bytes with the
101.Xr ifconfig 8
102utility configures the adapter to receive and transmit jumbo frames.
103Using jumbo frames can greatly improve performance for certain tasks,
104such as file transfers and data streaming.
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.
113.It 10baseT/UTP
114Set 10Mbps operation.  The
115.Ar mediaopt
116option can also be used to select either
117.Ar full-duplex
118or
119.Ar half-duplex modes .
120.It 100baseTX
121Set 100Mbps (fast
122.Tn Ethernet )
123operation.  The
124.Ar mediaopt
125option can also be used to select either
126.Ar full-duplex
127or
128.Ar half-duplex
129modes.
130.It 1000baseSX
131Set 1000Mbps (gigabit
132.Tn Ethernet over multimode fiber ) operation.  Only full
133.Ar full-duplex
134mode is supported at this speed.
135.It 1000baseT
136Set 1000Mbps (gigabit
137.Tn Ethernet over twisted pair ) operation.  Only full
138.Ar full-duplex
139mode is supported at this speed.
140.El
141.Pp
142The
143.Nm
144driver supports the following media options:
145.Pp
146.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
147.It full-duplex
148Force full duplex operation.
149.It half-duplex
150Force half duplex operation.
151.El
152.Pp
153The Algeon Tigon and Tigon II support IPv4/TCP/UDP checksumming in
154hardware.
155The
156.Nm
157supports this feature of the chip's firmware.  See
158.Xr ifconfig 8
159for information on how to enable this feature.
160.Pp
161For more information on configuring this device, see
162.Xr ifconfig 8 .
163.Sh DIAGNOSTICS
164.Bl -diag
165.It "ti%d: can't map memory space"
166A fatal initialization error has occurred.
167.It "ti%d: couldn't map / establish interrupt"
168A fatal initialization error has occurred.
169.It "ti%d: jumbo buffer allocation failed"
170The driver failed to allocate memory for jumbo frames during
171initialization.
172.It "ti%d: bios thinks we're in a 64 bit slot, but we aren't"
173The BIOS has programmed the NIC as though it had been installed in
174a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot.  This happens
175as a result of a bug in some BIOSes.  This 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.  The
182.Nm
183driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips
184and has firmware only for those devices.
185.It "ti%d: watchdog timeout"
186The device has stopped responding to the network, or there is a problem with
187the network connection (cable).
188.El
189.Sh SEE ALSO
190.Xr netintro 4 ,
191.Xr pci 4 ,
192.Xr ifconfig 8
193.Rs
194.%T Alteon Gigabit Ethernet/PCI NIC manuals
195.%O http://www.alteon.com/support/openkits
196.Re
197.Sh HISTORY
198The
199.Nm
200device driver first appeared in
201.Nx 1.4.2 .
202.Sh AUTHORS
203The
204.Nm
205driver was written by
206.An Bill Paul Aq wpaul@ctr.columbia.edu .
207.Sh BUGS
208The driver currently tries to access some on-board memory transparently.
209This mapping (BUS_SPACE_MAP_LINEAR) fails on systems where the corresponding
210PCI memory range is located in "sparse" space only.
211.Pp
212This driver currently does not work on big-endian systems.
213