STRUCT MEI_CLIENT_PROPERTIES(9)

💅 struct mei_client_properties(9) — like, the mei client properties bestie

okay so this is a page straight out of the Kernel API Manual (yes that one, the 9 section, we love a kernel section) and it's all about struct mei_client_properties — the lil struct that tells you everything about a mei client. no cap, it's lowkey iconic. let's get into it ✨

---

🌸 NAME 🌸

struct mei_client_properties — mei client properties. that's it, that's the vibe. 💖

---

🎀 SYNOPSIS 🎀

here's the whole struct, bestie, copied exactly, don't come for me:

struct mei_client_properties {
    uuid_le protocol_name;
    u8 protocol_version;
    u8 max_number_of_connections;
    u8 fixed_address;
    u8 single_recv_buf:1;
    u8 vt_supported:1;
    u8 reserved:6;
    u32 max_msg_length;
 };

---

👑 Members 👑

okay so each field ate and left no crumbs, here's the tea on every single one:

• protocol_name — the guid of the client 🫶 literally its little name tag.
• protocol_version — the client protocol version. which era of the client are we in, iykyk.
• max_number_of_connections — number of possible connections. the friend-group cap, fr fr.
• fixed_address — fixed me address (and it's 0 if the client is dynamic, so watch out for that 💀).
• single_recv_buf — 1 if all connections share a single receive buffer. sharing is caring, bestie 💖
• vt_supported — the client support vtag. yes, exactly as written, no notes.
• reserved — reserved. it's giving "no thoughts, head empty" — it's just reserved, leave it alone 🙈
• max_msg_length — MTU of the client. the message-size ceiling, periodt.

---

🦋 SEE ALSO 🦋

so many cross-refs, we're basically at a family reunion. all in the Kernel file ./drivers/misc/mei/hw.h:

enum mei_hbm_status(9), enum mei_ext_hdr_type(9), struct mei_ext_hdr(9), struct mei_ext_meta_hdr(9), struct mei_ext_hdr_vtag(9), mei_ext_begin(9), mei_ext_last(9), struct mei_ext_hdr_gsc_h2f(9), struct mei_ext_hdr_gsc_f2h(9), mei_ext_next(9), mei_ext_hdr_len(9), struct mei_msg_hdr(9), struct mei_hbm_cl_cmd(9), enum hbm_host_enum_flags(9), struct hbm_host_enum_request(9), struct hbm_add_client_request(9), struct hbm_add_client_response(9), struct hbm_power_gate(9), struct hbm_client_connect_request(9), struct hbm_client_connect_response(9), struct hbm_notification_request(9), struct hbm_notification_response(9), struct hbm_notification(9), struct hbm_dma_mem_dscr(9), struct hbm_dma_setup_request(9), struct hbm_dma_setup_response(9), struct hbm_dma_ring_ctrl(9), struct hbm_capability_request(9), struct hbm_capability_response(9), struct hbm_client_dma_map_request(9), struct hbm_client_dma_unmap_request(9), struct hbm_client_dma_response(9)

like, go read them, bestie, they're all right there 💅

---

quick vibe check: everything above is straight from the kernel docs, nothing invented, promise. 🫶

and that's a wrap, babes 💖 this page came from ./drivers/misc/mei and is dated October 2026 — so it's lowkey from the future, main character energy fr fr. go forth and struct responsibly 🌈⭐