STRUCT IWL_TOF_RANGE_RSP_NTFY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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 β€” 1 if no more FTM sessions are scheduled, 0 otherwise πŸ”₯ so basically "is this the finale or is there more?" β€” 1 means that's a wrap, 0 means 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_APS of 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