xref: /freebsd/share/man/man4/ste.4 (revision b2d48be1bc7df45ddd13b143a160d0acb5a383c5)
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.
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$
32.\"
33.Dd December 24, 2009
34.Dt STE 4
35.Os
36.Sh NAME
37.Nm ste
38.Nd "Sundance Technologies ST201 Fast Ethernet device driver"
39.Sh SYNOPSIS
40To compile this driver into the kernel,
41place the following lines in your
42kernel configuration file:
43.Bd -ragged -offset indent
44.Cd "device miibus"
45.Cd "device ste"
46.Ed
47.Pp
48Alternatively, to load the driver as a
49module at boot time, place the following line in
50.Xr loader.conf 5 :
51.Bd -literal -offset indent
52if_ste_load="YES"
53.Ed
54.Sh DESCRIPTION
55The
56.Nm
57driver provides support for PCI Ethernet adapters and embedded
58controllers based on the Sundance Technologies ST201 PCI Fast
59Ethernet controller chip.
60.Pp
61The Sundance ST201 uses bus master DMA and is designed to be a
623Com Etherlink XL workalike.
63It uses the same DMA descriptor
64structure and is very similar in operation, however its register
65layout is different.
66The ST201 has a 64-bit multicast hash filter
67and a single perfect filter entry for the station address.
68It supports both 10 and 100Mbps speeds in either full or half duplex
69using an MII transceiver.
70.Pp
71The
72.Nm
73driver supports the following media types:
74.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
75.It autoselect
76Enable autoselection of the media type and options.
77The user can manually override
78the autoselected mode by adding media options to the
79.Pa /etc/rc.conf
80file.
81.It 10baseT/UTP
82Set 10Mbps operation.
83The
84.Ar mediaopt
85option can also be used to select either
86.Ar full-duplex
87or
88.Ar half-duplex
89modes.
90.It 100baseTX
91Set 100Mbps (Fast Ethernet) operation.
92The
93.Ar mediaopt
94option can also be used to select either
95.Ar full-duplex
96or
97.Ar half-duplex
98modes.
99.El
100.Pp
101The
102.Nm
103driver supports the following media options:
104.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
105.It full-duplex
106Force full duplex operation.
107.It half-duplex
108Force half duplex operation.
109.El
110.Pp
111For more information on configuring this device, see
112.Xr ifconfig 8 .
113.Sh HARDWARE
114The
115.Nm
116driver supports Sundance Technologies ST201 based Fast Ethernet
117adapters and embedded controllers including:
118.Pp
119.Bl -bullet -compact
120.It
121D-Link DFE-530TXS
122.It
123D-Link DFE-550TX
124.It
125D-Link DFE-580TX
126.El
127.Sh SYSCTL VARIABLES
128The following variables are available as both
129.Xr sysctl 8
130variables and
131.Xr loader 8
132tunables:
133.Bl -tag -width "xxxxxx"
134.It Va dev.ste.%d.int_rx_mod
135Maximum number of time to delay RX interrupts.
136The valid range is 0 to 209712 in units of 1us, the default is
137150 (150us).
138The value 0 effectively disables the RX interrupt moderation.
139The resolution of timer is about 3.2us so finer tuning than
1403.2us wouldn't be available.
141The interface does not need to be brought down and up again before
142a change takes effect.
143.El
144.Sh DIAGNOSTICS
145.Bl -diag
146.It "ste%d: couldn't map ports/memory"
147A fatal initialization error has occurred.
148.It "ste%d: couldn't map interrupt"
149A fatal initialization error has occurred.
150.It "ste%d: watchdog timeout"
151The device has stopped responding to the network, or there is a problem with
152the network connection (cable).
153.It "ste%d: no memory for rx list"
154The driver failed to allocate an mbuf for the receiver ring.
155.It "ste%d: no memory for tx list"
156The driver failed to allocate an mbuf for the transmitter ring when
157allocating a pad buffer or collapsing an mbuf chain into a cluster.
158.It "ste%d: chip is in D3 power state -- setting to D0"
159This message applies only to adapters which support power
160management.
161Some operating systems place the controller in low power
162mode when shutting down, and some PCI BIOSes fail to bring the chip
163out of this state before configuring it.
164The controller loses all of
165its PCI configuration in the D3 state, so if the BIOS does not set
166it back to full power mode in time, it will not be able to configure it
167correctly.
168The driver tries to detect this condition and bring
169the adapter back to the D0 (full power) state, but this may not be
170enough to return the driver to a fully operational condition.
171If
172you see this message at boot time and the driver fails to attach
173the device as a network interface, you will have to perform a second
174warm boot to have the device properly configured.
175.Pp
176Note that this condition only occurs when warm booting from another
177operating system.
178If you power down your system prior to booting
179.Fx ,
180the card should be configured correctly.
181.El
182.Sh SEE ALSO
183.Xr altq 4 ,
184.Xr arp 4 ,
185.Xr miibus 4 ,
186.Xr netintro 4 ,
187.Xr ng_ether 4 ,
188.Xr polling 4 ,
189.Xr vlan 4 ,
190.Xr ifconfig 8
191.Rs
192.%T Sundance ST201 data sheet
193.%U http://www.sundanceti.com
194.Re
195.Sh HISTORY
196The
197.Nm
198device driver first appeared in
199.Fx 3.0 .
200.Sh AUTHORS
201The
202.Nm
203driver was written by
204.An Bill Paul Aq Mt wpaul@ee.columbia.edu .
205