STRUCT IWL_PHY_CONTEXT_CMD_TAIL(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

okay so bestie, we're looking at struct iwl_phy_context_cmd_tail from the Kernel API Manual β€” it's the tail of iwl_phy_ctx_cmd for alignment with various channel structures. that's the whole vibe, she's a tail, she aligns things πŸ’…


✨ SYNOPSIS ✨

struct iwl_phy_context_cmd_tail {
    __le32 txchain_info;
    __le32 rxchain_info;
    __le32 acquisition_data;
    __le32 dsp_cfg_flags;
 };

literally just four little __le32 fields living their best life πŸŽ€


🫢 Members 🫢

  • txchain_info β€” ??? … yeah the docs genuinely just say ??? here 😭 no cap, that's all we get, she's mysterious and we respect it πŸ™ˆ
  • rxchain_info β€” also ??? πŸ’€ the mystery continues, iconic honestly
  • acquisition_data β€” ??? again bestie, three for three, we know nothing and that's the journey 🌈
  • dsp_cfg_flags β€” this one's the main character: set to 0 ⭐ the only member with lore
ngl, three of the four members are documented as ??? β€” that's not me being lazy, that is fr fr what the page says πŸ“

πŸ‘‘ SEE ALSO πŸ‘‘

  • the kernel file ./drivers/net/wireless/intel/iwlwifi/fw/api/phy-ctxt.h β€” go read it, that's where the real tea is 🧚
  • struct iwl_phy_context_cmd_v1(9)
  • struct iwl_phy_context_cmd(9)

and that's the page, bestie πŸ’– this lil gem comes from the kernel source tree at ./drivers/net/wireless/intel/i..., dated October 2026, and it's page struct iwl_...ext_cmd_tail(9) in the Kernel API Manual β€” go forth and align your channel structures, periodt πŸ”₯πŸ‘‘

πŸ“¦ where this page comes from