linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@freenet.de>
To: Helmut Schaa <helmut.schaa@googlemail.com>,
	Arend van Spriel <arend@broadcom.com>
Cc: Sourav <sourav.chakraborty@netcommwireless.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Not reaching optimum speeds with IEEE 802.11n
Date: Wed, 10 Sep 2014 17:18:08 +0200	[thread overview]
Message-ID: <54106BB0.1090105@maya.org> (raw)
In-Reply-To: <CAGXE3d9FRLOPQ1pO6WFWy4FF67PGbo5ztfhLELydq3k410731w@mail.gmail.com>

Hello Helmut!

Helmut Schaa wrote:
> On Wed, Sep 10, 2014 at 10:42 AM, Arend van Spriel <arend@broadcom.com> wrote:
>> On 09/10/14 03:26, Sourav wrote:
>>> We are using Ralink chip Rt3072L (using rt2800usb drivers rt2800usb.c),
> 
> The Ralink USB hardware is quite bad in reporting TX status and as
> such minstrel_ht cannot do proper rate selection.

Rate control of the vendor driver seems to work just fine (or at least
better as minstrel_ht).

Iow: minstrel_ht doesn't meet the requirements of ralink chipsets :-).

But this is not the only problem of rt2800usb. As long as a driver has
the ability to damage a device [1], there is something more basically
broken!


[1] http://thread.gmane.org/gmane.linux.kernel.wireless.general/126856


Regards,
Andreas

  reply	other threads:[~2014-09-10 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10  1:26 Not reaching optimum speeds with IEEE 802.11n Sourav
2014-09-10  8:42 ` Arend van Spriel
2014-09-10 14:14   ` Helmut Schaa
2014-09-10 15:18     ` Andreas Hartmann [this message]
2014-09-11 10:15       ` Helmut Schaa
2014-09-12  2:11     ` Sourav
2014-09-12  7:46       ` Helmut Schaa
     [not found]         ` <5412A831.3050804@netcommwireless.com>
2014-09-18  8:53           ` Sourav
2014-09-10 14:53 ` Andreas Hartmann

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=54106BB0.1090105@maya.org \
    --to=andihartmann@freenet.de \
    --cc=arend@broadcom.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sourav.chakraborty@netcommwireless.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).