mirror/freebsd
1
0
Fork 0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-18 10:35:55 +00:00
Code Issues Releases Activity

update to reflect bugs fixed in v0.9.5.2 of the hal

Browse Source
This commit is contained in:
Sam Leffler 2003-08-02 06:16:59 +00:00
parent 6b59f5e3d0
commit b56e3df93e
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=118343
1 changed files with 1 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
share/man/man4/ath.4
View File

@ -31,7 +31,7 @@
.\" .\"
.\" $FreeBSD$ .\" $FreeBSD$
.\"/ .\"/
.Dd July 13, 2003 .Dd August 1, 2003
.Dt ATH 4 .Dt ATH 4
.Os .Os
.Sh NAME .Sh NAME
@ -284,16 +284,8 @@ Alternatively, most 11g compatibility issues are in the 802.11 layer
and you may be able to workaround issues by modifying the and you may be able to workaround issues by modifying the
.Xr wlan 4 .Xr wlan 4
module. module.
.Pp
Atheros Turbo mode is untested.
.Sh BUGS .Sh BUGS
.Pp .Pp
Roaming mode is broken.
If you lose your access point by going out of
range the driver does not automaticaly re-associate.
.Pp
Adhoc mode is untested and possibly/probably broken.
.Pp
Performance in lossy environments is suboptimal. Performance in lossy environments is suboptimal.
The algorithm used to select the rate for transmitted packets is The algorithm used to select the rate for transmitted packets is
very simplistic. very simplistic.
@ -306,11 +298,5 @@ The Atheros hardware is known to be capable of transfer rates of 23-34 Mb/s
(or more) in 11a and 11g modes using their NDIS (aka Windows) driver. (or more) in 11a and 11g modes using their NDIS (aka Windows) driver.
Results with this driver are mixed and seem to vary significantly. Results with this driver are mixed and seem to vary significantly.
.Pp .Pp
It has been observed that getting a DHCP address sometimes requires
multiple tries.
This seems to happen only with AR5211 and AR5212 parts and mostly
in a noisy environment (i.e. one where many access points are found).
This problem is specific to the driver and not the hardware.
.Pp
The driver does not fully enable power-save operation of the chip; The driver does not fully enable power-save operation of the chip;
consequently power use is suboptimal. consequently power use is suboptimal.