ieee80211_s..._iftype_data(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_s..._iftype_data(9)

okay bestie, welcome to the Kernel API Manual ✨ this is the page for ieee80211_s..._iftype_data(9) and honestly? it's giving short-but-iconic. no cap, we're gonna get through it together 🫢


🌸 NAME 🌸

ieee80211_set_sband_iftype_data β€” set the sband iftype data array πŸ’–

like, that's the whole gig. it sets the sband iftype data array. main character energy fr fr πŸ‘‘


✨ SYNOPSIS ✨

ieee80211_set_sband_iftype_data (sband , iftd );

that's it, that's the call πŸŽ€ (spacing is exactly how the page has it, don't come for me 😭)


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sband β€” the sband to initialize. bestie, this is the one getting set up 🌸
  • iftd β€” the iftype data array. this is the data that goes in πŸ’…

lowkey important: this is part 1 of the page, so don't close the tab β€” more is on the way πŸ”₯

πŸ’… SEE ALSO πŸ’…

okay bestie, this is the part where the page lists literally everyone it knows. it's giving massive group chat energy πŸ’– every single one of these is a real cross-reference, so if you're lost, just tap one and keep vibing. no cap, this is a long list, but we're getting through it together.


  • the kernel file ./include/net/cfg80211.h β€” that's the actual home base where all this stuff lives
  • Introduction(9) and Device registration(9) β€” start here if you're brand new, they set the whole scene


next up, a whole other section β€” Actions and configuration(9) β€” and the entire squad that comes with it:


and now Scanning and BSS list handling(9) β€” another whole section, another whole friend group πŸ¦‹

  • struct cfg80211_ssid(9), struct cfg80211_scan_info(9), struct cfg80211_scan_6ghz_params(9)
  • struct cfg80211_scan_request(9), struct cfg80211_match_set(9)
  • struct cfg80211_sched_scan_plan(9), struct cfg80211_bss_select_adjust(9), struct cfg80211_sched_scan_request(9)
  • enum cfg80211_signal_type(9), struct cfg80211_inform_bss(9)
  • struct cfg80211_bss_ies(9), struct cfg80211_bss(9)
  • ieee80211_bss_get_elem(9), ieee80211_bss_get_ie(9)
  • struct cfg80211_auth_request(9), struct cfg80211_assoc_link(9), struct cfg80211_ml_reconf_req(9)
  • enum cfg80211_assoc_req_flags(9), struct cfg80211_assoc_request(9)
  • struct cfg80211_deauth_request(9), struct cfg80211_disassoc_request(9)
  • struct cfg80211_ibss_params(9), struct cfg80211_bss_selection(9)
  • struct cfg80211_connect_params(9), enum cfg80211_connect_params_changed(9)
  • enum wiphy_params_flags(9)
  • struct cfg80211_pmksa(9), struct cfg80211_pkt_pattern(9)
  • struct cfg80211_wowlan_tcp(9), struct cfg80211_wowlan(9)
  • struct cfg80211_coalesce_rules(9), struct cfg80211_coalesce(9)
  • struct cfg80211_wowlan_nd_match(9), struct cfg80211_wowlan_nd_info(9), struct cfg80211_wowlan_wakeup(9)
  • struct cfg80211_gtk_rekey_data(9), struct cfg80211_update_ft_ies_params(9), struct cfg80211_mgmt_tx_params(9)
  • struct cfg80211_dscp_exception(9), struct cfg80211_dscp_range(9), struct cfg80211_qos_map(9)

Neighbor Awareness Networking (NAN)(9) gets its own little moment ✨ and honestly? deserved. the NAN crew:

  • struct cfg80211_nan_band_config(9), struct cfg80211_nan_conf(9), struct cfg80211_nan_channel(9)
  • struct cfg80211_nan_local_sched(9), struct cfg80211_nan_peer_map(9), struct cfg80211_nan_peer_sched(9)
  • enum cfg80211_nan_conf_changes(9), struct cfg80211_nan_func_filter(9), struct cfg80211_nan_func(9)

and then we just keep rolling:

  • struct cfg80211_pmk_conf(9), struct cfg80211_external_auth_params(9)
  • struct cfg80211_ftm_responder_stats(9), struct cfg80211_pmsr_ftm_result(9), struct cfg80211_pmsr_result(9)
  • struct cfg80211_pmsr_ftm_request_peer(9), struct cfg80211_pmsr_request_peer(9), struct cfg80211_pmsr_request(9)
  • struct cfg80211_update_owe_info(9), struct mgmt_frame_regs(9)
  • struct cfg80211_ops(9) β€” the big one, the ops table, the whole personality
  • enum wiphy_flags(9), struct ieee80211_iface_limit(9), struct ieee80211_iface_combination(9)
  • enum wiphy_wowlan_support_flags(9), struct wiphy_wowlan_support(9), struct wiphy_coalesce_support(9)
  • enum wiphy_vendor_command_flags(9), enum wiphy_opmode_flag(9), struct sta_opmode_info(9), struct wiphy_vendor_command(9)
  • struct wiphy_iftype_ext_capab(9), cfg80211_get_iftype_ext_capa(9)
  • struct cfg80211_pmsr_capabilities(9), struct wiphy_iftype_akm_suites(9)
  • struct wiphy_radio_cfg(9), struct wiphy_radio_freq_range(9), struct wiphy_radio(9)
  • enum wiphy_nan_flags(9), struct wiphy_nan_capa(9)
  • struct wiphy(9) β€” the icon herself πŸ‘‘

wiphy lifecycle besties, in order because that's how we do:


okay, Utility functions(9) β€” the little helpers that make everything else possible 🫢


Data path helpers(9) β€” where packets actually get handled πŸ”₯ lowkey the most fun part:


Regulatory enforcement infrastructure(9) β€” the vibes police, fr fr 🌈


now the notify/report/scan-done gang β€” this is the longest stretch so hydrate first πŸ’€


RFkill integration(9) β€” the on/off switch besties:


Vendor commands(9) β€” for when the driver needs to do its own special thing ✨


Test mode(9) β€” yes, this exists, and no, we don't ask questions πŸ™ˆ


connect/roam/assoc notification squad, back at it:


and yes bestie, that's genuinely the whole SEE ALSO list β€” every last reference, not one skipped πŸ’– keep reading, there's still more coming and it only gets better from here β€”

...and the cross-reference hall of fame keeps going, bestie β€” this is the rest of the list, no skips, no cuts, every single one is here 🫢


okay that's the whole list, every single reference, zero crumbs left behind πŸ’– that was the entire manual page and honestly? ate. no cap.

this page lives in ./include/net (that's the source/version, mwah), and it's dated October 2026 β€” so like, future-dated and still serving looks πŸ‘‘ go be iconic with your cfg80211 lore bestie, ily, bye πŸŽ€βœ¨

πŸ“¦ where this page comes from