tb_xdomain_request(9)

📦 version 7.3.1, in nixpkgs unstable

✨ tb_xdomain_request(9) ✨

okay bestie, so this is a page straight out of the Kernel API Manual and it's literally about tb_xdomain_request — sending a XDomain request 💅 no cap, that's the whole vibe.

🎀 NAME 🎀

tb_xdomain_request — Send a XDomain request. That's it, that's the function 🫶

🌸 SYNOPSIS 🌸

int tb_xdomain_request (struct tb_xdomain *xd , const void *request ,
size_t request_size , enum tb_cfg_pkg_type request_type , void *response
, size_t response_size , enum tb_cfg_pkg_type response_type , unsigned
int timeout_msec );

look at all those args, she's got range 💀

🦋 ARGUMENTS 🦋

  • xd — the XDomain you're sending the request to 👑
  • request — the actual request you're sending out into the world ✨
  • request_size — how big the request is, in bytes 📏
  • request_type — the PDF type of the request (yes, PDF type, that's the term, don't come for me) 🍓
  • response — the response gets copied in here, it's the designated landing spot 💖
  • response_size — the size you're expecting the response to be, in bytes 🌸
  • response_type — the expected PDF type of the response 👀
  • timeout_msec — how long to wait for the response, in milliseconds ⏳

💜 DESCRIPTION 💜

so this function is your go-to for sending XDomain control channel messages over to the other domain 🌈 main character energy fr.

and here's the thing — she waits. The function just sits there, waiting until either the response shows up or the timeout triggers. Whichever comes first 😭 it's giving patient queen.

⭐ RETURN ⭐

0 on success, and a negative errno otherwise 💀 (iykyk, classic kernel behaviour)

👑 SEE ALSO 👑

hit up the Kernel file ./drivers/thunderbolt/xdomain.c and also literally all of these besties:

ngl that's a LOT of cross-references but we stay reading 📚💅

and that's the whole page bestie, love that for you 🧚💜

signed off with love from ./drivers/thunderbolt ✨ dated October 2026 🎀 slay, go send some XDomain requests 🦋

📦 where this page comes from