xcb_xf86dri_q...ering_capable(3)

💖 xcb_xf86dri_query_direct_rendering_capable 💖

okay bestie, welcome to the XCB Requests corner of the manual, and today's main character is xcb_xf86dri_query_direct_rendering_capable from the xf86dri fam. it's giving "asking the X server if direct rendering is even possible on this screen", and honestly? we love a low-stakes little query. ✨

---

🌸 NAME 🌸

xcb_xf86dri_query_direct_rendering_capable —

ngl the original page just... stops there. no description. the NAME section is out here with main character energy and zero lore. 💀 we move.

---

🎀 SYNOPSIS 🎀

#include <xcb/xf86dri.h>

✨ Request function ✨

xcb_xf86dri_query_direct_rendering_capable_cookie_t
       xcb_xf86dri_query_direct_rendering_capable(xcb_connection_t *conn,
       uint32_t screen);

🦋 Reply datastructure 🦋

typedef struct xcb_xf86dri_query_direct_rendering_capable_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  is_capable;
} xcb_xf86dri_query_direct_rendering_capable_reply_t;

💅 Reply function 💅

xcb_xf86dri_query_direct_rendering_capable_reply_t
       *xcb_xf86dri_query_direct_rendering_capable_reply(xcb_connection_t *conn,
       xcb_xf86dri_query_direct_rendering_capable_cookie_t cookie,
       xcb_generic_error_t **e);

---

🌈 REQUEST ARGUMENTS 🌈

• conn — the XCB connection to X11, aka your little hotline to the server. she's the whole vibe, everything goes through her. 🫶
• screen — TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll get to it" and then did not get to it. iconic of them tbh. 😭

---

⭐ REPLY FIELDS ⭐

• response_type — the type of this reply, which in this particular case is XCB_XF86DRI_QUERY_DIRECT_RENDERING_CAPABLE. this field also lives inside the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. it's the name tag at the party. 🏷️
• sequence — the sequence number of the last request the X11 server processed. think of it as the receipt number, no cap. 🧾
• length — the length of the reply, measured in words. and a word is 4 bytes, so do your math, girlie. 🔢
• is_capable — TODO: NOT YET DOCUMENTED. again!! the void!! we know nothing!! 🙈

---

💜 DESCRIPTION 💜

literally nothing here. the section exists. it is empty. it is a vibe. the original authors truly said "no thoughts, head empty" and moved on. we respect the honesty. 🕳️✨

---

👑 RETURN VALUE 👑

she returns an xcb_xf86dri_query_direct_rendering_capable_cookie_t, bestie. that's the deal.

and here's the tea: errors have to be handled when you call the reply function xcb_xf86dri_query_direct_rendering_capable_reply.

but if you'd rather handle errors inside the event loop instead, then use xcb_xf86dri_query_direct_rendering_capable_unchecked. the details live over in xcb-requests(3), go read that one. 📚

---

🔥 ERRORS 🔥

okay this is the good part: this request does never generate any errors. not one. zero. a clean queen. slay. 💅✨

---

🧚 SEE ALSO 🧚

bestie... the original listed nothing here. no cross-references. no friends. just an empty section standing alone in the rain. she's mysterious. she's unbothered. 🌧️

---

💖 AUTHOR 💖

Generated from xf86dri.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (they're literally asking to be corrected, so if you find something, tell them, fr fr 🫶)

---

and that's the whole page, bestie!! 🎀 this lil manual page came to you from X Version 11, libxcb 1.17.0, and yes she still goes by the very dramatic name xcb_xf86dri_q...ering_capable(3). mwah, take care of her. 💋🌸🦋