xcb_dri3_pixmap_from_buffer(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_pixmap_from_buffer(3) 💖

okay bestie, welcome to the XCB Requests corner of the manual, where we're gonna talk about xcb_dri3_pixmap_from_buffer — and no, I'm not gonna pretend this one is well-documented, because it is not, and we're gonna be honest about that together 🫶

✨ NAME ✨

xcb_dri3_pixmap_from_buffer — literally just the name, the manpage gave us nothing else here, not even a one-liner. iconic of it honestly 💀

🌸 SYNOPSIS 🌸

First, you gotta pull in the header, no cap:

#include <xcb/dri3.h>

🎀 Request function 🎀

xcb_void_cookie_t xcb_dri3_pixmap_from_buffer(xcb_connection_t *conn,
       xcb_pixmap_t pixmap, xcb_drawable_t drawable, uint32_t size,
       uint16_t width, uint16_t height, uint16_t stride, uint8_t depth,
       uint8_t bpp, int32_t pixmap_fd);

that's the whole vibe. ten arguments. she's high maintenance and we love her 💅

🦋 REQUEST ARGUMENTS 🦋

okay so here's the thing — the upstream docs for every single one of these says TODO: NOT YET DOCUMENTED. and I am not about to make stuff up and lie to you, bestie. so here's the honest list, every arg, exactly as undocumented as the source says:

  • conn — the XCB connection to X11. that part is documented, slay ✨
  • pixmap — TODO: NOT YET DOCUMENTED. 😭
  • drawable — TODO: NOT YET DOCUMENTED. 😭
  • size — TODO: NOT YET DOCUMENTED. 😭
  • width — TODO: NOT YET DOCUMENTED. 😭
  • height — TODO: NOT YET DOCUMENTED. 😭
  • stride — TODO: NOT YET DOCUMENTED. 😭
  • depth — TODO: NOT YET DOCUMENTED. 😭
  • bpp — TODO: NOT YET DOCUMENTED. 😭
  • pixmap_fd — TODO: NOT YET DOCUMENTED. 😭
not me reading a manpage that's 90% "TODO: NOT YET DOCUMENTED." — if you need the real tea on what these do, go read the protocol spec, because this page is giving placeholder energy and nothing else 🙈

💜 DESCRIPTION 💜

…yeah. there's nothing here. the DESCRIPTION section is empty. the void. the silence. main character energy but make it absent 💀

⭐ RETURN VALUE ⭐

She returns an xcb_void_cookie_t, bestie. and listen — errors, if there are any, have to be handled in the event loop. that's the rule, periodt.

But if you'd rather handle errors directly with xcb_request_check instead of doing the whole event-loop dance, then you want xcb_dri3_pixmap_from_buffer_checked — she's the sibling function for exactly that. more details live in xcb-requests(3), go read it, iykyk 📖

💀 ERRORS 💀

good news for once: this request does never generate any errors. zero. none. clean run, no drama, we love a low-maintenance king 🔥

🌈 SEE ALSO 🌈

…it's empty. nothing to see. nothing to also. the section is there and it is ✨vacant✨.

👑 AUTHOR 👑

This page was generated from dri3.xml. If you've got corrections or improvements, hit up the good people at xcb@lists.freedesktop.org — they're the ones who want to hear it 💌

okay that's the whole page, bestie!! 🎀 thanks for reading my little deep-dive into the most mysterious function in dri3 — and a cute little sign-off for the credits: this is X Version 11, from libxcb 1.17.0, and yes the manpage header/footer has been giving you xcb_dri3_pixmap_from_buffer(3) this whole time like the icon it is 💅✨ mwah, go write some X11 code 🦋

📦 where this page comes from