1.\" $OpenBSD: sis.4,v 1.18 2004/03/22 20:31:36 miod Exp $ 2.\" 3.\" Copyright (c) 1997, 1998, 1999 4.\" Bill Paul <wpaul@ee.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/sis.4,v 1.2 1999/11/15 23:14:27 phantom Exp $ 34.\" 35.Dd September 4, 1999 36.Dt SIS 4 37.Os 38.Sh NAME 39.Nm sis 40.Nd "SiS 900, SiS 7016, and NS DP83815 Fast Ethernet driver" 41.Sh SYNOPSIS 42.Cd "sis* at pci? dev ? function ?" 43.Sh DESCRIPTION 44The 45.Nm 46driver provides support for PCI Ethernet adapters and embedded 47controllers based on the Silicon Integrated Systems SiS 900 48and SiS 7016 Fast Ethernet controller chips, as well as support 49for adapters based on the National Semiconductor DP83815 (MacPhyter) 50PCI Ethernet controller chip, including the Netgear FA311 and FA312. 51.Pp 52The SiS 900 is a 100Mbps Ethernet MAC and MII-compliant transceiver 53in a single package. 54It uses a bus master DMA and a scatter/gather descriptor scheme. 55The SiS 7016 is similar to the SiS 900 except that it has no internal PHY, 56requiring instead an external transceiver to be attached to its MII interface. 57The SiS 900 and SiS 7016 both have a 128-bit multicast hash filter 58and a single perfect filter entry for the station address. 59.Pp 60The NS DP83815 is also a 100Mbps Ethernet MAC with integrated PHY. 61The NatSemi chip and the SiS 900 share many of the same features and 62a fairly similar programming interface, hence both chips are supported 63by the same driver. 64.Pp 65The 66.Nm 67driver supports the following media types: 68.Bl -tag -width full-duplex 69.It autoselect 70Enable autoselection of the media type and options. 71The user can manually override 72the autoselected mode by adding media options to the 73.Xr hostname.if 5 74file. 75.It 10baseT 76Set 10Mbps operation. 77The 78.Ar mediaopt 79option can also be used to select either 80.Ar full-duplex 81or 82.Ar half-duplex 83modes. 84.It 100baseTX 85Set 100Mbps (Fast Ethernet) operation. 86The 87.Ar mediaopt 88option can also be used to select either 89.Ar full-duplex 90or 91.Ar half-duplex 92modes. 93.El 94.Pp 95The 96.Nm 97driver supports the following media options: 98.Bl -tag -width full-duplex 99.It full-duplex 100Force full duplex operation. 101.It half-duplex 102Force half duplex operation. 103.El 104.Pp 105For more information on configuring this device, see 106.Xr ifconfig 8 . 107.Sh DIAGNOSTICS 108.Bl -diag 109.It "sis%d: couldn't map ports/memory" 110A fatal initialization error has occurred. 111.It "sis%d: couldn't map interrupt" 112A fatal initialization error has occurred. 113.It "sis%d: watchdog timeout" 114The device has stopped responding to the network, or there is a problem with 115the network connection (cable). 116.It "sis%d: no memory for rx list" 117The driver failed to allocate an mbuf for the receiver ring. 118.It "sis%d: no memory for tx list" 119The driver failed to allocate an mbuf for the transmitter ring when 120allocating a pad buffer or collapsing an mbuf chain into a cluster. 121.It "sis%d: chip is in D3 power state -- setting to D0" 122This message applies only to adapters which support power management. 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 its PCI configuration in the D3 state, so 127if the BIOS does not set it back to full power mode in time, it won't 128be able to configure it correctly. 129The driver tries to detect this condition and bring 130the adapter back to the D0 (full power) state, but this may not be 131enough to return the driver to a fully operational condition. 132If this message appears at boot time and the driver fails to attach 133the device as a network interface, a second warm boot will have to be 134performed to have the device properly configured. 135.Pp 136Note that this condition only occurs when warm booting from another 137operating system. 138If the system is powered down prior to booting 139.Ox , 140the card should be configured correctly. 141.El 142.Sh SEE ALSO 143.Xr arp 4 , 144.Xr ifmedia 4 , 145.Xr intro 4 , 146.Xr netintro 4 , 147.Xr pci 4 , 148.Xr hostname.if 5 , 149.Xr ifconfig 8 150.Rs 151.%T SiS 900 and SiS 7016 datasheets 152.%O http://www.sis.com.tw 153.Re 154.Rs 155.%T NatSemi DP83815 datasheet 156.%O http://www.national.com 157.Re 158.Sh HISTORY 159The 160.Nm 161device driver first appeared in 162.Fx 3.0 . 163.Ox 164support was added in 165.Ox 2.7 . 166.Sh AUTHORS 167The 168.Nm 169driver was written by 170.An Bill Paul Aq wpaul@ee.columbia.edu 171and ported to 172.Ox 173by 174.An Aaron Campbell Aq aaron@openbsd.org . 175