From: frank agius <ftagius@yahoo.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ATH10K set bitrates problem
Date: Mon, 09 Jun 2014 07:43:30 -0400 [thread overview]
Message-ID: <53959DE2.7050906@yahoo.com> (raw)
On 6/6/2014 2:43 PM, Janusz Dziedzic wrote:
> On 6 June 2014 18:43, Frank Agius <ftagius@yahoo.com> wrote:
>> I am unable to set the bitrates for devices using the ath10k driver,
>> regardless of the arguments I pass:
>>
>>
>> # iw wlan0 set bitrates legacy-2.4 6 12 24
>> command failed: Invalid argument (-22)
>> # iw dev wlan0 set bitrates mcs-2.4 10
>> command failed: Invalid argument (-22)
>>
>>
>> The ath10k drivers were built from stable backports v3.15-rc1. I
am using
>> firmware file firmware-2.bin_999.999.0.636
>>
>>
>> Is this a known issue?
>>
> This is expected.
> ath10k support only single rate setting (or single nss). So, please
> check commit message,
> ath10k: add set_bitrate_mask callback
>
> Try this:
> iw wlan0 set bitrates legacy-2.4 18 ht-mcs-2.4
> iw wlan0 set bitrates legacy-2.4 ht-mcs-2.4 6
> iw wlan0 set bitrates - back to default mask.
Thanks, using the bitrate option ht-mcs-2.4 instead of mcs-2.4 worked.
Note that I did have to upgrade the iw tools package. The version I was
using (3.11) does not have support for bitrate option ht-mcs. Version
3.15 of iw tools does support the new options.
frank agius
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2014-06-09 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 11:43 frank agius [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-06 16:43 ATH10K set bitrates problem Frank Agius
2014-06-06 18:43 ` Janusz Dziedzic
2014-06-06 19:35 ` frank agius
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=53959DE2.7050906@yahoo.com \
--to=ftagius@yahoo.com \
--cc=ath10k@lists.infradead.org \
--cc=janusz.dziedzic@tieto.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