View | Details | Raw Unified | Return to bug 55442
Collapse All | Expand All

(-)share/man/man4/awi.4 (-6 / +6 lines)
Lines 30-45 Link Here
30
which serves as a link-layer bridge between an Ethernet and
30
which serves as a link-layer bridge between an Ethernet and
31
the wireless network.
31
the wireless network.
32
An access point also provides roaming capability
32
An access point also provides roaming capability
33
which allows wireless node to move between access points.
33
which allows wireless nodes to move between access points.
34
.Pp
34
.Pp
35
In adhoc mode, it communicates peer to peer.
35
In adhoc mode, it communicates peer to peer.
36
Though it is more efficient to communicate between wireless nodes,
36
Though it is more efficient to communicate between wireless nodes,
37
the coverage is limited spatially due to lack of roaming capability.
37
the coverage is limited spatially due to lack of roaming capability.
38
.Pp
38
.Pp
39
In addition to these two mode in IEEE 802.11 specification, the
39
In addition to these two modes in the IEEE 802.11 specification, the
40
.Nm
40
.Nm
41
driver also supports a variant of adhoc mode out of spec for DS radio cards,
41
driver also supports a variant of adhoc mode out of spec for DS radio cards,
42
which makes possible to communicate with adhoc mode of
42
which makes it possible to communicate with adhoc mode of
43
.Xr wi 8
43
.Xr wi 8
44
driver.
44
driver.
45
The NWID doesn't affect in this mode.
45
The NWID doesn't affect in this mode.
Lines 97-103 Link Here
97
(slightly slower) i/o-space only access methods to read and write to
97
(slightly slower) i/o-space only access methods to read and write to
98
the shared memory.
98
the shared memory.
99
Since by default,
99
Since by default,
100
.Nx ,
100
.Nx 
101
only allocates 16kb of
101
only allocates 16kb of
102
address space per PCMCIA controller, this message is in some sense to
102
address space per PCMCIA controller, this message is in some sense to
103
be expected and should not be a cause for alarm.
103
be expected and should not be a cause for alarm.
Lines 119-125 Link Here
119
.It "awi0: association failed (reason %d)"
119
.It "awi0: association failed (reason %d)"
120
The access point refuses the association request from the device.
120
The access point refuses the association request from the device.
121
.It "awi0: no recent beacons from %s; rescanning"
121
.It "awi0: no recent beacons from %s; rescanning"
122
The device has not heard a beacon from its currently associated Access
122
The device has not seen a beacon from its currently associated Access
123
Point recently, and is looking for a new access point.
123
Point recently, and is looking for a new access point.
124
.It "awi0: transmit timeout"
124
.It "awi0: transmit timeout"
125
The device failed to generate an interrupt to acknowledge a
125
The device failed to generate an interrupt to acknowledge a
Lines 157-162 Link Here
157
.An Bill Sommerfeld Aq sommerfeld@netbsd.org .
157
.An Bill Sommerfeld Aq sommerfeld@netbsd.org .
158
Then the
158
Then the
159
.Nm
159
.Nm
160
driver module completely rewritten to support cards with DS phy and
160
driver module was completely rewritten to support cards with DS phy and
161
to support adhoc mode by
161
to support adhoc mode by
162
.An Atsushi Onoe Aq onoe@netbsd.org .
162
.An Atsushi Onoe Aq onoe@netbsd.org .

Return to bug 55442