STRUCT IWL_FTM_RESPONDER_STATS(9)
πΈ struct iwl_ftm_responder_stats(9) β the Kernel API Manual moment π
okay so bestie, welcome to the Kernel API Manual page for struct iwl_ftm_responder_stats β that's the FTM responder statistics struct, and yeah the manpage title truncates it as struct iwl_f...ponder_stats(9) but we know what it is π
β¨ NAME β¨
struct iwl_ftm_responder_stats β FTM responder statistics, literally the receipts for your FTM responder π§Ύβ¨
π SYNOPSIS π
okay here's the whole struct, verbatim, do not touch, do not edit, copy it exactly:
struct iwl_ftm_responder_stats {
u8 addr[ETH_ALEN];
u8 success_ftm;
u8 ftm_per_burst;
__le32 flags;
__le32 duration;
__le32 allocated_duration;
u8 bw;
u8 rate;
__le16 reserved;
};
π¦ Members π¦
okay so let's go field by field, main character energy for each one:
addrβ the initiator address, bestie. like who started this whole thing πsuccess_ftmβ how many FTM frames actually succeeded, the good vibes count β¨ftm_per_burstβ the number of FTM frames that were received πflagsβ this one's anenum ftm_responder_stats_flags, iykyk πΈdurationβ the actual duration of the FTM, like real real π«Άallocated_durationβ the time that was allocated for this FTM session, so the plan vs. the reality πbwβ the FTM request bandwidth πrateβ the FTM request rate βreservedβ reserved for alingment and future use, like a little seat saved for later π
π SEE ALSO π
okay this list is LONG and I'm obsessed, but every single one of these is here, no skips, no cap:
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h and friends:
enum iwl_location_subcmd_ids(9)enum iwl_location_frame_format(9)enum iwl_location_bw(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)
π real talk: that's 51 whole entries and I typed every one, so you will read them. it's giving dedication.
and that's the page, bestie π«Ά this one lived at ./drivers/net/wireless/intel/i..., dated October 2026, and went out as struct iwl_f...ponder_stats(9) β slay, periodt π
β¨
π¦ 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