1.\" $NetBSD: we.4,v 1.13 2002/02/13 08:17:51 ross Exp $ 2.\" 3.\" Copyright (c) 1997 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Jason R. Thorpe of the Numerical Aerospace Simulation Facility, 8.\" NASA Ames Research Center. 9.\" 10.\" Redistribution and use in source and binary forms, with or without 11.\" modification, are permitted provided that the following conditions 12.\" are met: 13.\" 1. Redistributions of source code must retain the above copyright 14.\" notice, this list of conditions and the following disclaimer. 15.\" 2. Redistributions in binary form must reproduce the above copyright 16.\" notice, this list of conditions and the following disclaimer in the 17.\" documentation and/or other materials provided with the distribution. 18.\" 3. All advertising materials mentioning features or use of this software 19.\" must display the following acknowledgement: 20.\" This product includes software developed by the NetBSD 21.\" Foundation, Inc. and its contributors. 22.\" 4. Neither the name of The NetBSD Foundation nor the names of its 23.\" contributors may be used to endorse or promote products derived 24.\" from this software without specific prior written permission. 25.\" 26.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 27.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 28.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 29.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 30.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 31.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 32.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 33.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 34.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 35.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 36.\" POSSIBILITY OF SUCH DAMAGE. 37.\" 38.Dd October 20, 1997 39.Dt WE 4 40.Os 41.Sh NAME 42.Nm we 43.Nd "Western Digital/SMC WD80x3, SMC Elite Ultra, and SMC EtherEZ Ethernet cards device driver" 44.Sh SYNOPSIS 45.Cd "we0 at isa? port 0x280 iomem 0xd0000 irq 9" 46.Cd "we1 at isa? port 0x300 iomem 0xcc000 irq 10" 47.Cd "we* at mca? slot ?" 48.Sh DESCRIPTION 49The 50.Nm 51device driver supports Western Digital/SMC WD80x3, SMC Elite Ultra, and 52SMC EtherEZ Ethernet cards. 53.Sh FLAG VALUES 54For some clone boards the driver is not able to recognize 16bit or 8bit 55interfaces correctly. Since this makes a huge difference (see diagnostic 56section below) 57you can override this by specifying flags value in the config file: 58.Pp 59.Cd "we2 at isa? port 0x300 iomem 0xe0000 irq 15 flags 4" 60.Pp 61The values to add together for flags are: 62.Pp 63.Bl -diag 64.It 2 65force adapter to be treated as 8bit, even if it probes 66as a 16bit interface. Improper use of this flag will make the 67driver fail or send invalid Ethernet packets. 68.It 4 69force adapter to be treated as 16bit, even if it probes 70as a 8bit interface. For example the COMPEX ENT/U boards 71identify as WD8003 compatibles, but are in fact 16bit cards. 72Using this flag on a board that really is a 8bit board will 73result in bogus packets being sent. 74.It 8 75disable the use of double transmit buffers to save space in 76the on-board RAM for more receive buffers. 77.El 78.Pp 79Note that all supported MCA cards are 16bit. 80.Sh MEDIA SELECTION 81The ability to select media from software is dependent on the particular 82model of WD/SMC card. The following models support only manual configuration: 83WD8003S, WD8003E, and WD8013EBT. 84.Pp 85Other WD/SMC 80x3 interfaces support two types of media on a single card. 86All support the AUI media type. The other media is either BNC or UTP 87behind a transceiver. Software cannot differentiate between BNC and UTP 88cards. On some models, the AUI port is always active. 89.Pp 90The SMC Elite Ultra and SMC EtherEZ interfaces support three media 91a single card: AUI, BNC, and UTP. If the transceiver is active, the BNC 92media is selected. Otherwise, the AUI and UTP ports are both active. 93.Pp 94To enable the AUI media, select the 95.Em 10base5 96or 97.Em aui 98media type with 99.Xr ifconfig 8 's 100.Sq media 101directive. To select the other media (transceiver), select the 102.Em 10base2 103or 104.Em bnc 105media type. 106.Sh DIAGNOSTICS 107.Bl -diag 108.It "we0: overriding IRQ \*[Lt]n\*[Gt] to \*[Lt]m\*[Gt]" 109The IRQ specified in the kernel configuration file is different from that 110found in the card's configuration registers. The value in the kernel 111configuration file is being overridden by the one configured into the card. 112.It "we0: can't wildcard IRQ on a \*[Lt]model\*[Gt]" 113The IRQ was wildcarded in the kernel configuration file, and the card is 114a WD8003S, WD8003E, or WD8013EBT, which do not support software IRQ 115configuration. 116.It "we0: failed to clear shared memory at offset \*[Lt]off\*[Gt]" 117The memory test was unable to clear the interface's shared memory 118region. This often indicates that the card is configured at a conflicting 119.Em iomem 120address. 121.It we0: warning - receiver ring buffer overrun 122The DP8390 Ethernet chip used by this board implements a shared-memory 123ring-buffer to store incoming packets. 124.Pp 125The 16bit boards (8013 series) have 16k of memory as well as 126fast memory access speed. Typical memory access speed on these 127boards is about 4MB/second. These boards generally have no 128problems keeping up with full Ethernet speed and the ring-buffer 129seldom overfills. 130.Pp 131However, the 8bit boards (8003) usually have only 8k bytes of shared 132memory. This is only enough room for about 4 full-size (1500 byte) 133packets. This can sometimes be a problem, especially on the original 134WD8003E, because these boards' shared-memory access speed is quite 135slow; typically only about 1MB/second. The overhead of this slow 136memory access, and the fact that there is only room for 4 full-sized 137packets means that the ring-buffer will occasionally overrun. When 138this happens, the board must be reset to avoid a lockup problem in 139early revision 8390's. Resetting the board causes all of the data in 140the ring-buffer to be lost, requiring it to be retransmitted/received, 141congesting the board further. Because of this, maximum throughput on 142these boards is only about 400-600k per second. 143.Pp 144This problem is exasperated by NFS because the 8bit boards lack 145sufficient memory to support the default 8k byte packets that NFS and 146other protocols use as their default. If these cards must be used 147with NFS, use the NFS -r and -w options in /etc/fstab to limit NFS's 148packet size. 4096 byte packets generally work. 149.El 150.Sh SEE ALSO 151.Xr ifmedia 4 , 152.Xr intro 4 , 153.Xr isa 4 , 154.Xr mca 4 , 155.Xr ifconfig 8 156