xref: /openbsd/share/man/man4/tl.4 (revision f7de5c7b)
1.\"	$OpenBSD: tl.4,v 1.5 1999/09/23 04:12:05 alex Exp $
2.\" Copyright (c) 1997, 1998
3.\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\" 3. All advertising materials mentioning features or use of this software
14.\"    must display the following acknowledgement:
15.\"	This product includes software developed by Bill Paul.
16.\" 4. Neither the name of the author nor the names of any co-contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"   without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
24.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
25.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
26.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
27.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
28.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
29.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
30.\" THE POSSIBILITY OF SUCH DAMAGE.
31.\"
32.\"	$Id: tl.4,v 1.5 1999/09/23 04:12:05 alex Exp $
33.\"
34.Dd May 1, 1998
35.Dt TL 4
36.Os
37.Sh NAME
38.Nm tl
39.Nd
40Texas Instruments ThunderLAN ethernet device driver
41.Sh SYNOPSIS
42.Cd "tl* at pci? dev ? function ?"
43.Sh DESCRIPTION
44The
45.Nm
46driver provides support for PCI ethernet adapters based on the Texas
47Instruments ThunderLAN ethernet controller chip. This includes a large
48number of Compaq PCI-bus ethernet adapters as well as the integrated
49ethernet controllers built in to several models of Compaq Prosignia
50servers and Compaq Deskpro desktop machines. This driver also supports
51the Olicom OC-2135/2138, OC-2325 and OC-2326 10/100 TX UTP adapters
52and the Racore 8165 10/100baseTX and 8148 10baseT/100baseTX/100baseFX
53multi-personality cards.
54.Pp
55The ThunderLAN controller has a standard MII interface that supports
56up to 32 physical interface devices (PHYs). It also has a built-in
5710baseT PHY hardwired at MII address 31, which may be used in some
5810Mbps-only hardware configurations. In 100Mbps configurations, a
59National Semiconductor DP83840A or other MII-compliant PHY may be
60attached to the ThunderLAN's MII bus. If a DP83840A or equivalent
61is available, the ThunderLAN chip can operate at either 100Mbps or
6210Mbps in either half-duplex or full-duplex modes. The ThunderLAN's
63built-in PHY and the DP83840A also support autonegotiation.
64.Pp
65The
66.Nm
67driver supports the following media types:
68.Pp
69.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
70.It autoselect
71Enable autoselection of the media type and options. Note that this
72option is only available on those PHYs that support autonegotiation.
73Also, the PHY will not advertise those modes that have been explicitly
74disabled using the following media options.
75.It 10baseT/UTP
76Set 10Mbps operation
77.It 100baseTX
78Set 100Mbps (fast ethernet) operation
79.It 10base5/AUI
80Enable AUI/BNC interface (useful only with the built-in PHY).
81.El
82.Pp
83The
84.Nm
85driver supports the following media options:
86.Pp
87.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
88.It full-duplex
89Force full duplex operation
90.It half-duplex
91Force half duplex operation.
92.It hw-loopback
93Enable hardware loopback mode.
94.El
95.Pp
96Note that the 100baseTX media type is only available if supported
97by the PHY.
98For more information on configuring this device, see
99.Xr ifconfig 8 .
100.Sh DIAGNOSTICS
101.Bl -diag
102.It "tl%d: couldn't map memory"
103A fatal initialization error has occurred.
104.It "tl%d: couldn't map interrupt"
105A fatal initialization error has occurred.
106.It "tl%d: device timeout"
107The device has stopped responding to the network, or there is a problem with
108the network connection (cable).
109.It "tl%d: no memory for rx list"
110The driver failed to allocate an mbuf for the receiver ring.
111.It "tl%d: no memory for tx list"
112The driver failed to allocate an mbuf for the transmitter ring when
113allocating a pad buffer or collapsing an mbuf chain into a cluster.
114.El
115.Sh SEE ALSO
116.Xr arp 4 ,
117.Xr netintro 4 ,
118.Xr ifconfig 8
119.Sh HISTORY
120The
121.Nm
122device driver first appeared in
123.Fx 2.2 .
124.Ox
125support first appeared in
126.Ox 2.4 .
127.Sh AUTHOR
128The
129.Nm
130driver was written by
131.An Bill Paul Aq wpaul@ctr.columbia.edu .
132