From: Ben Greear <greearb@candelatech.com>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k + iw set bitrates is causing FW crash
Date: Fri, 8 Jul 2016 08:47:16 -0700 [thread overview]
Message-ID: <577FCB04.4030905@candelatech.com> (raw)
In-Reply-To: <CABPxzYLdS-QicOj9AdcubT8uxgw0cqXpzerpuwGcwkSQ7PCiOA@mail.gmail.com>
On 07/08/2016 08:44 AM, Krishna Chaitanya wrote:
> On Fri, Jul 8, 2016 at 9:12 PM, Ben Greear <greearb@candelatech.com> wrote:
>> On 07/08/2016 08:39 AM, Krishna Chaitanya wrote:
>>
>>> Also can you please tell me how to make ath10k use minstrel rc, its needed
>>> for comparative purposes? Is disable HW_RATE_CONTROL enough or does
>>> it need more changes?
>>
>>
>> It cannot be done. You have to use whatever rate-ctrl is baked into the
>> firmware.
> Ok, its a good feature to have.
>
It is unlikely to happen anytime soon. It requires significant firmware
modification (and driver too), and probably you would have to add MU-MIMO
support to minstrel if you wanted to support latest ath10k NICs.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2016-07-08 15:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 16:49 ath10k + iw set bitrates is causing FW crash Krishna Chaitanya
2016-07-07 18:35 ` Krishna Chaitanya
2016-07-08 10:09 ` Manoharan, Rajkumar
2016-07-08 11:56 ` Krishna Chaitanya
2016-07-08 12:59 ` Manoharan, Rajkumar
2016-07-08 15:27 ` Krishna Chaitanya
2016-07-08 15:37 ` Krishna Chaitanya
2016-07-08 15:39 ` Krishna Chaitanya
2016-07-08 15:42 ` Ben Greear
2016-07-08 15:44 ` Krishna Chaitanya
2016-07-08 15:47 ` Ben Greear [this message]
2016-07-08 15:49 ` Krishna Chaitanya
2016-07-20 10:52 ` Krishna Chaitanya
2016-07-22 11:59 ` Manoharan, Rajkumar
2016-07-22 12:21 ` Krishna Chaitanya
2016-07-22 13:32 ` Ben Greear
2016-07-22 14:48 ` Krishna Chaitanya
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=577FCB04.4030905@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=chaitanya.mgit@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@qti.qualcomm.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