ENUM IWL_LOCATION_BW(9)
π enum iwl_location_bw(9)
okay so bestie, welcome to the Kernel API Manual β¨ β yes that manual, the one with the actual lore. Today's episode: enum iwl_location_bw, aka the vibe check for how much spectrum you're claiming. no cap, it's giving very "pick your lane" energy π¦
πΈ NAME πΈ
enum iwl_location_bw β location bandwidth selection π (literally just picking your bandwidth, iykyk)
β¨ SYNOPSIS β¨
enum iwl_location_bw {
IWL_LOCATION_BW_20MHZ ,
IWL_LOCATION_BW_40MHZ ,
IWL_LOCATION_BW_80MHZ ,
IWL_LOCATION_BW_160MHZ ,
IWL_LOCATION_BW_320MHZ
};
like, that's the whole squad right there π five constants, no drama, all in order.
π Constants π
IWL_LOCATION_BW_20MHZβ 20 MHz π (the cozy starter size, ngl)IWL_LOCATION_BW_40MHZβ 40 MHz πΈ (doubled up, main character energy)IWL_LOCATION_BW_80MHZβ 80 MHz π¦ (now we're actually cooking)IWL_LOCATION_BW_160MHZβ 160 MHz π₯ (big, bold, iconic)IWL_LOCATION_BW_320MHZβ 320 MHz π (the final boss of bandwidth, ate and left no crumbs)
π SEE ALSO π
so like, if you wanna go down the rabbit hole (and you do), these are all the siblings β go say hi π«Ά
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h, then:
enum iwl_location_subcmd_ids(9)enum iwl_location_frame_format(9)enum iwl_location_format_bw(9)struct iwl_tof_config_cmd(9)enum iwl_tof_bandwidth(9)enum iwl_tof_responder_cmd_valid_field(9)enum iwl_tof_responder_cfg_flags(9)struct iwl_tof_responder_config_cmd_v6(9)struct iwl_tof_responder_config_cmd_v7(9)struct iwl_tof_responder_config_cmd_v8(9)struct iwl_tof_responder_config_cmd_v9(9)struct iwl_tof_responder_config_cmd(9)struct iwl_tof_responder_dyn_config_cmd_v2(9)enum iwl_responder_dyn_cfg_valid_flags(9)struct iwl_tof_responder_dyn_config_cmd(9)struct iwl_tof_range_req_ext_cmd(9)enum iwl_tof_location_query(9)enum iwl_initiator_ap_flags(9)struct iwl_tof_range_req_ap_entry_v3(9)struct iwl_tof_range_req_ap_entry_v4(9)enum iwl_location_cipher(9)struct iwl_tof_range_req_ap_entry_v6(9)struct iwl_tof_range_req_ap_entry_v7(9)struct iwl_tof_range_req_ap_entry_v8(9)struct iwl_tof_range_req_ap_entry_v9(9)struct iwl_tof_range_req_ap_entry(9)enum iwl_tof_response_mode(9)enum iwl_tof_initiator_flags(9)struct iwl_tof_range_req_cmd_v5(9)struct iwl_tof_range_req_cmd_v7(9)struct iwl_tof_range_req_cmd_v8(9)struct iwl_tof_range_req_cmd_v9(9)struct iwl_tof_range_req_cmd_v11(9)struct iwl_tof_range_req_cmd_v12(9)struct iwl_tof_range_req_cmd_v13(9)struct iwl_tof_range_req_cmd(9)enum iwl_tof_entry_status(9)struct iwl_tof_range_rsp_ap_entry_ntfy_v3(9)struct iwl_tof_range_rsp_ap_entry_ntfy_v4(9)struct iwl_tof_range_rsp_ap_entry_ntfy_v5(9)struct iwl_tof_range_rsp_ap_entry_ntfy_v7(9)struct iwl_tof_range_rsp_ap_entry_ntfy(9)enum iwl_tof_response_status(9)struct iwl_tof_range_rsp_ntfy_v5(9)struct iwl_tof_range_rsp_ntfy_v6(9)struct iwl_tof_range_rsp_ntfy_v7(9)struct iwl_tof_range_rsp_ntfy_v9(9)struct iwl_tof_range_rsp_ntfy(9)struct iwl_tof_mcsi_notif(9)struct iwl_tof_range_abort_cmd(9)struct iwl_ftm_responder_stats(9)
bestie heads up: every one of those is straight from the source file, so don't come for me if a version number got you feeling some type of way π
and that's the whole page, no notes π sign-off time: this little beauty came out of ./drivers/net/wireless/intel/i... and it's stamped October 2026 β so go forth, pick your MHz, and slay ππ§ββοΈ
π¦ 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