xcb_dri3_fd_from_fence(3)

✨ NAME ✨

xcb_dri3_fd_from_fence — bestie, the description slot is literally empty, the manpage left it blank, so we're just vibing with the name itself 💅

---

🦋 SYNOPSIS 🦋

#include <xcb/dri3.h>

🎀 Request function

xcb_dri3_fd_from_fence_cookie_t
       xcb_dri3_fd_from_fence(xcb_connection_t *conn,
       xcb_drawable_t drawable, uint32_t fence);

🎀 Reply datastructure

typedef struct xcb_dri3_fd_from_fence_reply_t {
    uint8_t  response_type;
    uint8_t  nfd;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad0[24];
} xcb_dri3_fd_from_fence_reply_t;

🎀 Reply function

xcb_dri3_fd_from_fence_reply_t
       *xcb_dri3_fd_from_fence_reply(xcb_connection_t *conn,
       xcb_dri3_fd_from_fence_cookie_t cookie, xcb_generic_error_t **e);

---

🌸 REQUEST ARGUMENTS 🌸

• conn — your XCB connection to X11, the whole pipeline to the server, no cap.
• drawable — okay so the manpage literally says "TODO: NOT YET DOCUMENTED." and honestly? same energy, it's giving mystery 🙈 we're not gonna pretend we know more than the docs do.
• fence — also "TODO: NOT YET DOCUMENTED." bestie, the docs said nothing and I'm not about to make stuff up ✨

---

💜 REPLY FIELDS 💜

• response_type — the type of this reply, and in this specific case it's XCB_DRI3_FD_FROM_FENCE. it also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other 👑
• sequence — the sequence number of the last request that got processed by the X11 server, iconic bookkeeping fr fr.
• length — how long the reply is, measured in words (and a word is 4 bytes, remember that 🧚).
• nfd — "TODO: NOT YET DOCUMENTED." yeah, the docs just didn't 🫶
• fence_fd — "TODO: NOT YET DOCUMENTED." also a mystery, we move 💀

---

🌈 DESCRIPTION 🌈

The DESCRIPTION section is empty in the original, bestie — not a single sentence, zero, nada. So there's nothing to tell you here except: this is where the description would be if anyone had written one. vibe check passed, content pending 😭

---

⭐ RETURN VALUE ⭐

You get back an xcb_dri3_fd_from_fence_cookie_t. Errors? Those have to be handled when you call the reply function xcb_dri3_fd_from_fence_reply. periodt.

But wait — if you'd rather handle your errors in the event loop instead, then you use xcb_dri3_fd_from_fence_unchecked. See xcb-requests(3) for all the details on that, iykyk.

---

🍓 ERRORS 🍓

This request does never generate any errors. not one, zero, a totally clean slate, we love that for us 💖

---

🦄 SEE ALSO 🦄

Empty, bestie. The SEE ALSO section has nothing in it — no references, no cross-links, just vibes ✨

---

💅 AUTHOR 💅

Generated from dri3.xml. Contact xcb@lists.freedesktop.org for corrections and improvements — that's literally the whole line, go off 👑

---

okay bestie that's the whole page, you ate it up 💖 this was X Version 11, libxcb 1.17.0, and yeah the date slot is just as mysterious as the TODOs up there — but you got this, go forth and slay 🎀🦋✨