1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
<table class="head">
<tr>
<td class="head-ltitle">AWI(4)</td>
<td class="head-vol">Device Drivers Manual</td>
<td class="head-rtitle">AWI(4)</td>
</tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">awi</code> — <span class="Nd">AMD
PCnetMobile IEEE 802.11 PCMCIA wireless network driver</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">awi* at pcmcia? function ?</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">awi</code> driver supports various IEEE
802.11 wireless cards that run AMD PCnetMobile firmware based on the AMD
79c930 controller with the Intersil (formerly Harris) PRISM radio chipset.
It provides access to 32kb of memory shared between the controller and the
host. All host/device interaction is accomplished via this shared memory,
which can be accessed either via PCMCIA or I/O memory spaces. The
<code class="Nm">awi</code> driver encapsulates all IP and ARP traffic in
802.11 frames.</p>
<p class="Pp">The driver works both in infrastructure mode and in ad-hoc
(independent BSS) mode.</p>
<p class="Pp">In infrastructure mode, it communicates with an Access Point,
which serves as a link-layer bridge between an Ethernet segment and the
wireless network. An access point also provides roaming capability, which
allows a wireless node to move between access points.</p>
<p class="Pp">In ad-hoc mode, the device communicates peer to peer. Although it
is more efficient to communicate between wireless nodes, the coverage is
limited spatially due to the lack of roaming capability.</p>
<p class="Pp">In addition to these two modes in the IEEE 802.11 specification,
the <code class="Nm">awi</code> driver also supports a variant of ad-hoc
mode outside of the spec for DS radio cards. This makes it possible to
communicate with the WaveLAN ad-hoc mode of <a class="Xr">wi(4)</a> driver.
The NWID has no effect in this mode.</p>
<p class="Pp">Another mode added to the <code class="Nm">awi</code> driver can
be used with old Melco access points with 2Mbps cards. This mode actually
uses the IEEE 802.11 ad-hoc mode with encapsulation of raw Ethernet packets
(including headers) in 802.11 frames.</p>
<p class="Pp">For more information on configuring this device, see
<a class="Xr">ifconfig(8)</a> and <a class="Xr">ifmedia(4)</a>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1>
<p class="Pp">Cards supported by the <code class="Nm">awi</code> driver
include:</p>
<p class="Pp"></p>
<div class="Bd-indent">
<dl class="Bl-tag Bl-compact">
<dt>BayStack 650</dt>
<dd>1Mbps Frequency Hopping PCCARD adapter</dd>
<dt>BayStack 660</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>Icom SL-200</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>Melco WLI-PCM</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>NEL SSMagic</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>Netwave AirSurfer Plus</dt>
<dd>1Mbps Frequency Hopping PCCARD adapter</dd>
<dt>Netwave AirSurfer Pro</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>Nokia C020 WLAN</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>Farallon SkyLINE</dt>
<dd>2Mbps Direct Sequence PCCARD adapter</dd>
<dt>Zoom Air Model 4000</dt>
<dd style="width: auto;"> </dd>
</dl>
</div>
<p class="Pp">The original Xircom Netwave AirSurfer is supported by the
<a class="Xr">cnw(4)</a> driver, and the PRISM-II cards are supported by the
<a class="Xr">wi(4)</a> driver.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="MEDIA_SELECTION"><a class="permalink" href="#MEDIA_SELECTION">MEDIA
SELECTION</a></h1>
<p class="Pp">In addition to default
<a class="permalink" href="#Auto"><i class="Em" id="Auto">Auto</i></a> media
type, the DS cards support
<a class="permalink" href="#DS1"><i class="Em" id="DS1">DS1</i></a> and
<a class="permalink" href="#DS2"><i class="Em" id="DS2">DS2</i></a> media
types, while the FH cards support the
<a class="permalink" href="#FH1"><i class="Em" id="FH1">FH1</i></a> media
type. For each media type, the
<a class="permalink" href="#adhoc"><i class="Em" id="adhoc">adhoc</i></a>
mediaopt can be used to indicate to the driver to operate in ad-hoc mode.
The
<a class="permalink" href="#flag0"><i class="Em" id="flag0">flag0</i></a>
mediaopt should be used only with old access points, which operate in IBSS
mode. For DS radio cards, the
<a class="permalink" href="#adhoc,flag0"><i class="Em" id="adhoc,flag0">adhoc,flag0</i></a>
mediaopt can be used for <a class="Xr">wi(4)</a> compatible WaveLAN ad-hoc
mode.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
<dt>awi0: no suitable CIS info found</dt>
<dd>The device cannot be mapped due to a resource conflict. Or, the device
failed to initialize its firmware.</dd>
<dt>awi0: failed to complete selftest (%s)</dt>
<dd>The device failed to complete its self test. In some circumstances,
resetting device after power on fails. Re-inserting the card or setting
the interface up and then down again (using <a class="Xr">ifconfig(8)</a>)
may also be helpful.</dd>
<dt>awi0: transmit timeout</dt>
<dd>The device failed to generate an interrupt to acknowledge a transmitted
packet.</dd>
<dt>awi0: failed to lock interrupt</dt>
<dd>The system was unable to obtain the lock to access shared memory.</dd>
<dt>awi0: command %d failed %x</dt>
<dd>The device failed to complete the request from the system.</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE
ALSO</a></h1>
<p class="Pp"><a class="Xr">arp(4)</a>, <a class="Xr">cnw(4)</a>,
<a class="Xr">ifmedia(4)</a>, <a class="Xr">netintro(4)</a>,
<a class="Xr">pcmcia(4)</a>, <a class="Xr">wi(4)</a>,
<a class="Xr">ifconfig(8)</a>, <a class="Xr">wiconfig(8)</a></p>
<p class="Pp"><cite class="Rs"><span class="RsT">Am79C930 PCnet Mobile
Single-Chip Wireless LAN Media Access Controller</span>,
<a class="RsU" href="http://www.amd.com">http://www.amd.com</a>.</cite></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">awi</code> device driver first appeared in
<span class="Ux">NetBSD 1.5</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1>
<p class="Pp">The initial version of the <code class="Nm">awi</code> driver was
written by <span class="An">Bill Sommerfeld</span>
⟨sommerfeld@NetBSD.org⟩. It was then completely rewritten to
support cards with the DS phy and ad-hoc mode by
<br/>
<span class="An">Atsushi Onoe</span> ⟨onoe@NetBSD.org⟩.</p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">January 2, 2006</td>
<td class="foot-os">NetBSD 10.1</td>
</tr>
</table>
|
