1.\" Copyright (c) 1997, 1998 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. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by Bill Paul. 15.\" 4. Neither the name of the author nor the names of any co-contributors 16.\" may be used to endorse or promote products derived from this software 17.\" without specific prior written permission. 18.\" 19.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND 20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 22.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD 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: src/share/man/man4/tl.4,v 1.10.2.4 2003/02/17 21:20:39 trhodes Exp $ 32.\" $DragonFly: src/share/man/man4/tl.4,v 1.4 2007/05/17 08:19:01 swildner Exp $ 33.\" 34.Dd May 1, 1998 35.Dt TL 4 36.Os 37.Sh NAME 38.Nm tl 39.Nd Texas Instruments ThunderLAN ethernet device driver 40.Sh SYNOPSIS 41.Cd "device miibus" 42.Cd "device tl" 43.Sh DESCRIPTION 44The 45.Nm 46driver provides support for PCI ethernet adapters based on the Texas 47Instruments ThunderLAN ethernet controller chip. 48This includes a large 49number of Compaq PCI-bus ethernet adapters as well as the integrated 50ethernet controllers built in to several models of Compaq Prosignia 51servers and Compaq Deskpro desktop machines. 52This driver also supports 53the Olicom OC-2135/2138, OC-2325 and OC-2326 10/100 TX UTP adapters 54and the Racore 8165 10/100baseTX and 8148 10baseT/100baseTX/100baseFX 55multi-personality cards. 56.Pp 57The ThunderLAN controller has a standard MII interface that supports 58up to 32 physical interface devices (PHYs). It also has a built-in 5910baseT PHY hardwired at MII address 31, which may be used in some 6010Mbps-only hardware configurations. 61In 100Mbps configurations, a 62National Semiconductor DP83840A or other MII-compliant PHY may be 63attached to the ThunderLAN's MII bus. 64If a DP83840A or equivalent 65is available, the ThunderLAN chip can operate at either 100Mbps or 6610Mbps in either half-duplex or full-duplex modes. 67The ThunderLAN's 68built-in PHY and the DP83840A also support autonegotiation. 69.Pp 70The 71.Nm 72driver supports the following media types: 73.Pp 74.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 75.It autoselect 76Enable autoselection of the media type and options. 77Note that this 78option is only available on those PHYs that support autonegotiation. 79Also, the PHY will not advertise those modes that have been explicitly 80disabled using the following media options. 81.It 10baseT/UTP 82Set 10Mbps operation 83.It 100baseTX 84Set 100Mbps (fast ethernet) operation 85.It 10base5/AUI 86Enable AUI/BNC interface (useful only with the built-in PHY). 87.El 88.Pp 89The 90.Nm 91driver supports the following media options: 92.Pp 93.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 94.It full-duplex 95Force full duplex operation 96.It half-duplex 97Force half duplex operation. 98.It hw-loopback 99Enable hardware loopback mode. 100.El 101.Pp 102Note that the 100baseTX media type is only available if supported 103by the PHY. 104For more information on configuring this device, see 105.Xr ifconfig 8 . 106.Sh DIAGNOSTICS 107.Bl -diag 108.It "tl%d: couldn't map memory" 109A fatal initialization error has occurred. 110.It "tl%d: couldn't map interrupt" 111A fatal initialization error has occurred. 112.It "tl%d: device timeout" 113The device has stopped responding to the network, or there is a problem with 114the network connection (cable). 115.It "tl%d: no memory for rx list" 116The driver failed to allocate an mbuf for the receiver ring. 117.It "tl%d: no memory for tx list" 118The driver failed to allocate an mbuf for the transmitter ring when 119allocating a pad buffer or collapsing an mbuf chain into a cluster. 120.El 121.Sh SEE ALSO 122.Xr arp 4 , 123.Xr ifmedia 4 , 124.Xr miibus 4 , 125.Xr netintro 4 , 126.Xr ng_ether 4 , 127.Xr ifconfig 8 128.Sh HISTORY 129The 130.Nm 131device driver first appeared in 132.Fx 2.2 . 133.Sh AUTHORS 134The 135.Nm 136driver was written by 137.An Bill Paul Aq wpaul@ctr.columbia.edu . 138