From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
users@rt2x00.serialmonkey.com, gwingerde@gmail.com,
Ivo Van Doorn <ivdoorn@gmail.com>,
Andreas Hartmann <andihartmann@freenet.de>
Subject: Re: Poor RT2880 performance
Date: Thu, 16 Feb 2012 14:00:21 +0100 [thread overview]
Message-ID: <20120216130020.GG25833@redhat.com> (raw)
In-Reply-To: <4F3961FB.7020409@openwrt.org>
On Mon, Feb 13, 2012 at 08:18:19PM +0100, Florian Fainelli wrote:
> Le 02/13/12 14:45, Helmut Schaa a écrit :
> >On Mon, Feb 13, 2012 at 2:23 PM, Florian Fainelli<florian@openwrt.org> wrote:
> >>I am playing with a RT2880-F based AP, with a N connected station, in a
> >>residential environment.
> >Mind to provide the RF and RT chipset identifications? rt2x00 should print them
> >out during module load (at least when compiled with debugging options).
>
> Sure, here are the HW infos of the AP:
> Ralink RT2880 id:1 rev:1 running at 266.66 MHz
> phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 2860, rf:
> 0001, rev: 0101.
Did you try to revert commit (if you use kernel, which include it) ?
commit f0425beda4d404a6e751439b562100b902ba9c98
Author: Felix Fietkau <nbd@openwrt.org>
Date: Sun Aug 28 21:11:01 2011 +0200
mac80211: retry sending failed BAR frames later instead of tearing
It was already identified that it couse performace issues on rt2860
based APs.
Stanislaw
next prev parent reply other threads:[~2012-02-16 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:23 Poor RT2880 performance Florian Fainelli
2012-02-13 13:45 ` Helmut Schaa
2012-02-13 15:05 ` Andreas Hartmann
2012-02-13 19:18 ` Florian Fainelli
2012-02-16 13:00 ` Stanislaw Gruszka [this message]
2012-02-17 8:50 ` Florian Fainelli
2012-02-17 8:52 ` Helmut Schaa
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=20120216130020.GG25833@redhat.com \
--to=sgruszka@redhat.com \
--cc=andihartmann@freenet.de \
--cc=florian@openwrt.org \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.