STRUCT IWL_TOF_RANGE_REQ_AP_ENTRY_V4(9)
π struct iwl_t_tof_range_req_ap_entry_v4(9) π
okay so bestie, welcome to the Kernel API Manual β¨ β this one lives in section 9 of the kernel docs, and it's literally the <struct iwl_tof_range_req_ap_entry_v4> situation. it's giving "AP configuration parameters" and honestly? she ate. π
πΈ NAME πΈ
struct iwl_tof_range_req_ap_entry_v4 β AP configuration parameters. that's it, that's the whole vibe. no cap. π
β¨ SYNOPSIS β¨
here's the whole glow-up, copy it exactly, she's iconic:
struct iwl_tof_range_req_ap_entry_v4 {
__le32 initiator_ap_flags;
u8 channel_num;
u8 format_bw;
u8 ctrl_ch_position;
u8 ftmr_max_retries;
u8 bssid[ETH_ALEN];
__le16 burst_period;
u8 samples_per_burst;
u8 num_of_bursts;
__le16 reserved;
u8 hltk[HLTK_11AZ_LEN];
u8 tk[TK_11AZ_LEN];
};
like... look at her. every field accounted for. not one missing. we love a complete struct. π«Ά
π¦ Members π¦
okay bestie, field-by-field tour, let's go π§:
initiator_ap_flagsβ seeenum iwl_initiator_ap_flags. that's where the actual flag lore lives, go read it iykyk.channel_numβ the AP Channel number. simple. slay.format_bwβenum iwl_location_format_bw. yes, the enum name is very close to other enum names, do not get it twisted π.ctrl_ch_positionβ the coding of the control channel position relative to the center frequency, seeiwl_mvm_get_ctrl_pos. (not me being obsessed with how specific that is π)ftmr_max_retriesβ max number of retries to send the FTMR in case of no reply from the AP. like, how many times do we knock before we accept nobody's home.bssidβ the AP's BSSID. main character identifier energy π.burst_periodβ recommended value to be sent to the AP. measurement periodicity in units of100ms. ignored ifnum_of_bursts_exp=0β yes, really, it just gets ignored, so don't come for her.samples_per_burstβ the number of FTMs pairs in single Burst (1-31). range check your girl bestie, fr fr.num_of_burstsβ recommended value to be sent to the AP.2sexponent of the number of measurement iterations (min2^0=1, max2^14). math is mathing π.reservedβ for alignment and future use. she's just holding space, literally. πhltkβ HLTK to be used for secured 11az measurement. π₯tkβ TK to be used for secured 11az measurement. yes there are two, and yes both matter. π
π₯ SEE ALSO π₯
bestie there are SO many friends in this clique, buckle up π β all of these live 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), 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), struct iwl_ftm_responder_stats(9).
like, that's the whole group chat. every single one. mwah π
and that's the page, bestie π β sourced from ./drivers/net/wireless/intel/i... (the path got a lil truncated in the header, don't @ me), dated October 2026, and it's the struct iwl_t..._ap_entry_v4(9) manual, same energy as that footer you saw. 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