ti.4 (79727) | ti.4 (98849) |
---|---|
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 79727 2001-07-14 19:41:16Z schweikh $ | 31.\" $FreeBSD: head/share/man/man4/ti.4 98849 2002-06-26 03:37:47Z ken $ |
32.\" 33.Dd March 4, 1999 34.Dt TI 4 35.Os 36.Sh NAME 37.Nm ti 38.Nd "Alteon Networks Tigon I and Tigon II gigabit ethernet driver" 39.Sh SYNOPSIS 40.Cd "device ti" | 32.\" 33.Dd March 4, 1999 34.Dt TI 4 35.Os 36.Sh NAME 37.Nm ti 38.Nd "Alteon Networks Tigon I and Tigon II gigabit ethernet driver" 39.Sh SYNOPSIS 40.Cd "device ti" |
41.Cd "options TI_PRIVATE_JUMBOS" 42.Cd "options TI_JUMBO_HDRSPLIT" |
|
41.Sh DESCRIPTION 42The 43.Nm 44driver provides support for PCI gigabit ethernet adapters based on 45the Alteon Networks Tigon gigabit ethernet controller chip. 46The Tigon 47contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and 48a PCI interface unit. --- 55 unchanged lines hidden (view full) --- 104.Pp 105Support for jumbo frames is provided via the interface MTU setting. 106Selecting an MTU larger than 1500 bytes with the 107.Xr ifconfig 8 108utility configures the adapter to receive and transmit jumbo frames. 109Using jumbo frames can greatly improve performance for certain tasks, 110such as file transfers and data streaming. 111.Pp | 43.Sh DESCRIPTION 44The 45.Nm 46driver provides support for PCI gigabit ethernet adapters based on 47the Alteon Networks Tigon gigabit ethernet controller chip. 48The Tigon 49contains an embedded R4000 CPU, gigabit MAC, dual DMA channels and 50a PCI interface unit. --- 55 unchanged lines hidden (view full) --- 106.Pp 107Support for jumbo frames is provided via the interface MTU setting. 108Selecting an MTU larger than 1500 bytes with the 109.Xr ifconfig 8 110utility configures the adapter to receive and transmit jumbo frames. 111Using jumbo frames can greatly improve performance for certain tasks, 112such as file transfers and data streaming. 113.Pp |
114Header splitting support for Tigon 2 boards (this option has no effect for 115the Tigon 1) can be turned on with the 116.Dv TI_JUMBO_HDRSPLIT 117option. See 118.Xr zero_copy 9 119for more discussion on zero copy receive and header splitting. 120.Pp 121The 122.Nm 123driver normally uses jumbo receive buffers allocated by the 124.Xr jumbo 9 125buffer allocator, but can be configured to use its own private pool of 126jumbo buffers that are contiguous instead of buffers from the jumbo 127allocator, which are made up of multiple page sized chunks. To turn on 128private jumbos, use the 129.Dv TI_PRIVATE_JUMBOS 130option. 131.Pp |
|
112Support for vlans is also available using the 113.Xr vlan 4 114mechanism. 115See the 116.Xr vlan 4 117man page for more details. 118.Pp 119The --- 40 unchanged lines hidden (view full) --- 160.It full-duplex 161Force full duplex operation 162.It half-duplex 163Force half duplex operation. 164.El 165.Pp 166For more information on configuring this device, see 167.Xr ifconfig 8 . | 132Support for vlans is also available using the 133.Xr vlan 4 134mechanism. 135See the 136.Xr vlan 4 137man page for more details. 138.Pp 139The --- 40 unchanged lines hidden (view full) --- 180.It full-duplex 181Force full duplex operation 182.It half-duplex 183Force half duplex operation. 184.El 185.Pp 186For more information on configuring this device, see 187.Xr ifconfig 8 . |
188.Sh IOCTLS 189In addition to the standard 190.Xr socket 2 191.Xr ioctl 2 192calls implemented by most network drivers, the 193.Nm 194driver also includes a character device interface that can be used for 195additional diagnostics, configuration and debugging. With this character 196device interface, and a specially patched version of gdb, the user can 197debug firmware running on the Tigon board. 198.Pp 199These ioctls and their arguments are defined in the 200.Aq Pa sys/tiio.h 201header file. 202.Bl -tag -width ALT_WRITE_TG_MEM 203.It Dv TIIOCGETSTATS 204Return card statistics DMAed from the card into kernel memory approximately 205every 2 seconds. (That time interval can be changed via the 206.Dv TIIOCSETPARAMS 207ioctl.) The argument is 208.Va struct ti_stats . 209.It Dv TIIOCGETPARAMS 210Get various performance-related firmware parameters that largely affect how 211interrupts are coalesced. The argument is 212.Va struct ti_params . 213.It Dv TIIOCSETPARAMS 214Set various performance-related firmware parameters that largely affect how 215interrupts are coalesced. The argument is 216.Va struct ti_params . 217.It Dv TIIOCSETTRACE 218Tell the NIC to trace the requested types of information. 219The argument is 220.Va ti_trace_type . 221.It Dv TIIOCGETTRACE 222Dump the trace buffer from the card. The argument is 223.Va struct ti_trace_buf . 224.It Dv ALT_ATTACH 225This ioctl is used for compatibility with Alteon's Solaris driver. They 226apparantly only have one character interface for debugging, so they have 227to tell it which Tigon instance they want to debug. This ioctl is a noop 228for FreeBSD. 229.It Dv ALT_READ_TG_MEM 230Read the requested memory region from the Tigon board. The argument is 231.Va struct tg_mem . 232.It Dv ALT_WRITE_TG_MEM 233Write to the requested memory region on the Tigon board. The argument is 234.Va struct tg_mem . 235.It Dv ALT_READ_TG_REG 236Read the requested register on the Tigon board. The argument is 237.Va struct tg_reg . 238.It Dv ALT_WRITE_TG_REG 239Write to the requested register on the Tigon board. The argument is 240.Va struct tg_reg . 241.El 242.Sh FILES 243.Bl -tag -width /dev/ti[0-255] -compact 244.It Pa /dev/ti[0-255] 245Tigon driver character interface. |
|
168.Sh DIAGNOSTICS 169.Bl -diag 170.It "ti%d: couldn't map memory" 171A fatal initialization error has occurred. 172.It "ti%d: couldn't map interrupt" 173A fatal initialization error has occurred. 174.It "ti%d: no memory for softc struct!" 175The driver failed to allocate memory for per-device instance information --- 25 unchanged lines hidden (view full) --- 201The device has stopped responding to the network, or there is a problem with 202the network connection (cable). 203.El 204.Sh SEE ALSO 205.Xr arp 4 , 206.Xr netintro 4 , 207.Xr ng_ether 4 , 208.Xr vlan 4 , | 246.Sh DIAGNOSTICS 247.Bl -diag 248.It "ti%d: couldn't map memory" 249A fatal initialization error has occurred. 250.It "ti%d: couldn't map interrupt" 251A fatal initialization error has occurred. 252.It "ti%d: no memory for softc struct!" 253The driver failed to allocate memory for per-device instance information --- 25 unchanged lines hidden (view full) --- 279The device has stopped responding to the network, or there is a problem with 280the network connection (cable). 281.El 282.Sh SEE ALSO 283.Xr arp 4 , 284.Xr netintro 4 , 285.Xr ng_ether 4 , 286.Xr vlan 4 , |
209.Xr ifconfig 8 | 287.Xr ifconfig 8 , 288.Xr zero_copy 9 , 289.Xr jumbo 9 |
210.Rs 211.%T Alteon Gigabit Ethernet/PCI NIC manuals 212.%O http://sanjose.alteon.com/open.shtml 213.Re 214.Sh HISTORY 215The 216.Nm 217device driver first appeared in 218.Fx 3.0 . 219.Sh AUTHORS 220The 221.Nm 222driver was written by 223.An Bill Paul Aq wpaul@bsdi.com . | 290.Rs 291.%T Alteon Gigabit Ethernet/PCI NIC manuals 292.%O http://sanjose.alteon.com/open.shtml 293.Re 294.Sh HISTORY 295The 296.Nm 297device driver first appeared in 298.Fx 3.0 . 299.Sh AUTHORS 300The 301.Nm 302driver was written by 303.An Bill Paul Aq wpaul@bsdi.com . |
304The header splitting firmware modifications, character ioctl interface and 305debugging support were written by 306.An Kenneth Merry Aq ken@FreeBSD.org . 307Initial zero copy support was written by 308.An Andrew Gallatin Aq gallatin@FreeBSD.org . |
|