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: src/share/man/man4/ste.4,v 1.7.2.5 2003/02/17 21:20:39 trhodes Exp $ 32.\" $DragonFly: src/share/man/man4/ste.4,v 1.2 2003/06/17 04:36:59 dillon Exp $ 33.\" 34.Dd August 21, 1999 35.Dt STE 4 36.Os 37.Sh NAME 38.Nm ste 39.Nd "Sundance Technologies ST201 fast ethernet device driver" 40.Sh SYNOPSIS 41.Cd "device miibus" 42.Cd "device ste" 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 workalike. 53It uses the same DMA descriptor 54structure and is very similar in operation, however its register 55layout is different. 56The ST201 has a 64-bit multicast hash filter 57and a single perfect filter entry for the station address. 58IT 59supports both 10 and 100Mbps speeds in either full or half duplex 60using an MII transceiver. 61.Pp 62The 63.Nm 64driver supports the following media types: 65.Pp 66.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 67.It autoselect 68Enable autoselection of the media type and options. 69The user can manually override 70the autoselected mode by adding media options to the 71.Pa /etc/rc.conf 72fine. 73.It 10baseT/UTP 74Set 10Mbps operation. 75The 76.Ar mediaopt 77option can also be used to select either 78.Ar full-duplex 79or 80.Ar half-duplex 81modes. 82.It 100baseTX 83Set 100Mbps (fast ethernet) operation. 84The 85.Ar mediaopt 86option can also be used to select either 87.Ar full-duplex 88or 89.Ar half-duplex 90modes. 91.El 92.Pp 93The 94.Nm 95driver supports the following media options: 96.Pp 97.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 98.It full-duplex 99Force full duplex operation 100.It half-duplex 101Force half duplex operation. 102.El 103.Pp 104For more information on configuring this device, see 105.Xr ifconfig 8 . 106.Sh DIAGNOSTICS 107.Bl -diag 108.It "ste%d: couldn't map ports/memory" 109A fatal initialization error has occurred. 110.It "ste%d: couldn't map interrupt" 111A fatal initialization error has occurred. 112.It "ste%d: watchdog timeout" 113The device has stopped responding to the network, or there is a problem with 114the network connection (cable). 115.It "ste%d: no memory for rx list" 116The driver failed to allocate an mbuf for the receiver ring. 117.It "ste%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.It "ste%d: chip is in D3 power state -- setting to D0" 121This message applies only to adapters which support power 122management. 123Some operating systems place the controller in low power 124mode when shutting down, and some PCI BIOSes fail to bring the chip 125out of this state before configuring it. 126The controller loses all of 127its PCI configuration in the D3 state, so if the BIOS does not set 128it back to full power mode in time, it won't be able to configure it 129correctly. 130The driver tries to detect this condition and bring 131the adapter back to the D0 (full power) state, but this may not be 132enough to return the driver to a fully operational condition. 133If 134you see this message at boot time and the driver fails to attach 135the device as a network interface, you will have to perform second 136warm boot to have the device properly configured. 137.Pp 138Note that this condition only occurs when warm booting from another 139operating system. 140If you power down your system prior to booting 141.Fx , 142the card should be configured correctly. 143.El 144.Sh SEE ALSO 145.Xr arp 4 , 146.Xr miibus 4 , 147.Xr netintro 4 , 148.Xr ng_ether 4 , 149.Xr ifconfig 8 150.Rs 151.%T Sundance ST201 data sheet 152.%O http://www.sundanceti.com 153.Re 154.Sh HISTORY 155The 156.Nm 157device driver first appeared in 158.Fx 3.0 . 159.Sh AUTHORS 160The 161.Nm 162driver was written by 163.An Bill Paul Aq wpaul@ee.columbia.edu . 164