ENUM IWL_LOCATION_FORMAT_BW(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum iwl_location_format_bw(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ this is the glow-up page for enum iwl_location_format_bw and honestly it's serving exactly what it says on the tin: format + bandwidth encoding πŸŽ€


✨ NAME ✨

enum iwl_location_format_bw β€” the format/BW encoding, no cap πŸ¦‹


🌸 SYNOPSIS 🌸

enum iwl_location_format_bw {
    IWL_LOCATION_FMT_BW_FORMAT ,
    IWL_LOCATION_FMT_BW_BANDWIDTH

};

like, that's the whole vibe. two constants, sitting there, being iconic πŸ‘‘


πŸŽ€ Constants πŸŽ€

  • IWL_LOCATION_FMT_BW_FORMAT β€” this one's an enum iwl_location_frame_format, iykyk πŸ’«
  • IWL_LOCATION_FMT_BW_BANDWIDTH β€” and this one's an enum iwl_location_bw, periodt πŸ’…

πŸ¦‹ SEE ALSO πŸ¦‹

so here's the whole friend group, and yes you do need to know all of them πŸ’–

  • Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h
  • enum iwl_location_subcmd_ids(9)
  • enum iwl_location_frame_format(9)
  • enum iwl_location_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)

lowkey that's a LOT of friends but every single one of them matters, don't skip a single one or the vibe check fails 😭

okay that's the page!! it came from ./drivers/net/wireless/intel/i..., dated October 2026, and it's literally titled enum iwl_location_format_bw(9) β€” slay, go read the kernel now πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from