From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: John Linville <linville@tuxdriver.com>,
Michael Buesch <mb@bu3sch.de>,
Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org,
Jiri Benc <jbenc@suse.cz>
Subject: Re: [PATCH] mac80211: Report correct wireless statistics
Date: Sun, 08 Apr 2007 17:26:11 -0500 [thread overview]
Message-ID: <46196C03.4070003@lwfinger.net> (raw)
In-Reply-To: <200704081135.33106.flamingice@sourmilk.net>
Michael Wu wrote:
> On Sunday 08 April 2007 01:04, Larry Finger wrote:
>> In mac80211 the 'qual' and 'level' values are interchanged. The patch also
>> places the 'qual' value on a 0 - 100 scale and calculated using the formula
>> contained in iwlib.
>>
> NACK. Qual (arbitrary signal quality) and level (RSSI) values are correct and
> userspace is responsible for scaling any statistics values.
I disagree. For the wireless extensions output, the maximum values are set implicitly in the
iw_range struct. In addition, the level is always in dBm (a negative number), whereas the RSSI is an
arbitrary positive number. Because the maximum value is driver dependent, it must be specified when
the driver initializes the MAC layer.
In any case, the current code is broken. Without my patch, an iwconfig command with bcm43xx-mac80211
produces the line:
Link Quality=216/146 Signal level=-197 dBm Noise level=-63 dBm
We could argue about the Link Quality, although the x/146 looks pretty strange. The Signal level of
-197 dBm is impossible. With my patch, the same version of bcm43xx gets the line
Link Quality=90/100 Signal level=-36 dBm Noise level=-69 dBm
That Signal level matches what comes from both bcm43xx-softmac and the Windows driver running under
ndiswrapper.
Larry
next prev parent reply other threads:[~2007-04-08 22:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 5:04 [PATCH] mac80211: Report correct wireless statistics Larry Finger
2007-04-08 7:48 ` Tomas Winkler
2007-04-08 15:35 ` Michael Wu
2007-04-08 22:26 ` Larry Finger [this message]
2007-04-08 23:02 ` Michael Wu
2007-04-08 23:32 ` Larry Finger
2007-04-08 23:41 ` Michael Wu
2007-04-09 0:02 ` Larry Finger
2007-04-09 0:31 ` Michael Wu
2007-04-09 3:54 ` Larry Finger
2007-04-09 4:43 ` Michael Wu
2007-04-09 5:06 ` Larry Finger
2007-04-09 12:07 ` Dan Williams
2007-04-09 12:21 ` Dan Williams
2007-04-09 15:49 ` Larry Finger
2007-04-09 17:16 ` Michael Wu
2007-04-09 21:12 ` Larry Finger
2007-04-09 23:02 ` Michael Wu
2007-04-10 0:59 ` Larry Finger
2007-04-13 23:18 ` Michael Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46196C03.4070003@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).