Attachment 34019 Details for Bug 55442 – awi.4.diff

[patch] awi.4.diff

awi.4.diff (text/plain), 2.16 KB, created by Lukas Ertl on 2003-08-10 12:20:17 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Lukas Ertl

Created: 2003-08-10 12:20:17 UTC

Size: 2.16 KB

patch

obsolete

>Index: share/man/man4/awi.4
>===================================================================
>RCS file: /usr/local/bsdcvs/src/share/man/man4/awi.4,v
>retrieving revision 1.13
>diff -u -r1.13 awi.4
>--- share/man/man4/awi.4	28 Jun 2003 23:53:37 -0000	1.13
>+++ share/man/man4/awi.4	10 Aug 2003 10:47:47 -0000
>@@ -30,16 +30,16 @@
> which serves as a link-layer bridge between an Ethernet and
> the wireless network.
> An access point also provides roaming capability
>-which allows wireless node to move between access points.
>+which allows wireless nodes to move between access points.
> .Pp
> In adhoc mode, it communicates peer to peer.
> Though it is more efficient to communicate between wireless nodes,
> the coverage is limited spatially due to lack of roaming capability.
> .Pp
>-In addition to these two mode in IEEE 802.11 specification, the
>+In addition to these two modes in the IEEE 802.11 specification, the
> .Nm
> driver also supports a variant of adhoc mode out of spec for DS radio cards,
>-which makes possible to communicate with adhoc mode of
>+which makes it possible to communicate with adhoc mode of
> .Xr wi 8
> driver.
> The NWID doesn't affect in this mode.
>@@ -97,7 +97,7 @@
> (slightly slower) i/o-space only access methods to read and write to
> the shared memory.
> Since by default,
>-.Nx ,
>+.Nx 
> only allocates 16kb of
> address space per PCMCIA controller, this message is in some sense to
> be expected and should not be a cause for alarm.
>@@ -119,7 +119,7 @@
> .It "awi0: association failed (reason %d)"
> The access point refuses the association request from the device.
> .It "awi0: no recent beacons from %s; rescanning"
>-The device has not heard a beacon from its currently associated Access
>+The device has not seen a beacon from its currently associated Access
> Point recently, and is looking for a new access point.
> .It "awi0: transmit timeout"
> The device failed to generate an interrupt to acknowledge a
>@@ -157,6 +157,6 @@
> .An Bill Sommerfeld Aq sommerfeld@netbsd.org .
> Then the
> .Nm
>-driver module completely rewritten to support cards with DS phy and
>+driver module was completely rewritten to support cards with DS phy and
> to support adhoc mode by
> .An Atsushi Onoe Aq onoe@netbsd.org .

Actions: View | Diff

Attachments on bug 55442: 34019