drm_mode_getresources(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_mode_getresources 💅

okay so bestie, welcome to the Kernel API Manual entry for drm_mode_getresources — yes that's the whole name, it's giving very long function name energy but we move 🎀

✨ NAME ✨

drm_mode_getresources — get graphics configuration 🖥️✨

Like, the whole vibe of this function is "hey kernel, tell me how you're set up," and honestly? iconic.

🦋 SYNOPSIS 🦋

int drm_mode_getresources (struct drm_device *dev , void *data , struct drm_file *file_priv );

that's it. that's the signature. no cap, copy it exactly, don't get cute with it 💀

🌸 ARGUMENTS 🌸

  • dev — the drm device for the ioctl 🫶 literally the thing you're asking about
  • data — data pointer for the ioctl 📦 this is where all the info goes
  • file_priv — drm file for the ioctl call 🗂️ the file handle doing the asking

💖 DESCRIPTION 💖

okay so here's the tea ☕ — this function constructs a whole set of configuration description structures and hands them right back to the user. what's in the set? we're talking:

  • CRTC configuration 🎛️
  • connector configuration 🔌
  • framebuffer configuration 🖼️

all of it. packaged up. returned. slay 💅

and how does this even happen? called by the user via ioctl — that's the whole entry point, iykyk ✨

⭐ RETURN ⭐

  • Zero on success 👑 (we love a clean win)
  • negative errno on failure 😭 (not the vibe, but at least it tells you what went wrong)

🔥 SEE ALSO 🔥

like, go read those too, they're the friend group this function rolls with 🫶

ngl bestie, this one's a shortie — no deprecated warnings, no undefined behaviour lurking, just a clean little ioctl that tells you how your graphics stack is doing 💜

and that's the page! brought to you from ./drivers/gpu/drm, dated October 2026 — mwah, catch you on the next man page 💋🎀💖

📦 where this page comes from