STRUCT IWL_FW_DBG_TRIGGER_MLME(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

struct iwl_fw_dbg_trigger_mlme β€” okay so this bad boy configures the trigger for mlme events, that's literally its whole job, no cap ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct iwl_fw_dbg_trigger_mlme {
    u8 stop_auth_denied;
    u8 stop_auth_timeout;
    u8 stop_rx_deauth;
    u8 stop_tx_deauth;
    u8 stop_assoc_denied;
    u8 stop_assoc_timeout;
    u8 stop_connection_loss;
    u8 reserved;
    u8 start_auth_denied;
    u8 start_auth_timeout;
    u8 start_rx_deauth;
    u8 start_tx_deauth;
    u8 start_assoc_denied;
    u8 start_assoc_timeout;
    u8 start_connection_loss;
    u8 reserved2;
 };

Sixteen u8s, bestie. Two of them are just vibe-holders (you'll see πŸ’€).


πŸ‘― Members πŸ‘‘

Okay so it's giving "two halves of the same coin" β€” there's a whole stop squad and a whole start squad, and honestly? Iconic structure. πŸŽ€

  • stop_auth_denied β€” the number of denied authentication to collect 🚫
  • stop_auth_timeout β€” the number of authentication timeout to collect ⏰
  • stop_rx_deauth β€” the number of Rx deauth before to collect πŸ“₯
  • stop_tx_deauth β€” the number of Tx deauth before to collect πŸ“€
  • stop_assoc_denied β€” the number of denied association to collect πŸ™…
  • stop_assoc_timeout β€” the number of association timeout to collect βŒ›
  • stop_connection_loss β€” the number of connection loss to collect πŸ’”
  • reserved β€” reserved πŸ«₯ (it's literally just reserved, don't come for me, that's the whole description)
  • start_auth_denied β€” the number of denied authentication to start recording πŸ”΄
  • start_auth_timeout β€” the number of authentication timeout to start recording πŸ”΄
  • start_rx_deauth β€” the number of Rx deauth to start recording πŸ”΄
  • start_tx_deauth β€” the number of Tx deauth to start recording πŸ”΄
  • start_assoc_denied β€” the number of denied association to start recording πŸ”΄
  • start_assoc_timeout β€” the number of association timeout to start recording πŸ”΄
  • start_connection_loss β€” the number of connection loss to start recording πŸ”΄
  • reserved2 β€” reserved πŸ«₯ (yes. again. reserved. we love a consistent queen)
Notice the pattern? The stop_* crew decides when to collect, and the start_* crew decides when to start recording. Same seven event types, two different jobs. Slay. ✨

🌈 SEE ALSO 🌈

Living in Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/file.h β€” and here's the whole friend group, fr fr:

  • enum iwl_ucode_tlv_flag(9)
  • enum iwl_ucode_tlv_api(9)
  • enum iwl_ucode_tlv_capa(9)
  • struct iwl_tlv_calib_ctrl(9)
  • struct iwl_fw_dbg_reg_op(9)
  • enum iwl_fw_dbg_monitor_mode(9)
  • struct iwl_fw_dbg_mem_seg_tlv(9)
  • struct iwl_fw_dbg_dest_tlv_v1(9)
  • enum iwl_fw_dbg_trigger_mode(9)
  • enum iwl_fw_dbg_trigger_flags(9)
  • enum iwl_fw_dbg_trigger_vif_type(9)
  • struct iwl_fw_dbg_trigger_tlv(9)
  • struct iwl_fw_dbg_trigger_missed_bcon(9)
  • struct iwl_fw_dbg_trigger_cmd(9)
  • struct iwl_fw_dbg_trigger_stats(9)
  • struct iwl_fw_dbg_trigger_low_rssi(9)
  • struct iwl_fw_dbg_trigger_txq_timer(9)
  • struct iwl_fw_dbg_trigger_time_event(9)
  • struct iwl_fw_dbg_trigger_ba(9)
  • struct iwl_fw_dbg_trigger_tdls(9)
  • struct iwl_fw_dbg_trigger_tx_status(9)
  • struct iwl_fw_dbg_conf_tlv(9)
  • struct iwl_fw_cmd_version(9)
  • struct iwl_fw_cmd_bios_table(9)

πŸ’… and that's the whole page, bestie, you ate πŸ’…

Source/version and date, for the record: ./drivers/net/wireless/intel/i... β€” October 2026 β€” struct iwl_f...trigger_mlme(9). Mwah. 🫢🌸

πŸ“¦ where this page comes from