xref: /openbsd-src/share/man/man4/ste.4 (revision db3296cf5c1dd9058ceecc3a29fe4aaa0bd26000)
1.\"	$OpenBSD: ste.4,v 1.13 2003/05/05 08:32:31 jmc Exp $
2.\"
3.\" Copyright (c) 1997, 1998, 1999
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.\" $FreeBSD: src/share/man/man4/ste.4,v 1.3 1999/11/15 23:14:27 phantom Exp $
34.\"
35.Dd August 21, 1999
36.Dt STE 4
37.Os
38.Sh NAME
39.Nm ste
40.Nd Sundance Technologies ST201 Fast Ethernet driver
41.Sh SYNOPSIS
42.Cd "ste* at pci? dev ? function ?"
43.Sh DESCRIPTION
44The
45.Nm
46driver provides support for PCI Ethernet adapters and embedded
47controllers based on the Sundance Technologies ST201 PCI fast
48Ethernet controller chip.
49This includes the D-Link DFE-550TX.
50.Pp
51The Sundance ST201 uses bus master DMA and is designed to be a
523Com EtherLink XL work-alike.
53It uses the same DMA descriptor structure and is very similar in operation,
54however its register layout is different.
55The ST201 has a 64-bit multicast hash filter and a single perfect filter
56entry for the station address.
57It supports both 10 and 100Mbps speeds in either full or half duplex
58using an MII transceiver.
59.Pp
60The
61.Nm
62driver supports the following media types:
63.Pp
64.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
65.It autoselect
66Enable autoselection of the media type and options.
67The user can manually override
68the autoselected mode by adding media options to the
69.Xr hostname.if 5
70file.
71.It 10baseT
72Set 10Mbps operation.
73The
74.Ar mediaopt
75option can also be used to select either
76.Ar full-duplex
77or
78.Ar half-duplex
79modes.
80.It 100baseTX
81Set 100Mbps (Fast Ethernet) operation.
82The
83.Ar mediaopt
84option can also be used to select either
85.Ar full-duplex
86or
87.Ar half-duplex
88modes.
89.El
90.Pp
91The
92.Nm
93driver supports the following media options:
94.Pp
95.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
96.It full-duplex
97Force full duplex operation.
98.It half-duplex
99Force half duplex operation.
100.El
101.Pp
102For more information on configuring this device, see
103.Xr ifconfig 8 .
104.Sh DIAGNOSTICS
105.Bl -diag
106.It "ste%d: couldn't map ports/memory"
107A fatal initialization error has occurred.
108.It "ste%d: couldn't map interrupt"
109A fatal initialization error has occurred.
110.It "ste%d: watchdog timeout"
111The device has stopped responding to the network, or there is a problem with
112the network connection (cable).
113.It "ste%d: no memory for rx list"
114The driver failed to allocate an mbuf for the receiver ring.
115.It "ste%d: no memory for tx list"
116The driver failed to allocate an mbuf for the transmitter ring when
117allocating a pad buffer or collapsing an mbuf chain into a cluster.
118.It "ste%d: chip is in D3 power state -- setting to D0"
119This message applies only to adapters which support power
120management.
121Some operating systems place the controller in low power
122mode when shutting down, and some PCI BIOSes fail to bring the chip
123out of this state before configuring it.
124The controller loses all of
125its PCI configuration in the D3 state, so if the BIOS does not set
126it back to full power mode in time, it won't be able to configure it
127correctly.
128The driver tries to detect this condition and bring
129the adapter back to the D0 (full power) state, but this may not be
130enough to return the driver to a fully operational condition.
131If this message appears at boot time and the driver fails to attach
132the device as a network interface, a second warm boot will have to be
133performed to have the device properly configured.
134.Pp
135Note that this condition only occurs when warm booting from another
136operating system.
137If the system is powered down prior to booting
138.Ox ,
139the card should be configured correctly.
140.El
141.Sh SEE ALSO
142.Xr arp 4 ,
143.Xr ifmedia 4 ,
144.Xr intro 4 ,
145.Xr netintro 4 ,
146.Xr pci 4 ,
147.Xr hostname.if 5 ,
148.Xr ifconfig 8
149.Rs
150.%T Sundance ST201 data sheet
151.%O http://www.sundanceti.com
152.Re
153.Sh HISTORY
154The
155.Nm
156device driver first appeared in
157.Fx 3.0 .
158.Ox
159support was added in
160.Ox 2.7 .
161.Sh AUTHORS
162The
163.Nm
164driver was written by
165.An Bill Paul Aq wpaul@ee.columbia.edu
166and ported to
167.Ox
168by
169.An Aaron Campbell Aq aaron@openbsd.org .
170