All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arik Nemtsov <arik@wizery.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] mac80211: Let VHT work on 2.4Ghz
Date: Tue, 23 Feb 2016 12:47:00 +0200	[thread overview]
Message-ID: <CA+XVXffpNDf0-5a6cPz0aUrrRfHgKQeu09zDt5eSe1K87m__pw@mail.gmail.com> (raw)
In-Reply-To: <1456180974-21062-1-git-send-email-greearb@candelatech.com>

On Tue, Feb 23, 2016 at 12:42 AM, <greearb@candelatech.com> wrote:
>
> From: Ben Greear <greearb@candelatech.com>
>
> ath10k supports VHT on 2.4Ghz band.
> If supplicant and hostapd and radio think
> VHT should be allowed, then kernel should let them
> try.

Removing the 80Mhz check entirely is not the right way to go IMO. The
check is there because there are countries where VHT rates are not
allowed, even on 20MHz channels. We use the fact these countries have
no 80MHz-allowed ranges as a crude regulatory hint to disable VHT
entirely. I'm not sure about the regulatory landscape in these
countries regarding VHT in 2.4GHz, but please don't break compliance
for the 5Ghz use-case.

Arik

  parent reply	other threads:[~2016-02-23 10:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 22:42 [PATCH] mac80211: Let VHT work on 2.4Ghz greearb
2016-02-22 22:48 ` Julian Calaby
2016-02-22 22:55   ` Ben Greear
2016-02-23 10:47 ` Arik Nemtsov [this message]
2016-02-23 13:46   ` Ben Greear
2016-02-24  8:40     ` Arik Nemtsov
2016-02-24 13:24       ` Ben Greear
2016-02-24 13:32         ` Arik Nemtsov
2016-02-24 13:37           ` Ben Greear
2016-02-24 14:25             ` Arik Nemtsov
2016-02-23 14:10 ` Johannes Berg
2016-02-23 14:18   ` Ben Greear
2016-02-23 14:22     ` Johannes Berg
2016-02-23 14:58       ` Ben Greear
2016-02-23 21:08   ` Jouni Malinen
2016-02-23 21:15     ` Ben Greear

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=CA+XVXffpNDf0-5a6cPz0aUrrRfHgKQeu09zDt5eSe1K87m__pw@mail.gmail.com \
    --to=arik@wizery.com \
    --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 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.