From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz
Date: Tue, 26 Apr 2016 09:04:32 +0200 [thread overview]
Message-ID: <1461654272.16188.4.camel@sipsolutions.net> (raw)
In-Reply-To: <5718EE7A.4030503@candelatech.com> (sfid-20160421_171514_734039_B1F3CF8F)
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.
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.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] ath10k: remove VHT capabilities from 2.4GHz
Date: Tue, 26 Apr 2016 09:04:32 +0200 [thread overview]
Message-ID: <1461654272.16188.4.camel@sipsolutions.net> (raw)
In-Reply-To: <5718EE7A.4030503@candelatech.com> (sfid-20160421_171514_734039_B1F3CF8F)
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.
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.
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-04-26 7:04 UTC|newest]
Thread overview: 24+ 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 13:17 ` Kalle Valo
2016-04-21 15:15 ` Ben Greear
2016-04-21 15:15 ` Ben Greear
2016-04-21 20:09 ` Sebastian Gottschall
2016-04-21 23:07 ` Michael Ney
2016-04-26 7:04 ` Johannes Berg [this message]
2016-04-26 7:04 ` Johannes Berg
2016-04-26 12:03 ` Valo, Kalle
2016-04-26 12:03 ` Valo, Kalle
2016-04-26 20:07 ` Krishna Chaitanya
2016-04-26 20:07 ` Krishna Chaitanya
2016-04-26 20:10 ` Ben Greear
2016-04-26 20:10 ` Ben Greear
2016-04-27 6:43 ` Krishna Chaitanya
2016-04-27 6:43 ` Krishna Chaitanya
2016-04-27 9:16 ` Jouni Malinen
2016-04-27 9:16 ` Jouni Malinen
2016-04-27 9:37 ` Krishna Chaitanya
2016-04-27 9:37 ` Krishna Chaitanya
2016-04-27 9:45 ` Johannes Berg
2016-04-27 9:45 ` Johannes Berg
2016-05-06 18:08 ` Valo, Kalle
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=1461654272.16188.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=kvalo@qca.qualcomm.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.