From: Stefano Brivio <stefano.brivio@polimi.it>
To: "Ivo Van Doorn" <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Chris Clayton" <chris2553@googlemail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
johannes@sipsolutions.net
Subject: Re: 2.6.25-rc2 regression in rt61pci wireless driver
Date: Tue, 26 Feb 2008 22:44:10 +0100 [thread overview]
Message-ID: <20080226224410.4b9216e5@morte> (raw)
In-Reply-To: <a32f33a40802261230o1743773dle38684609d702959@mail.gmail.com>
On Tue, 26 Feb 2008 21:30:38 +0100
"Ivo Van Doorn" <ivdoorn@gmail.com> wrote:
> rt2x00 is known to be less sensitive then the legacy drivers, scanning
> produces less and more inconsistent results (Not all AP's are reported,
> even when that AP has a high rssi), and the reported RSSI is often
> much lower then expected with the distance to the AP.
> I have compared many register dumps, but have never managed to
> find a real register setting that might cause this. So what might be
> the problem is that rt2x00 is not reporting the RSSI correctly to mac80211.
No, we don't care at all about RSSI in rc80211-pid.
> I have to admit that I haven't looked into the 'pid' algorithm closely,
> but could it be that some fields in the tx status report upon txdone
> are being treated as "very important" while the driver doesn't report it
> (For example ack signal strength)?
The only important thing drivers should report back to mac80211 are ACKed
frames. In rc80211-pid (and it's just the same in rc80211-simple) the only
inputs from mac80211 are succesfully (re)transmitted frames and failed
frames.
--
Ciao
Stefano
next prev parent reply other threads:[~2008-02-26 21:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 12:06 2.6.25-rc2 regression in rt61pci wireless driver Chris Clayton
2008-02-18 18:11 ` Ivo van Doorn
2008-02-18 18:16 ` Ivo van Doorn
2008-02-18 22:51 ` Chris Clayton
2008-02-19 9:26 ` Ivo van Doorn
2008-02-19 19:00 ` Chris Clayton
2008-02-19 19:46 ` Ivo van Doorn
2008-02-19 20:44 ` Chris Clayton
2008-02-19 21:03 ` Ivo van Doorn
2008-02-19 23:04 ` [Rt2400-devel] " Chris Vine
2008-02-20 16:05 ` Dan Williams
2008-02-20 20:27 ` Chris Vine
2008-02-20 20:50 ` Ivo van Doorn
2008-02-20 21:16 ` Chris Vine
2008-02-21 21:07 ` Chris Vine
2008-02-21 21:51 ` Ivo van Doorn
2008-02-21 22:46 ` Chris Vine
2008-02-21 22:51 ` Ivo van Doorn
2008-02-21 23:04 ` Chris Clayton
2008-02-21 23:20 ` Chris Vine
2008-02-22 7:39 ` Chris Clayton
2008-02-22 19:11 ` Ivo van Doorn
2008-02-22 20:33 ` Chris Vine
2008-02-20 22:13 ` Chris Clayton
2008-02-22 15:46 ` Chris Clayton
2008-02-22 19:47 ` Ivo van Doorn
2008-02-25 21:04 ` Chris Clayton
2008-02-25 22:09 ` Ivo Van Doorn
2008-02-26 19:11 ` Chris Clayton
2008-02-26 19:48 ` John W. Linville
2008-02-26 20:30 ` Ivo Van Doorn
2008-02-26 21:44 ` Stefano Brivio [this message]
2008-02-26 21:13 ` Chris Clayton
2008-02-26 21:38 ` Stefano Brivio
2008-02-26 22:36 ` Chris Clayton
2008-02-27 7:26 ` Stefano Brivio
2008-02-27 15:51 ` John W. Linville
2008-02-27 17:25 ` John W. Linville
2008-02-27 17:45 ` Chris Clayton
2008-03-02 10:33 ` Stefano Brivio
2008-03-02 15:11 ` Chris Clayton
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=20080226224410.4b9216e5@morte \
--to=stefano.brivio@polimi.it \
--cc=chris2553@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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).