From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: ath10k@lists.infradead.org
Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz
Date: Thu, 21 Apr 2016 22:09:23 +0200 [thread overview]
Message-ID: <57193373.9060109@dd-wrt.com> (raw)
In-Reply-To: <5718EE7A.4030503@candelatech.com>
Am 21.04.2016 um 17:15 schrieb Ben Greear:
> On 04/21/2016 06:17 AM, Kalle Valo wrote:
>> From: Johannes Berg <johannes.berg@intel.com>
>>
>> According to the spec, VHT doesn't exist in 2.4GHz.
>>
>> There are vendor extensions to allow a subset of VHT to work
>> (notably 256-QAM), but since mac80211 doesn't support those
>> advertising VHT capability on 2.4GHz leads to the behaviour
>> of reporting VHT capabilities but not being able to use any
>> of them due to mac80211's code requiring 80 MHz support.
>>
>> Remove the VHT capabilities from 2.4GHz for now. If mac80211
>> gets extended to use the (likely Broadcom) vendor IEs for it
>> and handles the lack of 80 MHz support, it can be added back.
>>
>> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
>> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
>
> The thing is, it actually works just fine with the patch I posted
> to fix mac80211, and at any rate, even if the mac80211 patch isn't
> applied, the ath10k driver works just fine in HT mode.
>
> Have you actually found any case where the existing behaviour causes
> a real problem?
i agree. other vendor chipsets to support QAM256 as well in 2.4 ghz
(notably broadcom)
this is nonstandard, but since all going the same way it wouldnt be a
great idea to keep QCA out of that extensions.
>
> Thanks,
> Ben
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-21 20:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 13:17 [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz Kalle Valo
2016-04-21 15:15 ` Ben Greear
2016-04-21 20:09 ` Sebastian Gottschall [this message]
2016-04-21 23:07 ` Michael Ney
2016-04-26 7:04 ` Johannes Berg
2016-04-26 12:03 ` Valo, Kalle
2016-04-26 20:07 ` Krishna Chaitanya
2016-04-26 20:10 ` Ben Greear
2016-04-27 6:43 ` Krishna Chaitanya
2016-04-27 9:16 ` Jouni Malinen
2016-04-27 9:37 ` Krishna Chaitanya
2016-04-27 9:45 ` Johannes Berg
2016-05-06 18:08 ` Valo, Kalle
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=57193373.9060109@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=ath10k@lists.infradead.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).