From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: j@w1.fi, greearb@candelatech.com
Subject: Re: [RFC 3/4] ieee80211: add new VHT capability fields/parsing
Date: Tue, 14 Feb 2017 14:06:14 +0100 [thread overview]
Message-ID: <1487077574.4705.13.camel@sipsolutions.net> (raw)
In-Reply-To: <20170214112827.28216-3-johannes@sipsolutions.net> (sfid-20170214_123003_071861_B32E46B9)
> +static inline int ieee80211_get_vht_max_nss(struct ieee80211_vht_cap
> *cap,
> + enum
> ieee80211_vht_chanwidth bw)
> +{
> + unsigned long w;
> + int max_vht_nss;
> + int ext_nss_bw;
> + int supp_width;
> +
> + if (cap->supp_mcs.rx_mcs_map == 0xffff)
> + return 0;
Apart from the various endian issues, this function is completely wrong
because the max_vht_nss is per MCS (at least 0-7, 8 and 9 separately),
which this can't take into account.
Also, the only code that would use this right now, in mac80211,
probably won't use the same types as the parameters were to this
function.
I want to preserve the strange table somewhere in a single place, but
not sure yet how to do that best.
johannes
next prev parent reply other threads:[~2017-02-14 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 11:28 [RFC 1/4] ieee80211: rename CCFS1/CCFS2 to CCFS0/CCFS1 Johannes Berg
2017-02-14 11:28 ` [RFC 2/4] ieee80211: define HT operation CCFS2 field Johannes Berg
2017-02-14 11:28 ` [RFC 3/4] ieee80211: add new VHT capability fields/parsing Johannes Berg
2017-02-14 13:06 ` Johannes Berg [this message]
2017-02-14 11:28 ` [RFC 4/4] mac80211: add ability to parse CCFS2 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=1487077574.4705.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=j@w1.fi \
--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.