STRUCT IWL_TOF_RANGE_RSP_NTFY(9)
π struct iwl_tof_range_rsp_ntfy(9) β the Kernel API Manual glow-up π
okay bestie, sit down, because we're looking at struct iwl_tof_range_rsp_ntfy β the ranging response notification π¦. this is a Kernel API Manual page, and honestly? it's giving quiet luxury. tiny struct, big job: it's the little note that comes back saying "here's how the ranging went" β¨
basically: you send out a range request, and this is the notification that comes home. main character energy fr fr π
π§ SYNOPSIS
struct iwl_tof_range_rsp_ntfy {
u8 request_id;
u8 num_of_aps;
u8 last_report;
u8 reserved;
struct iwl_tof_range_rsp_ap_entry_ntfy ap[IWL_TOF_MAX_APS];
};
look at her. five fields, zero drama. IWL_TOF_MAX_APS is the cap on how many APs can fit in the ap array, iykyk π
πΈ Members
request_idβ the Token ID of the corresponding Range request π like, which request is this a reply to? this is the reply-to header, bestie.num_of_apsβ the number of APs results π«Ά how many answers actually showed up.last_reportβ1if no more FTM sessions are scheduled,0otherwise π₯ so basically "is this the finale or is there more?" β1means that's a wrap,0means keep watching.reservedβ reserved π«₯ the padding friend. nothing to see here, she's just holding space (literally).apβ per-AP data π the actual per-AP deets, one entry per AP,IWL_TOF_MAX_APSof them max.
ngl, reserved is the most relatable field on this whole page β just vibing, being reserved, contributing nothing but structure π
π SEE ALSO
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h, and then, bestie, the whole friend group π:
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_mcsi_notif(9)struct iwl_tof_range_abort_cmd(9)struct iwl_ftm_responder_stats(9)
like, the entire location.h extended universe is in here π no cap, every sibling and cousin got a mention. ate and left no crumbs π
and that's the whole page, bestie π«Ά huge thank you to the source ./drivers/net/wireless/intel/i... and uhh, October 2026 β yes, the date really says that, she's from the future apparently π¦β¨ mwah, go read struct iwl_tof_range_rsp_ap_entry_ntfy(9) next, it's the sequel π
π¦ 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