From: Ben Greear <greearb@candelatech.com>
To: ath10k <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: VHT 20Mhz, MCS 9 RX rate reported by (my) ath10k
Date: Mon, 4 Jan 2016 11:00:29 -0800 [thread overview]
Message-ID: <568AC14D.4000102@candelatech.com> (raw)
While trying to track down some funny results from 'iw station dump',
I find that my ath10k NIC is occasionally reporting MCS 9, 20Mhz bandwidth,
which I guess must be an invalid rate.
This is with non-stock firmware and patched driver, but I have mostly messed
with the TX rate reporting, not RX rate, so I'm not sure this is a local
issue.
Previously, I have also verified that ath10k can send and receive CCK rates
on 5Ghz, which is also evidently not supposed to be valid, so I'm suspicious
that maybe it can do MCS 9 at 20Mhz as well. Or, maybe it is just reporting
bogus values.
Either way, I'd like it to do better than show a zero rate in the
station dump. Any suggestions for the least-bad way to report a
non-zero rate when I have a NIC reporting this rate info?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2016-01-04 19:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=568AC14D.4000102@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).