STRUCT IEEE80211_EHT_CAP_ELEM_FIXED(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct ieee80211_eht_cap_elem_fixed πŸ’–

okay so bestie, we're deep in the ieee80211 kernel headers today β€” this one's from the Kernel API Manual, page struct ieee...p_elem_fixed(9) if you're searching for it. it's a tiny struct with big main character energy and honestly? obsessed.


✨ NAME ✨

struct ieee80211_eht_cap_elem_fixed β€” the EHT capabilities fixed data. yeah. that's the whole vibe. it's the fixed-size part, bestie, and it slays.


πŸŽ€ SYNOPSIS πŸŽ€

look at her. she's so small. she's so powerful.

struct ieee80211_eht_cap_elem_fixed {
    u8 mac_cap_info[2];
    u8 phy_cap_info[9];
};

two bytes and nine bytes and suddenly we're doing Extremely High Throughput. no cap.


🌸 MEMBERS 🌸

  • mac_cap_info β€” the MAC capabilities, a little u8[2] of pure potential ✨ go check out IEEE80211_EHT_MAC_CAP* for the actual lore, iykyk
  • phy_cap_info β€” the PHY capabilities, u8[9] this time because the physical layer has a lot to say πŸ’… the details live in IEEE80211_EHT_PHY_CAP*

πŸ¦‹ DESCRIPTION πŸ¦‹

so what even is this? it's the "EHT Capabilities element" fixed fields β€” like, the chunky non-optional head of the element β€” exactly as described in P802.11be_D2.0 section 9.4.2.313. if you need to cite your sources for the group chat, that's the citation 🫢

heads up: the spec reference is to the draft P802.11be_D2.0, so keep that exact string β€” don't go "fixing" it to some final version, bestie. fr fr. πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

this struct does NOT show up alone, she rolls with an entire entourage. like, an iconic friend group:

that's twenty-six entries and a header path, and yes, we listed every single one, because we do NOT skip the boring parts here πŸ’œ


🌈 sign-off 🌈

this lil page lives in ./include/linux, stamped October 2026, and it's filed under the manual page struct ieee...p_elem_fixed(9). go read the headers, bestie, they ate and left no crumbs. periodt. πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from