1.\" $NetBSD: awi.4,v 1.20 2003/05/06 10:46:42 jmmv Exp $ 2.\" 3.\" Copyright (c) 1999,2000,2001 The NetBSD Foundation, Inc. 4.\" All rights reserved. 5.\" 6.\" This code is derived from software contributed to The NetBSD Foundation 7.\" by Bill Sommerfeld 8.\" 9.\" Redistribution and use in source and binary forms, with or without 10.\" modification, are permitted provided that the following conditions 11.\" are met: 12.\" 1. Redistributions of source code must retain the above copyright 13.\" notice, this list of conditions and the following disclaimer. 14.\" 2. Redistributions in binary form must reproduce the above copyright 15.\" notice, this list of conditions and the following disclaimer in the 16.\" documentation and/or other materials provided with the distribution. 17.\" 3. All advertising materials mentioning features or use of this software 18.\" must display the following acknowledgement: 19.\" This product includes software developed by the NetBSD 20.\" Foundation, Inc. and its contributors. 21.\" 4. Neither the name of The NetBSD Foundation nor the names of its 22.\" contributors may be used to endorse or promote products derived 23.\" from this software without specific prior written permission. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS 26.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED 27.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 28.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS 29.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 30.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 31.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 32.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 33.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 34.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 35.\" POSSIBILITY OF SUCH DAMAGE. 36.Dd September 18, 2001 37.Dt AWI 4 38.Os 39.Sh NAME 40.Nm awi 41.Nd 42AMD PCnetMobile IEEE 802.11 PCMCIA wireless network driver 43.Sh SYNOPSIS 44.Cd "awi* at pcmcia? function ?" 45.Sh DESCRIPTION 46The 47.Nm 48driver supports various IEEE 802.11 wireless cards 49which run AMD PCnetMobile firmware based on AMD 79c930 controller 50with Intersil (formerly Harris) PRISM radio chipset. 51It provides access to 32kb of memory shared between the controller 52and the host. 53All host/device interaction is via this shared memory, which can be 54accessed either via PCMCIA memory space or I/O space. 55The 56.Nm 57driver encapsulates all IP and ARP traffic as 802.11 frames. 58.Pp 59The driver works both in infrastructure mode and in ad-hoc (independent 60BSS) mode. 61.Pp 62In infrastructure mode, it communicates with an Access Point 63which serves as a link-layer bridge between an Ethernet and 64the wireless network. An access point also provides roaming capability 65which allows wireless node to move between access points. 66.Pp 67In ad-hoc mode, it communicates peer to peer. 68Though it is more efficient to communicate between wireless nodes, 69the coverage is limited spatially due to lack of roaming capability. 70.Pp 71In addition to these two mode in IEEE 802.11 specification, the 72.Nm 73driver also supports a variant of ad-hoc mode out of spec for DS radio cards, 74which makes possible to communicate with WaveLAN ad-hoc mode of 75.Xr wi 4 76driver. The NWID doesn't affect in this mode. 77.Pp 78Another mode added to the 79.Nm 80driver can be used with old Melco access point with 2Mbps card, 81which actually use IEEE 802.11 ad-hoc mode with encapsulation of 82raw Ethernet packet including header in 802.11 frames. 83.Pp 84For more information on configuring this device, see 85.Xr ifconfig 8 86and 87.Xr ifmedia 4 . 88.Sh HARDWARE 89Cards supported by the 90.Nm 91driver include: 92.Pp 93.Bl -tag -width BayStack_650x -offset indent -compact 94.It BayStack 650 951Mbps Frequency Hopping PCCARD adapter 96.It BayStack 660 972Mbps Direct Sequence PCCARD adapter 98.It Icom SL-200 992Mbps Direct Sequence PCCARD adapter 100.It Melco WLI-PCM 1012Mbps Direct Sequence PCCARD adapter 102.It NEL SSMagic 1032Mbps Direct Sequence PCCARD adapter 104.It Netwave AirSurfer Plus 1051Mbps Frequency Hopping PCCARD adapter 106.It Netwave AirSurfer Pro 1072Mbps Direct Sequence PCCARD adapter 108.It Nokia C020 WLAN 1092Mbps Direct Sequence PCCARD adapter 110.It Farallon SkyLINE 1112Mbps Direct Sequence PCCARD adapter 112.El 113.Pp 114The original Xircom Netwave AirSurfer is supported by the 115.Xr cnw 4 116driver, and the PRISM-II cards are supported by the 117.Xr wi 4 118driver. 119.Sh MEDIA SELECTION 120In addition to default 121.Em Auto 122media type, 123the DS cards support 124.Em DS1 125and 126.Em DS2 127media types, while the FH cards support 128.Em FH1 129media type. For each media type, 130.Em adhoc 131mediaopt can be used to indicate the driver to operate in ad-hoc mode. 132The 133.Em flag0 134mediaopt 135should be used only with old access point which operates in IBSS mode. 136For DS radio cards, 137.Em adhoc,flag0 138mediaopt can be used for 139.Xr wi 4 140compatible WaveLAN ad-hoc mode. 141.Pp 142To configure more detailed parameters for the 143.Nm 144driver, 145.Xr wiconfig 8 146can be used. 147.Sh DIAGNOSTICS 148.Bl -diag 149.It "awi0: unable to allocate memory space; using i/o only" 150Indicates that the driver was not able to allocate 32kb of PCMCIA bus 151address space into which to map the device; the driver will use the 152(slightly slower) i/o-space only access methods to read and write to 153the shared memory. Since by default, 154.Nx 155only allocates 16kb of 156address space per PCMCIA controller, this message is in some sense to 157be expected and should not be a cause for alarm. 158See 159.Xr pcmcia 4 160for information on how to increase the memory available to the PCMCIA 161controller. 162.It "awi0: failed to complete selftest (%s)" 163The device failed to complete its self test. 164In some circumstances, resetting device after power on fails. 165Re-inserting the card or down-then-up interface may be helpful. 166.It "awi0: associated with %s ssid %s channel %d signal %d" 167The device has successfully synchronized with the identified Access 168Point or BSS and is ready to relay traffic. 169.It "awi0: authentication failed (reason %d)" 170.It "awi0: association failed (reason %d)" 171The access point refuses the authentication or association request 172from the device. 173.It "awi0: no recent beacons from %s; rescanning" 174The device has not heard a beacon from its currently associated Access 175Point recently, and is looking for a new access point. 176.It "awi0: transmit timeout" 177The device failed to generate an interrupt to acknowledge a 178transmitted packet. 179.It "awi0: failed to lock interrupt" 180The system was unable to obtain the lock to access shared memory. 181.It "awi0: command %d failed %x" 182The device failed to complete the request from the system. 183.El 184.Sh SEE ALSO 185.Xr arp 4 , 186.Xr cnw 4 , 187.Xr ifmedia 4 , 188.Xr netintro 4 , 189.Xr pcmcia 4 , 190.Xr wi 4 , 191.Xr ifconfig 8 , 192.Xr wiconfig 8 193.Rs 194.%T Am79C930 PCnet Mobile Single-Chip Wireless LAN Media Access Controller 195.%O http://www.amd.com 196.Re 197.Sh HISTORY 198The 199.Nm 200device driver first appeared in 201.Nx 1.5 . 202.Sh AUTHORS 203The initial version of the 204.Nm 205driver was written by 206.An Bill Sommerfeld 207.Aq sommerfeld@NetBSD.org . 208Then the 209.Nm 210driver module completely rewritten to support cards with DS phy and 211to support ad-hoc mode by 212.An Atsushi Onoe 213.Aq onoe@NetBSD.org . 214