1.\" $OpenBSD: ste.4,v 1.14 2003/11/09 16:06:07 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.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 64.It autoselect 65Enable autoselection of the media type and options. 66The user can manually override 67the autoselected mode by adding media options to the 68.Xr hostname.if 5 69file. 70.It 10baseT 71Set 10Mbps operation. 72The 73.Ar mediaopt 74option can also be used to select either 75.Ar full-duplex 76or 77.Ar half-duplex 78modes. 79.It 100baseTX 80Set 100Mbps (Fast Ethernet) operation. 81The 82.Ar mediaopt 83option can also be used to select either 84.Ar full-duplex 85or 86.Ar half-duplex 87modes. 88.El 89.Pp 90The 91.Nm 92driver supports the following media options: 93.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 94.It full-duplex 95Force full duplex operation. 96.It half-duplex 97Force half duplex operation. 98.El 99.Pp 100For more information on configuring this device, see 101.Xr ifconfig 8 . 102.Sh DIAGNOSTICS 103.Bl -diag 104.It "ste%d: couldn't map ports/memory" 105A fatal initialization error has occurred. 106.It "ste%d: couldn't map interrupt" 107A fatal initialization error has occurred. 108.It "ste%d: watchdog timeout" 109The device has stopped responding to the network, or there is a problem with 110the network connection (cable). 111.It "ste%d: no memory for rx list" 112The driver failed to allocate an mbuf for the receiver ring. 113.It "ste%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.It "ste%d: chip is in D3 power state -- setting to D0" 117This message applies only to adapters which support power 118management. 119Some operating systems place the controller in low power 120mode when shutting down, and some PCI BIOSes fail to bring the chip 121out of this state before configuring it. 122The controller loses all of 123its PCI configuration in the D3 state, so if the BIOS does not set 124it back to full power mode in time, it won't be able to configure it 125correctly. 126The driver tries to detect this condition and bring 127the adapter back to the D0 (full power) state, but this may not be 128enough to return the driver to a fully operational condition. 129If this message appears at boot time and the driver fails to attach 130the device as a network interface, a second warm boot will have to be 131performed to have the device properly configured. 132.Pp 133Note that this condition only occurs when warm booting from another 134operating system. 135If the system is powered down prior to booting 136.Ox , 137the card should be configured correctly. 138.El 139.Sh SEE ALSO 140.Xr arp 4 , 141.Xr ifmedia 4 , 142.Xr intro 4 , 143.Xr netintro 4 , 144.Xr pci 4 , 145.Xr hostname.if 5 , 146.Xr ifconfig 8 147.Rs 148.%T Sundance ST201 data sheet 149.%O http://www.sundanceti.com 150.Re 151.Sh HISTORY 152The 153.Nm 154device driver first appeared in 155.Fx 3.0 . 156.Ox 157support was added in 158.Ox 2.7 . 159.Sh AUTHORS 160The 161.Nm 162driver was written by 163.An Bill Paul Aq wpaul@ee.columbia.edu 164and ported to 165.Ox 166by 167.An Aaron Campbell Aq aaron@openbsd.org . 168