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