From: Danilo <dantard@unizar.es>
To: linux-wireless@vger.kernel.org
Subject: Re: Incoherency in iw (or mac80211 or drivers) behavior -- possible BUG in iwl4965
Date: Thu, 20 Dec 2012 12:58:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20121220T135530-191@post.gmane.org> (raw)
In-Reply-To: CA+XFjir7D5eCMrS+4FTDJdon3RZh4UXRmgzJY7NmRS3Z6RZetg@mail.gmail.com
Gábor Stefanik <netrolller.3d@...> writes:
>
> IIRC iwl4965 uses its own rate control algorithm (a while ago, it was
> called "iwl-agn-rs", before the iwlegacy split). I think you should
> look for the problem there.
>
Thanks for the answer.
In fact I looked at it as well and I tried to force iwl4965 to use 'minstrel' or
'pid' algorithm hacking the code of the mac80211 with scarce success.
Do you know what is the correct way of selecting the desire rate control
algorithm?
Thanks again.
prev parent reply other threads:[~2012-12-20 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 16:41 Incoerency in iw (or mac80211 or drivers) behavior Danilo
2012-12-20 10:25 ` Incoherency in iw (or mac80211 or drivers) behavior -- possible BUG in iwl4965 Danilo
2012-12-20 10:28 ` Gábor Stefanik
2012-12-20 12:58 ` Danilo [this message]
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=loom.20121220T135530-191@post.gmane.org \
--to=dantard@unizar.es \
--cc=linux-wireless@vger.kernel.org \
/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