From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Martin Steigerwald <Martin@lichtvoll.de>,
linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?)
Date: Tue, 13 Jul 2010 20:19:27 +0200 [thread overview]
Message-ID: <20100713201927.78674c4a@varda> (raw)
In-Reply-To: <20100713153530.GC3835@tuxdriver.com>
El Tue, 13 Jul 2010 11:35:31 -0400
"John W. Linville" <linville@tuxdriver.com> escribió:
>
> The patch (7e0986c1) corrects an obvious error. Reverting it might
> improve your (i.e. Alejandro) performance, but it seems likely to
> cause connectivity problems for others.
>
> The fact that reverting 7e098c1 helps you suggests that rt2500usb
my card is pci so it would be rt2500pci
> isn't using the basic_rates map properly. But after reviewing the
> code and the data I have, I can't see what would be causing that.
> It is at least possible that your AP is sending bad rate information.
> Have you tried this device with other APs?
No; this is a desktop pc that connects to my home router/AP. A new wifi
card is cheaper than a new AP ...
>
> John
next prev parent reply other threads:[~2010-07-13 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007110918.42120.Martin@lichtvoll.de>
[not found] ` <AANLkTimCwi2uJqqPaq3U30f3rvdDizu1BnaaXgvNeC9k@mail.gmail.com>
[not found] ` <201007111651.42963.Martin@lichtvoll.de>
[not found] ` <20100713131112.26a3da54@varda>
2010-07-13 12:50 ` rt2x00: slow wifi with correct basic rate bitmap (was Re: stable? quality assurance?) Stefan Richter
2010-07-13 15:35 ` John W. Linville
2010-07-13 18:19 ` Alejandro Riveira Fernández [this message]
2010-07-13 18:38 ` John W. Linville
2010-07-13 19:07 ` Alejandro Riveira Fernández
2010-07-13 18:06 ` Alejandro Riveira Fernández
2010-07-13 19:18 ` Stefan Richter
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=20100713201927.78674c4a@varda \
--to=ariveira@gmail.com \
--cc=Martin@lichtvoll.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stefanr@s5r6.in-berlin.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).