linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kalle.valo@iki.fi>, Dan Williams <dcbw@redhat.com>,
	John Linville <linville@tuxdriver.com>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Signal quality strange since commit 708c57cf1709fb95
Date: Tue, 24 Feb 2009 01:07:08 -0600	[thread overview]
Message-ID: <49A39C9C.7040002@lwfinger.net> (raw)
In-Reply-To: <1235452576.4455.81.camel@johannes.local>

Johannes Berg wrote:
> On Mon, 2009-02-23 at 22:18 -0600, Larry Finger wrote:
> 
>> No, I just wondered if it was intentional that it was changed to /70. It appears
>> that it was, therefore, at least 3 drivers must be changed as they are
>> calculating on the basis of /100. For example, my b43 is showing an iwconfig
>> Link Quality of 93/70 while the KNM applet is showing 50%.
> 
> Well that _is_ a bug, since this shouldn't have required driver changes!
> I'll take a look into why that might be happening.

Drivers b43, b43legacy, rtl8187, and p54usb all assume a Link Quality scaled to
100, which was the behavior before the commit in the subject. I don't quite
understand why as the old code had this fragment:

-       if (local->hw.flags & IEEE80211_HW_SIGNAL_DBM) {
-               /*
-                * cfg80211 assumes -110 to -40 dBm and clamps to that range
-                * for qual.qual, so tell userspace this is what we give it
-                * but take into account that we have to start from 0.
-                */
-               range->max_qual.qual = 70;
-               range->avg_qual.qual = 35;
-       } else {
-               /*
-                * cfg80211 just uses the level value for qual too, and it
-                * requires the level value to be 0 .. 100.
-                */
-               range->max_qual.qual = 100;
-               range->avg_qual.qual = 50;
-       }

That should have set max_qual.qual to 70 as all the drivers set
IEEE80211_HW_SIGNAL_DBM. I don't know why, but the code took the other branch,
which seems to have been some other bug.

Larry

  reply	other threads:[~2009-02-24  7:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21 15:09 Signal quality strange since commit 708c57cf1709fb95 Larry Finger
2009-02-21 18:44 ` Dan Williams
2009-02-21 20:04   ` Larry Finger
2009-02-22  6:39     ` Kalle Valo
2009-02-22 15:30       ` Dan Williams
2009-02-24  2:10       ` Johannes Berg
2009-02-24  4:18         ` Larry Finger
2009-02-24  5:16           ` Johannes Berg
2009-02-24  7:07             ` Larry Finger [this message]
2009-02-24  7:13               ` Johannes Berg
2009-02-27 17:45                 ` Johannes Berg
2009-02-27 21:24                   ` Larry Finger
2009-02-27 21:48                     ` Johannes Berg
2009-02-22 15:32     ` Dan Williams

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=49A39C9C.7040002@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).