From: Johannes Berg <johannes@sipsolutions.net>
To: "Pedersen, Thomas" <twp@qca.qualcomm.com>,
Ben Greear <greearb@candelatech.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: cap 20MHz VHT bitrate at MCS 8
Date: Mon, 12 Sep 2016 08:43:57 +0200 [thread overview]
Message-ID: <1473662637.4201.2.camel@sipsolutions.net> (raw)
In-Reply-To: <38049c4f-da5b-a6ec-bcc4-c803197abcd7@qca.qualcomm.com>
On Wed, 2016-09-07 at 18:20 +0000, Pedersen, Thomas wrote:
> On 09/06/2016 12:07 PM, Ben Greear wrote:
> >
> > On 09/06/2016 12:00 PM, Thomas Pedersen wrote:
> > >
> > > Some drivers (ath10k) report MCS 9 @ 20MHz, which
> > > technically isn't allowed. To get more meaningful value
> > > than 0 out of this however, just cap the bitrate for 20MHz
> > > to MCS 8.
> >
> > If it is actually reporting MCS9, why lie about it? Report it up
> > the stack as a proper value instead of hiding the issue?
>
> Good point, will send a v2 extrapolating the value to 86.5Mb/s.
That makes no sense either, IMHO.
Are you saying that ath10k actually somehow manages to use an invalid
bitrate over the air?!
It seems more likely that it's actually just misreporting what it's
doing, and thus the issue should be fixed in ath10k.
johannes
next prev parent reply other threads:[~2016-09-12 6:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 19:00 [PATCH] cfg80211: cap 20MHz VHT bitrate at MCS 8 Thomas Pedersen
2016-09-06 19:07 ` Ben Greear
2016-09-07 18:20 ` Pedersen, Thomas
2016-09-12 6:43 ` Johannes Berg [this message]
2016-09-12 16:36 ` Ben Greear
2016-09-13 17:57 ` Pedersen, Thomas
2016-09-13 18:02 ` Johannes Berg
2016-09-16 18:31 ` Pedersen, Thomas
2016-09-19 9:00 ` Johannes Berg
2016-09-19 9:31 ` Arend Van Spriel
2016-09-19 16:19 ` Ben Greear
2016-10-04 9:32 ` Johannes Berg
2016-10-04 16:31 ` Ben Greear
2016-10-13 12:52 ` Johannes Berg
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=1473662637.4201.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=twp@qca.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 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.