From: Jouni Malinen <j@w1.fi>
To: "Peer, Ilan" <ilan.peer@intel.com>
Cc: Ben Greear <greearb@candelatech.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] mac80211_hwsim: Set VHT capabilities only for the 5.2 GHz band
Date: Thu, 9 Apr 2015 10:35:25 +0300 [thread overview]
Message-ID: <20150409073525.GA21000@w1.fi> (raw)
In-Reply-To: <CB3B3D4774441E42AA3EA0E1BA8230A04D09BD1B@HASMSX106.ger.corp.intel.com>
On Wed, Apr 08, 2015 at 06:29:38PM +0000, Peer, Ilan wrote:
> According to the 802.11ac amendment: "The IEEE 802.11 VHT STA operates in frequency bands below 6 GHz excluding the 2.4 GHz band", so at least the spec. is clear about it. However, I guess it would be possible to enable VHT for 2.4 as well to enjoy some of benefits, but do you see a reason/use case to enable it also for hwsim?
It does not matter what the standard says on VHT in general; there are
clearly already products out there that allow some capabilities defined
in 802.11ac (mainly, 256-QAM) to be used on the 2.4 GHz band. As far as
hwsim is concerned, I'm already using it to verify the negotiation part
for this (see ap_vht_on_24ghz test case). The main remaining question
for cfg80211/nl80211 is on whether we can come up with a clean way of
advertising driver capability for doing this.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2015-04-09 7:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 16:05 [PATCH 1/2] mac80211_hwsim: Set VHT capabilities only for the 5.2 GHz band Ilan Peer
2015-04-07 16:05 ` [PATCH 2/2] mac80211_hwsim: Fix the supported VHT mcs rates Ilan Peer
2015-04-07 16:08 ` [PATCH 1/2] mac80211_hwsim: Set VHT capabilities only for the 5.2 GHz band Ben Greear
2015-04-08 18:29 ` Peer, Ilan
2015-04-08 18:41 ` Johannes Berg
2015-04-08 18:41 ` Ben Greear
2015-04-09 7:35 ` Jouni Malinen [this message]
2015-04-09 11:01 ` Krishna Chaitanya
2015-04-10 10:39 ` Johannes Berg
2015-04-10 14:16 ` Jouni Malinen
2015-05-06 12:53 ` 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=20150409073525.GA21000@w1.fi \
--to=j@w1.fi \
--cc=greearb@candelatech.com \
--cc=ilan.peer@intel.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 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).