STRUCT HAM_MESSAGE_HEADER(9)

✨ struct ham_message_header(9) ✨

okay bestie, welcome to the Kernel API Manual page for struct ham_message_header — like, this is the main character header struct and we're gonna get you obsessed with it 💅

---

🌸 NAME 🌸

struct ham_message_header — the message header that lives over DMA, no cap 🦋

---

🎀 SYNOPSIS 🎀

here's the whole glow-up, literally character for character:

struct ham_message_header {
    u32 length;
    u16 fw_id;
    u16 host_id;
    u32 flags;
    u32 status;
    u32 reserved;
 };

(yeah there's a lil space before that closing brace, she's quirky like that 🫶)

---

💖 Members 💖

okay so let's meet the squad, each field gets her moment:

• length — the message length, and listen: it's payload only, she does not include the header, periodt ✨
• fw_id — the firmware client id. and if it's 0, that means Bus Message — iykyk 🚌
• host_id — the host client id. same vibe: 0 means Bus Message 🌈
• flags — the message flags, cute lil bitfield energy 🎀
• status — the operation status, so you know how things went 💫
• reserved — reserved. she's just sitting there, being mysterious, we respect her 🙈

---

🔥 SEE ALSO 🔥

go read these next, bestie, they're all linked up:

• Kernel file ./drivers/misc/issei/hw_msg.h struct
• ham_setup_shared_memory_req(9)
• struct ham_setup_shared_memory_res(9)
• struct control_buffer(9)
• struct ham_bus_message(9)
• struct ham_start_message_req(9)
• struct ham_start_message_res(9)
• struct ham_get_clients_req(9)
• struct ham_client_properties(9)
• struct ham_get_clients_res(9)

---

ngl that's the whole page — every field, every 0-means-Bus-Message caveat, every single cross-reference. nothing skipped, we ate and left no crumbs 💀🍓

and that's the vibe check, bestie 💜 this icon lives at ./drivers/misc/issei, dated October 2026, and she's officially struct ham_message_header(9) — slay, go read the source 👑✨