From: Shay Bar <shay.bar@celeno.com>
To: Wen Gong <wgong@codeaurora.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, aviad.brikman@celeno.com,
eliav.farber@celeno.com, linux-wireless-owner@vger.kernel.org,
ath11k@lists.infradead.org
Subject: Re: [PATCH] wireless: fix wrong 160/80+80 MHz setting
Date: Wed, 30 Dec 2020 17:02:06 +0200 [thread overview]
Message-ID: <212736b1-43eb-a27d-c83d-68f669c8d9df@celeno.com> (raw)
In-Reply-To: <34893f267fa37b43d21c19d4c08c090e@codeaurora.org>
On 30/12/2020 12:57, Wen Gong wrote:
>
> On 2020-08-26 22:31, Shay Bar wrote:
>> Fix cfg80211_chandef_usable():
>> consider IEEE80211_VHT_CAP_EXT_NSS_BW when verifying 160/80+80 MHz.
>>
> When station with below 2 bit and connect to a 160MHZ 11ac mode AP, it
> will try to use 160Mhz width after this patch,
> but it does not support 160M in fact according spec of IEEE 802.11
> .... .... .... .... .... .... .... 00.. = Supported Channel Width Set:
> Neither 160MHz nor 80+80 supported (0x0)
> 01.. .... .... .... .... .... .... .... = Extended NSS BW Support: 0x1
>
> refer to spec of IEEE 802.11.
> Table 9-250—Setting of the Supported Channel Width Set subfield and
> Extended NSS BW Support subfield at a STA transmitting the VHT
> Capabilities Information field
> value of the 160Mhz is 1/2 in the table for upper configure.
> NOTE 2—1/2× or 3/4× Max VHT NSS support might end up being 0, indicating
> no support.
>
You mean for AP's with 1 SS for example ?
WARNING: multiple messages have this Message-ID (diff)
From: Shay Bar <shay.bar@celeno.com>
To: Wen Gong <wgong@codeaurora.org>
Cc: linux-wireless-owner@vger.kernel.org,
linux-wireless@vger.kernel.org, aviad.brikman@celeno.com,
Johannes Berg <johannes@sipsolutions.net>,
eliav.farber@celeno.com, ath11k@lists.infradead.org
Subject: Re: [PATCH] wireless: fix wrong 160/80+80 MHz setting
Date: Wed, 30 Dec 2020 17:02:06 +0200 [thread overview]
Message-ID: <212736b1-43eb-a27d-c83d-68f669c8d9df@celeno.com> (raw)
In-Reply-To: <34893f267fa37b43d21c19d4c08c090e@codeaurora.org>
On 30/12/2020 12:57, Wen Gong wrote:
>
> On 2020-08-26 22:31, Shay Bar wrote:
>> Fix cfg80211_chandef_usable():
>> consider IEEE80211_VHT_CAP_EXT_NSS_BW when verifying 160/80+80 MHz.
>>
> When station with below 2 bit and connect to a 160MHZ 11ac mode AP, it
> will try to use 160Mhz width after this patch,
> but it does not support 160M in fact according spec of IEEE 802.11
> .... .... .... .... .... .... .... 00.. = Supported Channel Width Set:
> Neither 160MHz nor 80+80 supported (0x0)
> 01.. .... .... .... .... .... .... .... = Extended NSS BW Support: 0x1
>
> refer to spec of IEEE 802.11.
> Table 9-250—Setting of the Supported Channel Width Set subfield and
> Extended NSS BW Support subfield at a STA transmitting the VHT
> Capabilities Information field
> value of the 160Mhz is 1/2 in the table for upper configure.
> NOTE 2—1/2× or 3/4× Max VHT NSS support might end up being 0, indicating
> no support.
>
You mean for AP's with 1 SS for example ?
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-12-30 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 14:31 [PATCH] wireless: fix wrong 160/80+80 MHz setting Shay Bar
2020-12-30 10:57 ` Wen Gong
2020-12-30 10:57 ` Wen Gong
2020-12-30 15:02 ` Shay Bar [this message]
2020-12-30 15:02 ` Shay Bar
2021-05-19 7:23 ` Wen Gong
2021-05-19 7:23 ` Wen Gong
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=212736b1-43eb-a27d-c83d-68f669c8d9df@celeno.com \
--to=shay.bar@celeno.com \
--cc=ath11k@lists.infradead.org \
--cc=aviad.brikman@celeno.com \
--cc=eliav.farber@celeno.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wgong@codeaurora.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.