linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Peer, Ilan" <ilan.peer@intel.com>,
	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: Fri, 10 Apr 2015 17:16:30 +0300	[thread overview]
Message-ID: <20150410141630.GA24572@w1.fi> (raw)
In-Reply-To: <1428662388.1890.8.camel@sipsolutions.net>

On Fri, Apr 10, 2015 at 12:39:48PM +0200, Johannes Berg wrote:
> On Thu, 2015-04-09 at 10:35 +0300, Jouni Malinen wrote:
> > 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).
> 
> Oh, I guess I can't apply this patch then. But perhaps we should make
> this an optional capability so we can create a new virtual radio
> with/without it.

Well.. It did not look like this patch on its own would actually break
the test since there is no reliable way of indicating support for this
special case nor really any part in the test to verify that the special
TX rates were used (rate control does not even support them for hwsim).

> > 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.
> 
> I'm not even sure what the question really is. Really you want just high
> MCSes, but what should happen OTA? Is interoperability even *desired*,
> given that it will never be tested?

For now, it looks like there is interoperability between vendors as long
as there is agreement on which vendor specific extensions to use for
advertising it. hostapd has an implementation that matches the one used
by number of Broadcom devices. I'd say that interoperability is desired.
I'm not sure what you mean with interoperability never being tested,
though. There may not be a formal certification program for this, but
this has been tested.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2015-04-10 14:16 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
2015-04-09 11:01       ` Krishna Chaitanya
2015-04-10 10:39       ` Johannes Berg
2015-04-10 14:16         ` Jouni Malinen [this message]
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=20150410141630.GA24572@w1.fi \
    --to=j@w1.fi \
    --cc=greearb@candelatech.com \
    --cc=ilan.peer@intel.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).