From: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>, <quic_vikram@quicinc.com>,
<quic_alokad@quicinc.com>, <quic_jiad@quicinc.com>,
<quic_periyasa@quicinc.com>, <quic_msinada@quicinc.com>,
<quic_srirrama@quicinc.com>
Subject: Re: [PATCH 3/6] nl80211: add support to send EHT capabilities from userspace
Date: Fri, 4 Feb 2022 20:07:36 +0530 [thread overview]
Message-ID: <382a29fe-dea3-7d32-2aeb-16ba18e9da28@quicinc.com> (raw)
In-Reply-To: <0c0ba8cebb877384172b5bd314cbbbb035d1f348.camel@sipsolutions.net>
On 2/4/22 1:41 PM, Johannes Berg wrote:
> On Fri, 2022-02-04 at 12:42 +0530, Veerendranath Jakkam wrote:
>>> I calculate only 51, based on the assumption that we can only have
>>> NSS==8. Even if you think NSS==16 (which I doubt), I get to 80 only?
>> So total max length would be 81 bytes
>>
> Right. Now I don't know how I got to 80...
>
> Regardless, I don't think NSS>8 is actually valid, the PHY spec always
> says it's max of 8, so I think we can safely limit to 51?
>
> johannes
There are some references for NSS > 8, ex: Table 9-33a, P802.11be_D1.3
hence I used 81.
Please let me know if you would like this to be changed to 51
next prev parent reply other threads:[~2022-02-04 14:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 9:04 [PATCH 0/6] cfg80211/nl80211: add support for EHT Veerendranath Jakkam
2021-12-22 9:04 ` [PATCH 1/6] ieee80211: add EHT capabilities element definitions Veerendranath Jakkam
2021-12-22 9:04 ` [PATCH 2/6] nl80211: add support to advertise driver's EHT capabilities Veerendranath Jakkam
2022-02-10 5:14 ` Aloka Dixit (QUIC)
2022-02-10 8:26 ` Johannes Berg
2022-02-10 11:17 ` Johannes Berg
2022-02-10 15:57 ` Aloka Dixit (QUIC)
2022-02-10 16:29 ` Johannes Berg
2021-12-22 9:04 ` [PATCH 3/6] nl80211: add support to send EHT capabilities from userspace Veerendranath Jakkam
2022-02-03 12:45 ` Johannes Berg
2022-02-04 7:12 ` Veerendranath Jakkam
2022-02-04 8:11 ` Johannes Berg
2022-02-04 14:37 ` Veerendranath Jakkam [this message]
2022-02-04 14:43 ` Johannes Berg
2022-02-04 17:43 ` Veerendranath Jakkam
2022-02-04 17:45 ` Johannes Berg
2022-02-04 18:28 ` Veerendranath Jakkam
2022-02-03 12:47 ` Johannes Berg
2022-02-04 7:18 ` Veerendranath Jakkam
2021-12-22 9:04 ` [PATCH 4/6] cfg80211: Add support for EHT 320 MHz channel width Veerendranath Jakkam
2021-12-22 9:04 ` [PATCH 5/6] nl80211: add support for 320MHz channel limitation Veerendranath Jakkam
2021-12-22 9:04 ` [PATCH 6/6] nl80211: add EHT MCS support Veerendranath Jakkam
2022-02-04 14: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=382a29fe-dea3-7d32-2aeb-16ba18e9da28@quicinc.com \
--to=quic_vjakkam@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_alokad@quicinc.com \
--cc=quic_jiad@quicinc.com \
--cc=quic_msinada@quicinc.com \
--cc=quic_periyasa@quicinc.com \
--cc=quic_srirrama@quicinc.com \
--cc=quic_vikram@quicinc.com \
/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.