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