| ti.4 (56612) | ti.4 (57676) |
|---|---|
| 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. --- 14 unchanged lines hidden (view full) --- 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.\" | 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. --- 14 unchanged lines hidden (view full) --- 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: head/share/man/man4/ti.4 56612 2000-01-25 20:34:43Z archie $ | 31.\" $FreeBSD: head/share/man/man4/ti.4 57676 2000-03-01 14:50:24Z sheldonh $ |
| 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 | 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. The Tigon | 46the Alteon Networks Tigon gigabit ethernet controller chip. 47The Tigon |
| 47contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and | 48contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and |
| 48a PCI interface unit. The Tigon II contains two R4000 CPUs and other 49refinements. Either chip can be used in either a 32-bit or 64-bit PCI 50slot. Communication with the chip is achieved via PCI shared memory 51and bus master DMA. The Tigon I and II support hardware multicast | 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 |
| 52address filtering, VLAN tag extraction and insertion, and jumbo | 57address filtering, VLAN tag extraction and insertion, and jumbo |
| 53ethernet frames sizes up to 9000 bytes. Note that the Tigon I chipset | 58ethernet frames sizes up to 9000 bytes. 59Note that the Tigon I chipset |
| 54is no longer in active production: all new adapters should come equipped 55with Tigon II chipsets. 56.Pp 57There are several PCI boards available from both Alteon and other | 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 |
| 58vendors that use the Tigon chipset under OEM contract. The | 64vendors that use the Tigon chipset under OEM contract. 65The |
| 59.Nm 60driver has been tested with the following Tigon-based adapters: 61.Bl -bullet -offset indent 62.It 63The Alteon AceNIC V gigabit ethernet adapter 64.It 65The 3Com 3c985-SX gigabit ethernet adapter 66.It --- 5 unchanged lines hidden (view full) --- 72.It 73The Digital EtherWORKS 1000SX PCI Gigabit Adapter 74.It 75Silicon Graphics PCI gigabit ethernet adapter 76.El 77.Pp 78While the Tigon chipset supports 10, 100 and 1000Mbps speeds, support for 7910 and 100Mbps speeds is only available on boards with the proper | 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 --- 5 unchanged lines hidden (view full) --- 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 |
| 80transceivers. Most adapters are only designed to work at 1000Mbps, | 87transceivers. 88Most adapters are only designed to work at 1000Mbps, |
| 81however the driver should support those NICs that work at lower speeds 82as well. 83.Pp 84Support for jumbo frames is provided via the interface MTU setting. 85Selecting an MTU larger than 1500 bytes with the 86.Xr ifconfig 8 87utility configures the adapter to receive and transmit jumbo frames. 88Using jumbo frames can greatly improve performance for certain tasks, 89such as file transfers and data streaming. 90.Pp 91Support for vlans is also available using the 92.Xr vlan 4 | 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 |
| 93mechanism. See the | 101mechanism. 102See the |
| 94.Xr vlan 4 95man page for more details. 96.Pp 97The 98.Nm 99driver supports the following media types: 100.Pp 101.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 102.It autoselect 103Enable autoselection of the media type and options. 104The user can manually override 105the autoselected mode by adding media options to the 106.Pa /etc/rc.conf 107file. 108.It 10baseT/UTP | 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 |
| 109Set 10Mbps operation. The | 118Set 10Mbps operation. 119The |
| 110.Ar mediaopt 111option can also be used to select either 112.Ar full-duplex 113or 114.Ar half-duplex modes. 115.It 100baseTX | 120.Ar mediaopt 121option can also be used to select either 122.Ar full-duplex 123or 124.Ar half-duplex modes. 125.It 100baseTX |
| 116Set 100Mbps (fast ethernet) operation. The | 126Set 100Mbps (fast ethernet) operation. 127The |
| 117.Ar mediaopt 118option can also be used to select either 119.Ar full-duplex 120or 121.Ar half-duplex 122modes. 123.It 1000baseSX | 128.Ar mediaopt 129option can also be used to select either 130.Ar full-duplex 131or 132.Ar half-duplex 133modes. 134.It 1000baseSX |
| 124Set 1000Mbps (gigabit ethernet) operation. Only full | 135Set 1000Mbps (gigabit ethernet) operation. 136Only full |
| 125.Ar full-duplex 126mode is supported at this speed. 127.El 128.Pp 129The 130.Nm 131driver supports the following media options: 132.Pp --- 11 unchanged lines hidden (view full) --- 144.It "ti%d: couldn't map memory" 145A fatal initialization error has occurred. 146.It "ti%d: couldn't map interrupt" 147A fatal initialization error has occurred. 148.It "ti%d: no memory for softc struct!" 149The driver failed to allocate memory for per-device instance information 150during initialization. 151.It "ti%d: failed to enable memory mapping!" | 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 --- 11 unchanged lines hidden (view full) --- 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!" |
| 152The driver failed to initialize PCI shared memory mapping. This might | 164The driver failed to initialize PCI shared memory mapping. 165This might |
| 153happen if the card is not in a bus-master slot. 154.It "ti%d: no memory for jumbo buffers!" 155The driver failed to allocate memory for jumbo frames during 156initialization. 157.It "ti%d: bios thinks we're in a 64 bit slot, but we aren't" 158The BIOS has programmed the NIC as though it had been installed in | 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 |
| 159a 64-bit PCI slot, but in fact the NIC is in a 32-bit slot. This happens 160as a result of a bug in some BIOSes. This can be worked around on the | 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 |
| 161Tigon II, but on the Tigon I initialization will fail. 162.It "ti%d: board self-diagnostics failed!" 163The ROMFAIL bit in the CPU state register was set after system 164startup, indicating that the on-board NIC diagnostics failed. 165.It "ti%d: unknown hwrev" | 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" |
| 166The driver detected a board with an unsupported hardware revision. The | 181The driver detected a board with an unsupported hardware revision. 182The |
| 167.Nm 168driver supports revision 4 (Tigon 1) and revision 6 (Tigon 2) chips 169and has firmware only for those devices. 170.It "ti%d: watchdog timeout" 171The device has stopped responding to the network, or there is a problem with 172the network connection (cable). 173.El 174.Sh SEE ALSO --- 19 unchanged lines hidden --- | 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 --- 19 unchanged lines hidden --- |