From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ben Greear <greearb@candelatech.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz
Date: Tue, 26 Apr 2016 12:03:03 +0000 [thread overview]
Message-ID: <87mvogy3ux.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1461654272.16188.4.camel@sipsolutions.net> (Johannes Berg's message of "Tue, 26 Apr 2016 09:04:32 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Thu, 2016-04-21 at 08:15 -0700, Ben Greear wrote:
>
>> 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.
>
> This patch has no implications on HT, and I wasn't planning on applying
> the mac80211 patch.
Yeah, makes sense. I'm planning to apply this soon.
> As I said, I have no objections to doing the (Broadcom) vendor specific
> IEs for "VHT" in 2.4 GHz band, but I don't think we should advertise
> the spec IEs when they're explicitly specified to be used only in the
> 5.2 GHz band.
But we really should have this, any volunteers? :) I think it shouldn't
be too hard to do so this would be a good project for someone looking
for a simple, but useful, task on wireless stack.
--
Kalle Valo
next prev parent reply other threads:[~2016-04-26 12:03 UTC|newest]
Thread overview: 11+ 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-26 7:04 ` Johannes Berg
2016-04-26 12:03 ` Valo, Kalle [this message]
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=87mvogy3ux.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).