ENUM IEEE80211_VHT_MCS_SUPPORT(9)
π enum ieee80211_vht_mcs_support β the kernel API manual, bestie edition π
Okay so picture this: you're deep in the kernel API manual (yes, the kernel API manual, we're fancy now β¨) and you bump into enum ieee80211_vht_mcs_support. That's the whole name, that's the vibe. It's the little enum that's about to tell you which MCSes you get for how many streams. Iconic behaviour, honestly.
πΈ NAME πΈ
enum ieee80211_vht_mcs_support β VHT MCS support definitions. That's it, that's the whole job. She defines things. She supports MCSes. She's booked and busy π
β¨ SYNOPSIS β¨
Like, here's the actual shape of her, no cap:
enum ieee80211_vht_mcs_support {
IEEE80211_VHT_MCS_SUPPORT_0_7 ,
IEEE80211_VHT_MCS_SUPPORT_0_8 ,
IEEE80211_VHT_MCS_SUPPORT_0_9 ,
IEEE80211_VHT_MCS_NOT_SUPPORTED
};
Four constants, all in a row, looking cute. Slay π«Ά
π¦ Constants π¦
IEEE80211_VHT_MCS_SUPPORT_0_7β MCSes0-7are supported for the number of streams. Lowkey the modest one, but she's valid πIEEE80211_VHT_MCS_SUPPORT_0_8β MCSes0-8are supported. One more, more to love πIEEE80211_VHT_MCS_SUPPORT_0_9β MCSes0-9are supported. Main character energy, truly πIEEE80211_VHT_MCS_NOT_SUPPORTEDβ this number of streams isn't supported. It's giving "we don't do that here" π no hate, just boundaries.
π§ Description π§
So here's where it gets good, bestie. These definitions live in each 2-bit subfield of the rx_mcs_map and tx_mcs_map fields of struct ieee80211_vht_mcs_info β and both of those are split into 8 subfields by number of streams. Eight! Subfields! Everywhere! π
What these values do is indicate which MCSes are supported for the number of streams that the value appears for. That's the flex. That's the whole point. Periodt.
π₯ SEE ALSO π₯
- Kernel file
./include/linux/ieee80211-vht.henumieee80211_vht_opmode_bits(9) struct ieee80211_vht_mcs_info(9)struct ieee80211_vht_cap(9)enum ieee80211_vht_chanwidth(9)struct ieee80211_vht_operation(9)ieee80211_get_vht_max_nss(9)
Go read them, iykyk, they're all besties too π
Fr fr though: these are enum constants in a kernel header, so don't go treating them like runtime values you can just poke at β they're definitions, and they mean exactly what they say here. Use them like the constants they are, and you'll be fine π
And that's a wrap, gorgeous π¦ this page ships from ./include/linux and its date stamp says October 2026 β so like, it's from the future, obviously, because she ate. π
β¨πΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms