ENUM IEEE80211_ROC_TYPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum ieee80211_roc_type(9) β€” the remain-on-channel type, bestie ✨

okay so this page is from the Kernel API Manual, and it's literally about enum ieee80211_roc_type β€” the remain on channel type. That's the name, that's the vibe, no cap. πŸŽ€


🌸 NAME 🌸

enum ieee80211_roc_type β€” remain on channel type. It's the enum that tags what kind of ROC moment you're requesting, and yes it's giving tiny-but-important. πŸ¦‹


✨ SYNOPSIS ✨

enum ieee80211_roc_type {
    IEEE80211_ROC_TYPE_NORMAL ,
    IEEE80211_ROC_TYPE_MGMT_TX

};

πŸŽ€ Constants πŸŽ€

  • IEEE80211_ROC_TYPE_NORMAL β€” bestie, there are literally no special requirements for this ROC. It's the chill one. 🫢
  • IEEE80211_ROC_TYPE_MGMT_TX β€” this remain on channel request is required for sending management frames offchannel. That's the whole assignment. πŸ’…

πŸ’– Description πŸ’–

okay so with the support for multi channel contexts and multi channel operations, remain on channel operations might be limited, deferred, or aborted by other flows/operations that have higher priority β€” and vice versa, fr fr. Specifying the ROC type can be used by devices to prioritize the ROC operations compared to other operations/flows. It's giving scheduler main character energy, but for wireless. 😭


πŸ¦‹ SEE ALSO πŸ¦‹

the whole extended friend group, no cap:


mwah πŸ’‹ β€” signing off from the Kernel API Manual, source ./include/net, dated October 2026, title enum ieee80211_roc_type(9). That's the footer, bestie, and it ate. πŸ‘‘

πŸ“¦ where this page comes from