xref: /openbsd/share/man/man4/tl.4 (revision 81356b8d)
1.\"	$OpenBSD: tl.4,v 1.19 2008/06/07 21:36:19 brad Exp $
2.\"
3.\" Copyright (c) 1997, 1998
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.\"	$Id: tl.4,v 1.19 2008/06/07 21:36:19 brad Exp $
34.\"
35.Dd $Mdocdate: June 7 2008 $
36.Dt TL 4
37.Os
38.Sh NAME
39.Nm tl
40.Nd Texas Instruments ThunderLAN 10/100 Ethernet device
41.Sh SYNOPSIS
42.Cd "tl* at pci?"
43.Cd "lxtphy* at mii?"
44.Cd "nsphy* at mii?"
45.Cd "tlphy* at mii?"
46.Sh DESCRIPTION
47The
48.Nm
49driver provides support for PCI Ethernet adapters based on the Texas
50Instruments ThunderLAN Ethernet controller chip.
51This includes a large number of Compaq PCI-bus Ethernet adapters as well as
52the integrated Ethernet controllers built in to several models
53of Compaq Prosignia servers and Compaq Deskpro desktop machines.
54This driver also supports the Olicom OC-2135/2138, OC-2325 and OC-2326
5510/100 TX UTP adapters and the Racore 8165 10/100baseTX and 8148
5610baseT/100baseTX/100baseFX multi-personality cards.
57.Pp
58The ThunderLAN controller has a standard MII interface that supports
59up to 32 physical interface devices (PHYs).
60It also has a built-in 10baseT PHY hardwired at MII address 31, which may be
61used in some 10Mbps-only hardware configurations.
62In 100Mbps configurations, a National Semiconductor DP83840A or other
63MII-compliant PHY may be attached to the ThunderLAN's MII bus.
64If a DP83840A or equivalent is available, the ThunderLAN chip can operate
65at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes.
66The ThunderLAN's built-in PHY and the DP83840A also support autonegotiation.
67.Pp
68The
69.Nm
70driver supports the following media types:
71.Bl -tag -width full-duplex
72.It autoselect
73Enable autoselection of the media type and options.
74Note that this option is only available on those PHYs that support
75autonegotiation.
76Also, the PHY will not advertise those modes that have been explicitly
77disabled using the following media options.
78.It 10baseT
79Set 10Mbps operation.
80.It 100baseTX
81Set 100Mbps (Fast Ethernet) operation.
82.It 10base5
83Enable AUI/BNC interface (useful only with the built-in PHY).
84.El
85.Pp
86The
87.Nm
88driver supports the following media options:
89.Bl -tag -width full-duplex
90.It full-duplex
91Force full duplex operation.
92.It half-duplex
93Force half duplex operation.
94.It hw-loopback
95Enable hardware loopback mode.
96.El
97.Pp
98Note that the 100baseTX media type is only available if supported
99by the PHY.
100For more information on configuring this device, see
101.Xr ifconfig 8 .
102.Sh DIAGNOSTICS
103.Bl -diag
104.It "tl%d: couldn't map memory"
105A fatal initialization error has occurred.
106.It "tl%d: couldn't map interrupt"
107A fatal initialization error has occurred.
108.It "tl%d: device timeout"
109The device has stopped responding to the network, or there is a problem with
110the network connection (cable).
111.It "tl%d: no memory for rx list"
112The driver failed to allocate an mbuf for the receiver ring.
113.It "tl%d: no memory for tx list"
114The driver failed to allocate an mbuf for the transmitter ring when
115allocating a pad buffer or collapsing an mbuf chain into a cluster.
116.El
117.Sh SEE ALSO
118.Xr arp 4 ,
119.Xr ifmedia 4 ,
120.Xr intro 4 ,
121.Xr lxtphy 4 ,
122.Xr netintro 4 ,
123.Xr nsphy 4 ,
124.Xr pci 4 ,
125.Xr tlphy 4 ,
126.Xr hostname.if 5 ,
127.Xr ifconfig 8
128.Sh HISTORY
129The
130.Nm
131device driver first appeared in
132.Fx 2.2 .
133.Ox
134support first appeared in
135.Ox 2.4 .
136.Sh AUTHORS
137The
138.Nm
139driver was written by
140.An Bill Paul Aq wpaul@ctr.columbia.edu .
141