1.\" $OpenBSD: ti.4,v 1.36 2009/08/30 05:42:14 jmc 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: src/share/man/man4/ti.4,v 1.11 2000/08/10 19:47:32 billf Exp $ 34.\" 35.Dd $Mdocdate: August 30 2009 $ 36.Dt TI 4 37.Os 38.Sh NAME 39.Nm ti 40.Nd Alteon Networks Tigon I and II Gigabit Ethernet device 41.Sh SYNOPSIS 42.Cd "ti* at pci?" 43.Cd "ti* at sbus?" 44.Sh DESCRIPTION 45The 46.Nm 47driver provides support for PCI Gigabit Ethernet adapters based on 48the Alteon Networks Tigon Gigabit Ethernet controller chip. 49The Tigon contains an embedded R4000 CPU, Gigabit MAC, dual DMA channels and 50a PCI interface unit. 51The Tigon II contains two R4000 CPUs and other refinements. 52Either chip can be used in either a 32-bit or 64-bit PCI slot. 53Communication with the chip is achieved via PCI shared memory and 54bus master DMA. 55SBus cards are also available and use a special bridge chip. 56The Tigon I and II support hardware multicast address filtering, 57VLAN tag insertion and stripping, and Jumbo frame sizes up to 589000 bytes. 59Note that the Tigon I chipset is no longer in active production: all new 60adapters should come equipped with Tigon II chipsets. 61.Pp 62There are several PCI boards available from both Alteon and other 63vendors that use the Tigon chipset under OEM contract. 64The 65.Nm 66driver has been tested with the following Tigon-based adapters: 67.Pp 68.Bl -bullet -compact -offset indent 69.It 703Com 3C985-SX Gigabit Ethernet (Tigon 1) 71.It 723Com 3C985B-SX Gigabit Ethernet (Tigon 2) 73.It 74Alteon AceNIC V Gigabit Ethernet (1000baseSX) 75.It 76Alteon AceNIC V Gigabit Ethernet (1000baseT) 77.It 78Digital EtherWORKS 1000SX PCI Gigabit Ethernet (1000baseSX) 79.It 80Netgear GA620 Gigabit Ethernet (1000baseSX) 81.It 82Netgear GA620T Gigabit Ethernet (1000baseT) 83.It 84Sun Vector Gigabit Ethernet (1000baseSX) 85.El 86.Pp 87The following should also be supported but have not yet been tested: 88.Pp 89.Bl -bullet -compact -offset indent 90.It 91Farallon PN9000SX Gigabit Ethernet 92.It 93Silicon Graphics PCI Gigabit Ethernet 94.El 95.Pp 96While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for 9710 and 100Mbps speeds is only available on boards with the proper 98transceivers. 99Most adapters are only designed to work at 1000Mbps, however the driver 100should support those NICs that work at lower speeds as well. 101.Pp 102Support for Jumbo frames is provided via the interface MTU setting. 103Selecting an MTU larger than 1500 bytes with the 104.Xr ifconfig 8 105utility configures the adapter to receive and transmit Jumbo frames. 106Using Jumbo frames can greatly improve performance for certain tasks, 107such as file transfers and data streaming. 108.Pp 109The 110.Nm 111driver supports the following media types: 112.Bl -tag -width full-duplex 113.It autoselect 114Enable autoselection of the media type and options. 115The user can manually override 116the autoselected mode by adding media options to the appropriate 117.Xr hostname.if 5 118file. 119.It 10baseT 120Set 10Mbps operation 121The 122.Ar mediaopt 123option can also be used to select either 124.Ar full-duplex 125or 126.Ar half-duplex 127modes. 128.It 100baseTX 129Set 100Mbps (Fast Ethernet) operation. 130The 131.Ar mediaopt 132option can also be used to select either 133.Ar full-duplex 134or 135.Ar half-duplex 136modes. 137.It 1000baseSX 138Set 1000Mbps (Gigabit Ethernet) on fiber operation. 139Only 140.Ar full-duplex 141mode is supported at this speed. 142.It 1000baseT 143Set 1000Mbps (Gigabit Ethernet) on copper operation. 144.El 145.Pp 146The 147.Nm 148driver supports the following media options: 149.Bl -tag -width full-duplex 150.It full-duplex 151Force full duplex operation 152.It half-duplex 153Force half duplex operation 154.El 155.Pp 156For more information on configuring this device, see 157.Xr ifconfig 8 . 158.Sh FILES 159Two firmware files are necessary, for Tigon 1 and Tigon 2 devices. 160These are loaded on demand 161when the device is attached: 162.Pp 163.Bl -tag -width Ds -offset indent -compact 164.It Pa /etc/firmware/tigon1 165.It Pa /etc/firmware/tigon2 166.El 167.Sh DIAGNOSTICS 168.Bl -diag 169.It "ti%d: couldn't map memory" 170A fatal initialization error has occurred. 171.It "ti%d: couldn't map interrupt" 172A fatal initialization error has occurred. 173.It "ti%d: no memory for softc struct!" 174The driver failed to allocate memory for per-device instance information 175during initialization. 176.It "ti%d: failed to enable memory mapping!" 177The driver failed to initialize PCI shared memory mapping. 178This might happen if the card is not in a bus-master slot. 179.It "ti%d: no memory for jumbo buffers!" 180The driver failed to allocate memory for Jumbo frames during 181initialization. 182.It "ti%d: bios thinks we're in a 64 bit slot, but we aren't" 183The BIOS has programmed the NIC as though it had been installed in 184a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot. 185This happens as a result of a bug in some BIOSes. 186This can be worked around on the Tigon II, but 187on the Tigon I initialization will fail. 188.It "ti%d: board self-diagnostics failed!" 189The ROMFAIL bit in the CPU state register was set after system 190startup, indicating that the on-board NIC diagnostics failed. 191.It "ti%d: unknown hwrev" 192The driver detected a board with an unsupported hardware revision. 193The 194.Nm 195driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips 196and has firmware only for those devices. 197.It "ti%d: watchdog timeout" 198The device has stopped responding to the network, or there is a problem with 199the network connection (cable). 200.El 201.Sh SEE ALSO 202.Xr arp 4 , 203.Xr ifmedia 4 , 204.Xr intro 4 , 205.Xr netintro 4 , 206.Xr pci 4 , 207.Xr sbus 4 , 208.Xr hostname.if 5 , 209.Xr ifconfig 8 210.Sh HISTORY 211The 212.Nm 213device driver first appeared in 214.Fx 3.0 . 215.Ox 216support first appeared in 217.Ox 2.6 . 218SBus support was added in 219.Ox 4.7 . 220.Sh AUTHORS 221.An -nosplit 222The 223.Nm 224driver was written by 225.An Bill Paul Aq wpaul@bsdi.com . 226SBus support was added by 227.An Mark Kettenis Aq kettenis@openbsd.org . 228