From: Shay Bar <shay.bar@celeno.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, aviad.brikman@celeno.com,
eliav.farber@celeno.com
Subject: Re: [PATCH v3 v3] mac80211: 160MHz support per IEEE802.11ax standard
Date: Sun, 8 Nov 2020 10:11:39 +0200 [thread overview]
Message-ID: <4f38e1cf-fc8c-c9fd-e064-e433a8b82186@celeno.com> (raw)
In-Reply-To: <9a043fdcf1c6324688f4c92b18f31c267969f5fc.camel@sipsolutions.net>
On 06/11/2020 12:35, Johannes Berg wrote:
> External Email
>
>
> On Mon, 2020-10-19 at 16:26 +0300, Shay Bar wrote:
>> According to the new IEEE802.11ax standard center frequency of the 160MHz
>> should be published in segment2 field of HT operation IE when using EXT NSS
>> (when supporting smaller number of NSS in VHT in 160MHz BW).
>> This patch adds the required support to mac80211, cfg80211 to parse it properly
>> according to the new style as appears in the new standard.
>>
>> According to the new style, the AP should publish that its bw is 80MHz and not
>> 160MHz.
>> A STA should conclude that an AP is working in 160MHz if it publishes
>> the center frequency of the 160MHz bandwidth in seg1 field of VHT operation IE
>> or seg2 field of HT operation IE.
> Is this referring to D6.2 Table 26-9 "Setting of the VHT Channel Width
> and VHT NSS at an HE STA transmitting the OM Control subfield"?
No, it is referring to IEEE P802.11-REVmd™/D5.0, September 2020 Table
9-81- "Setting of the Channel Width subfield and 160/80+80 BW subfield
at a VHT STA transmitting the Operating Mode field" (where it doesn't
refer to OM)
The nl80211.c change is also described in the first 3 rows of Table
9-274 "VHT Operation Information subfields".
next prev parent reply other threads:[~2020-11-08 8:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:18 [PATCH] mac80211: 160MHz support per IEEE802.11ax standard Shay Bar
2020-10-12 16:44 ` kernel test robot
2020-10-12 16:44 ` kernel test robot
2020-10-12 17:08 ` kernel test robot
2020-10-12 17:08 ` kernel test robot
2020-10-19 6:39 ` [PATCH v2] " Shay Bar
2020-10-19 13:26 ` [PATCH v3 v3] " Shay Bar
2020-11-06 10:35 ` Johannes Berg
2020-11-08 8:11 ` Shay Bar [this message]
2020-11-13 9:04 ` Johannes Berg
2020-11-15 8:57 ` Shay Bar
2020-12-11 12:22 ` Johannes Berg
2020-12-21 14:25 ` Shay Bar
2020-12-21 14:14 ` [PATCH] mac80211: 160Mhz with extended NSS BW in CSA Shay Bar
2020-12-22 6:47 ` Shay Bar
2020-12-11 12:28 ` [PATCH v2] mac80211: 160MHz support per IEEE802.11ax standard 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=4f38e1cf-fc8c-c9fd-e064-e433a8b82186@celeno.com \
--to=shay.bar@celeno.com \
--cc=aviad.brikman@celeno.com \
--cc=eliav.farber@celeno.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.