linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] mac80211: Let VHT work on 2.4Ghz
Date: Mon, 22 Feb 2016 14:55:14 -0800	[thread overview]
Message-ID: <56CB91D2.2080404@candelatech.com> (raw)
In-Reply-To: <CAGRGNgWPv89sWV9wtXPBpothJrebRJ+d6a8-TnDU0o-p6ZkAmA@mail.gmail.com>

On 02/22/2016 02:48 PM, Julian Calaby wrote:
> Hi Ben,
>
> On Tue, Feb 23, 2016 at 9: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.
>>
>> Signed-off-by: Ben Greear <greearb@candelatech.com>
>> ---
>>   net/mac80211/mlme.c | 16 ----------------
>>   net/mac80211/util.c | 13 +------------
>>   net/mac80211/vht.c  | 15 ---------------
>>   3 files changed, 1 insertion(+), 43 deletions(-)
>>
>> diff --git a/net/mac80211/util.c b/net/mac80211/util.c
>> index f8eb0f8..cabe16f 100644
>> --- a/net/mac80211/util.c
>> +++ b/net/mac80211/util.c
>> @@ -1604,17 +1603,7 @@ static int ieee80211_build_preq_ies_band(struct ieee80211_local *local,
>>                  *offset = noffset;
>>          }
>>
>> -       /* Check if any channel in this sband supports at least 80 MHz */
>> -       for (i = 0; i < sband->n_channels; i++) {
>> -               if (sband->channels[i].flags & (IEEE80211_CHAN_DISABLED |
>> -                                               IEEE80211_CHAN_NO_80MHZ))
>> -                       continue;
>> -
>> -               have_80mhz = true;
>> -               break;
>> -       }
>> -
>> -       if (sband->vht_cap.vht_supported && have_80mhz && !disable_vht) {
>> +       if (sband->vht_cap.vht_supported && /*have_80mhz &&*/ !disable_vht) {
>
> Do you want to actually remove have_80mhz here? We do have git history
> if this needs to be put back.

Yes, I just missed that when cleaning up my patch.

I'll wait for some other feedback and then do a -v2.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2016-02-22 22:55 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 [this message]
2016-02-23 10:47 ` Arik Nemtsov
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=56CB91D2.2080404@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=julian.calaby@gmail.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).