STRUCT IWL_FWRT_DUMP_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct iwl_fwrt_dump_data(9) β€” NAME

okay so struct iwl_fwrt_dump_data is literally just dump data ✨ that's it, that's the vibe. (and yes bestie, this is the struct iwl_fwrt_dump_data(9) page from the Kernel API Manual, we're getting into it 🫢)


✨ SYNOPSIS ✨

here's the whole glow-up, copy it exactly, no cap:

struct iwl_fwrt_dump_data {
    union {
      struct {
        struct iwl_fw_ini_trigger_tlv *trig;
        struct iwl_rx_packet *fw_pkt;
      };
      struct {
        const struct iwl_fw_dump_desc *desc;
        bool monitor_only;
      };
    };
 };

πŸŽ€ Members πŸŽ€

  • {unnamed_union} β€” anonymous πŸ™ˆ (yes, it's literally unnamed, we don't know her name)
  • {unnamed_struct} β€” anonymous again, the mystery continues πŸ’€
  • trig β€” the trigger the worker was scheduled upon πŸ”₯
  • fw_pkt β€” the packet received from FW πŸ“¦
  • {unnamed_struct} β€” anonymous, third times the charm 🧚
  • desc β€” the dump descriptor 🏷️
  • monitor_only β€” only dump for monitor πŸ‘€

🌸 Description 🌸

okay so here's the tea bestie β˜• β€” you've got two whole structs living inside one union, and which one you're actually using is a whole decision. The way that decision works? It's based on iwl_trans_dbg_ini_valid ✨

  • if it's true β†’ the 'trig' part is the main character πŸ‘‘
  • if it's false β†’ it's the 'desc' part instead, periodt πŸ’…

that's it, that's the whole lore. iykyk 🌈


πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/net/wireless/intel/iwlwifi/fw/runtime.h
  • struct iwl_fwrt_wk_data(9)
  • struct iwl_txf_iter_data(9)
  • struct iwl_fw_runtime(9)

go read those next, bestie, they're lowkey iconic too πŸ’–


and that's a wrap on struct iwl_fwrt_dump_data(9) from the Kernel API Manual! πŸŽ€ this lil beauty comes from ./drivers/net/wireless/intel/i..., dated October 2026 ⭐ obsessed, fr fr. slay πŸ’œ

πŸ“¦ where this page comes from