STRUCT ST_FDMA_HW_NODE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME β€” struct st_fdma_hw_node(9) πŸ’–

okay so struct st_fdma_hw_node is the Node structure used by fdma hw. That’s the whole assignment, bestie, and we’re gonna slay it.


✨ SYNOPSIS ✨

struct st_fdma_hw_node {
    u32 next;
    u32 control;
    u32 nbytes;
    u32 saddr;
    u32 daddr;
    union {
      struct st_fdma_generic_node generic;
    };
 };

πŸŽ€ Members πŸŽ€

  • next β€” pointer to next node. literally the β€œwho’s next” of the whole situation.
  • control β€” Transfer Control Parameters.
  • nbytes β€” Number of Bytes to read.
  • saddr β€” Source address.
  • daddr β€” Destination address.
  • {unnamed_union} β€” anonymous. yes, it’s giving mysterious unnamed-union main character energy.
    • generic β€” generic node for free running/paced transfert type 2. Others transfert type are possible, but not yet implemented.

🌸 Description 🌸

vibe check, and this one is serious: the NODE structures must be aligned to a 32 byte boundary. not optional, no cap.

⚠️ 32 byte boundary alignment is the rule. the NODE structures must be aligned to it, periodt.

πŸ¦‹ SEE ALSO πŸ¦‹

  • Kernel file ./drivers/dma/st_fdma.h β€” plus struct st_fdma_generic_node(9) and struct st_fdma_sw_node(9).

πŸ’… from the Kernel API Manual, source/version ./drivers/dma, dated October 2026, for struct st_fdma_hw_node(9) β€” byeee 🫢

πŸ“¦ where this page comes from