STRUCT IWL_TOF_RANGE_RSP_NTFY_V6(9)
π struct iwl_tof_range_rsp_ntfy_v6(9)
okay so bestie, welcome to the Kernel API Manual β¨ this one's about struct iwl_tof_range_rsp_ntfy_v6 and it's literally the ranging response notification, no cap π
β¨ NAME β¨
struct iwl_tof_range_rsp_ntfy_v6 β the ranging response notification π like, the lil' message that comes back saying "here's what we found" π«Ά
πΈ SYNOPSIS πΈ
struct iwl_tof_range_rsp_ntfy_v6 {
u8 request_id;
u8 num_of_aps;
u8 last_report;
u8 reserved;
struct iwl_tof_range_rsp_ap_entry_ntfy_v4 ap[IWL_TOF_MAX_APS];
};
look at her. iconic struct layout. four lil' u8s and then an array of per-AP entries π§
π Members π
π« request_id
A Token ID of the corresponding Range request π₯ it's giving "which request is this a reply to" energy, iykyk
π« num_of_aps
Number of APs results π like, how many access points actually showed up with data
π« last_report
1 if no more FTM sessions are scheduled, 0 otherwise β so it's the "are we done here or nah" flag
π« reserved
reserved π she's just vibing there, not doing anything, main character energy of empty space
π« ap
per-AP data π the actual payload, one entry per AP
π¦ SEE ALSO π¦
Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h β go read it, it's the whole vibe π
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_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)
no gatekeeping here, bestie β every single one of these is a whole rabbit hole and honestly? obsessed π
and that's the page!! π this lil' beauty lives at ./drivers/net/wireless/intel/i..., dated October 2026, and it's struct iwl_t..._rsp_ntfy_v6(9) all day every day π
β¨ 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