From: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k + iw set bitrates is causing FW crash
Date: Fri, 22 Jul 2016 11:59:41 +0000 [thread overview]
Message-ID: <1469188781289.75799@qti.qualcomm.com> (raw)
In-Reply-To: <CABPxzYKomhw5rF4Crj6sMbmr3VuuDYi=zqN2ky83v-=RJe7Zhg@mail.gmail.com>
[...]
> >> Thanks Raj, with this fix the rates are 0-7, if i disable then i am
> >> seeing 0-9, so its
> >> working.
> >>
> >> But i am seeing a weird issues, the moment i give bitrates command,
> >> ath10k no longer does encryption, link is a WPA2-PSK: AES. Even after
> >> interface up/down
> >> it doesn't work.
>> After reboot i dont see the "unencrypted" packet issue, i will do
>> some more testing on limiting the rates, currently in my setup its
>> not reaching MCS9 so cannot verify now.
> Rajkumar,
>
> I am still not able to make mcs9 work, so i have tried to change the Nss to 1
> using iw, but that is not taking affect. This command is not taking effect.
>
you mean not able to fix VHT rates alone. am i right? By auto rate mode, is firmware selecting
mcs9? What is the command used for fixing vht rate?
-Rajkumar
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: ath10k + iw set bitrates is causing FW crash
Date: Fri, 22 Jul 2016 11:59:41 +0000 [thread overview]
Message-ID: <1469188781289.75799@qti.qualcomm.com> (raw)
In-Reply-To: <CABPxzYKomhw5rF4Crj6sMbmr3VuuDYi=zqN2ky83v-=RJe7Zhg@mail.gmail.com>
[...]
> >> Thanks Raj, with this fix the rates are 0-7, if i disable then i am
> >> seeing 0-9, so its
> >> working.
> >>
> >> But i am seeing a weird issues, the moment i give bitrates command,
> >> ath10k no longer does encryption, link is a WPA2-PSK: AES. Even after
> >> interface up/down
> >> it doesn't work.
>> After reboot i dont see the "unencrypted" packet issue, i will do
>> some more testing on limiting the rates, currently in my setup its
>> not reaching MCS9 so cannot verify now.
> Rajkumar,
>
> I am still not able to make mcs9 work, so i have tried to change the Nss to 1
> using iw, but that is not taking affect. This command is not taking effect.
>
you mean not able to fix VHT rates alone. am i right? By auto rate mode, is firmware selecting
mcs9? What is the command used for fixing vht rate?
-Rajkumar
next prev parent reply other threads:[~2016-07-22 12:00 UTC|newest]
Thread overview: 33+ 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-07 18:35 ` Krishna Chaitanya
2016-07-08 10:09 ` Manoharan, Rajkumar
2016-07-08 10:09 ` Manoharan, Rajkumar
2016-07-08 11:56 ` Krishna Chaitanya
2016-07-08 11:56 ` Krishna Chaitanya
2016-07-08 12:59 ` Manoharan, Rajkumar
2016-07-08 12:59 ` Manoharan, Rajkumar
2016-07-08 15:27 ` Krishna Chaitanya
2016-07-08 15:27 ` Krishna Chaitanya
2016-07-08 15:37 ` Krishna Chaitanya
2016-07-08 15:37 ` Krishna Chaitanya
2016-07-08 15:39 ` Krishna Chaitanya
2016-07-08 15:39 ` Krishna Chaitanya
2016-07-08 15:42 ` Ben Greear
2016-07-08 15:42 ` Ben Greear
2016-07-08 15:44 ` Krishna Chaitanya
2016-07-08 15:44 ` Krishna Chaitanya
2016-07-08 15:47 ` Ben Greear
2016-07-08 15:47 ` Ben Greear
2016-07-08 15:49 ` Krishna Chaitanya
2016-07-08 15:49 ` Krishna Chaitanya
2016-07-20 10:52 ` Krishna Chaitanya
2016-07-20 10:52 ` Krishna Chaitanya
2016-07-22 11:59 ` Manoharan, Rajkumar [this message]
2016-07-22 11:59 ` Manoharan, Rajkumar
2016-07-22 12:21 ` Krishna Chaitanya
2016-07-22 12:21 ` Krishna Chaitanya
2016-07-22 13:32 ` Ben Greear
2016-07-22 13:32 ` Ben Greear
2016-07-22 14:48 ` Krishna Chaitanya
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=1469188781289.75799@qti.qualcomm.com \
--to=rmanohar@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=chaitanya.mgit@gmail.com \
--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 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.