linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	John Linville <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Signal quality strange since commit 708c57cf1709fb95
Date: Sun, 22 Feb 2009 10:30:28 -0500	[thread overview]
Message-ID: <1235316628.28069.2.camel@localhost> (raw)
In-Reply-To: <8763j33rgq.fsf@litku.valot.fi>

On Sun, 2009-02-22 at 08:39 +0200, Kalle Valo wrote:
> Larry Finger <Larry.Finger@lwfinger.net> writes:
> 
> > I know how it works with drivers that implement their own ioctl
> > calls for the WEXT interface; however, the 3 that I mentioned all
> > use mac80211 and get their WEXT support through cfg80211.
> 
> Yes, something is wrong now. I noticed the same problem (/70 in signal
> strength) when I was implementing rssi support for at76c50x-usb.

The /70 *by itself* is not a problem.  There could be a problem with the
quality calculation that cfg80211/mac80211 are doing with the reported
signal strength from the hardware-specific driver.

Dan



  reply	other threads:[~2009-02-22 15:32 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 [this message]
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
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=1235316628.28069.2.camel@localhost \
    --to=dcbw@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --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).