STRUCT IWL_TOF_MCSI_NOTIF(9)
π NAME π
struct iwl_tof_mcsi_notif β bestie, this struct is literally used for debug. That's the whole vibe. It's from the Kernel API Manual, section 9, and she's here to hold debug info, no cap.
β¨ SYNOPSIS β¨
struct iwl_tof_mcsi_notif {
u8 token;
u8 role;
__le16 reserved;
u8 initiator_bssid[ETH_ALEN];
u8 responder_bssid[ETH_ALEN];
u8 mcsi_buffer[IWL_MVM_TOF_MCSI_BUF_SIZE * 4];
};
π Members π
Okay so every field gets its moment, periodt:
tokenβ the token ID for the current session. She's the little name tag for this session, iykyk.roleβ the original manpage says absolutely nothing here. She's giving mysterious main character energy. No description, just vibes. πreservedβ reserved. That's it. That's the whole field. Do not touch, bestie. πinitiator_bssidβ the initiator machine. The one who starts the whole thing.responder_bssidβ the responder machine. The one who answers back.mcsi_bufferβ debug data. It's the buffer where the debug data lives, highkey iconic.
Lowkey important:mcsi_bufferis sizedIWL_MVM_TOF_MCSI_BUF_SIZE * 4β keep that exact, don't go editing it like it's a Google Doc. πΈ
π SEE ALSO π
The kernel file is ./drivers/net/wireless/intel/iwlwifi/fw/api/location.h, and honestly she has a whole friend group. Here's everyone, in order:
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_range_rsp_ntfy(9)struct iwl_tof_range_abort_cmd(9)struct iwl_ftm_responder_stats(9)
β¨ cute little sign-off β¨
This page came from ./drivers/net/wireless/intel/i... and it's dated October 2026. The whole thing is filed under struct iwl_tof_mcsi_notif(9) β literally the same name at the top and bottom, like a little symmetrical slay. π«Άπ
π¦ 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