xcb_dri3_open(3)

📦
version 1.17.0 · 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ xcb_dri3_open ✨

okay bestie, we're in the XCB Requests part of the manual (section 3, obviously), and today's main character is xcb_dri3_open. yes it's giving "one function that opens a DRI3 thing" and yes we're gonna read the whole thing together. grab a boba. 💅

🌸 NAME 🌸

xcb_dri3_open —

and that's it. that's the whole name section. no description. the manpage literally trailed off into the void and left us with a dash. lowkey iconic of it to say nothing. 🫶

🦋 SYNOPSIS 🦋

first up, the include, because you can't summon the function without the header:

#include <xcb/dri3.h>

Request function 💖

xcb_dri3_open_cookie_t xcb_dri3_open(xcb_connection_t *conn,
       xcb_drawable_t drawable, uint32_t provider);

Reply datastructure 🎀

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

Reply function 🌈

xcb_dri3_open_reply_t *xcb_dri3_open_reply(xcb_connection_t *conn,
       xcb_dri3_open_cookie_t cookie, xcb_generic_error_t **e);

🌟 REQUEST ARGUMENTS 🌟

  • conn — the XCB connection to X11. your lil phone line to the server, fr fr. 📞
  • drawable — TODO: NOT YET DOCUMENTED. yeah. the docs said "not yet" and honestly that's so real of them. 🙈
  • provider — TODO: NOT YET DOCUMENTED. same energy. we don't know. it's a mystery. a uint32_t mystery. 💀

💜 REPLY FIELDS 💜

  • response_type — the type of this reply, which in this specific case is XCB_DRI3_OPEN. this field is also hanging out in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. it's the reply's little name tag at the function. 🏷️
  • sequence — the sequence number of the last request the X11 server processed. the receipts, basically. 🧾
  • length — how long the reply is, measured in words. and bestie, a word is 4 bytes here. not a text word. a word word. don't get it twisted. ✨
  • nfd — TODO: NOT YET DOCUMENTED. 😭
  • device_fd — TODO: NOT YET DOCUMENTED. the manpage really said "you'll find out" and dipped. 🙈

💅 DESCRIPTION 💅

literally nothing here. the section exists, it's named DESCRIPTION, and it contains zero words. a true minimalist queen. no cap. 👑

⭐ RETURN VALUE ⭐

so xcb_dri3_open hands you back an xcb_dri3_open_cookie_t. the catch? errors have to be handled when you call the reply function xcb_dri3_open_reply. that's the deal, that's the arrangement. 🍓

but wait — if you'd rather handle errors in the event loop instead of right at reply time, use xcb_dri3_open_unchecked. see xcb-requests(3) for the details, iykyk. 💖

🔥 ERRORS 🔥

this request does never generate any errors.

like, never ever. not one. so if you were bracing for an error, you can unclench bestie. 💅

🌸 SEE ALSO 🌸

nothing listed. the SEE ALSO section is a beautiful empty room with great lighting. we love her. 🦋

🎀 AUTHOR 🎀

Generated from dri3.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes they want your emails, they're very open to feedback, go be helpful. 💌)

that's the whole page babes, and it was brought to you by X Version 11 with libxcb 1.17.0, filed under xcb_dri3_open(3). go open some DRI3 things. you ate. periodt. 👑✨🫶

📦 where this page comes from