STRUCT IWL_TOF_RANGE_RSP_NTFY_V7(9)
π struct iwl_t..._rsp_ntfy_v7(9) π
okay so bestie, welcome to the Kernel API Manual β¨ β yes we're reading kernel headers for fun now, this is who we are, main character energy fr fr π
πΈ NAME πΈ
struct iwl_tof_range_rsp_ntfy_v7 β it's the ranging response notification, aka the little message that comes back telling you how your FTM ranging sesh went π¦
β SYNOPSIS β
struct iwl_tof_range_rsp_ntfy_v7 {
u8 request_id;
u8 num_of_aps;
u8 last_report;
u8 reserved;
struct iwl_tof_range_rsp_ap_entry_ntfy_v5 ap[IWL_TOF_MAX_APS];
};
look at her π
four u8s and an array, immaculate, no notes.
π Members π
request_idβ the Token ID of the corresponding Range request π«Ά like a little receipt number so you know which request this answer belongs tonum_of_apsβ how many AP results you got, literally the count bestie π₯last_reportβ it's1if no more FTM sessions are scheduled, and0otherwise π so basically "are we done here or not"reservedβ reserved π (she's just sitting there, being reserved, iconic behaviour honestly)apβ per-AP data π the actual good stuff, one entry per AP, array ofstruct iwl_tof_range_rsp_ap_entry_ntfy_v5sizedIWL_TOF_MAX_APS
π¦ SEE ALSO π¦
no cap, this list is LONG, but we respect her for it π everything below lives in the 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)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_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)
yeah that's a lot of siblings π but we love a big family π
β¨ cute sign-off β¨
this lil page is from ./drivers/net/wireless/intel/i... and it's dated October 2026 β so mark your calendars bestie π stay hydrated, read your headers, and slay the day π
π
π¦ 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