DRM_CAP_VBLANK_HIGH_CRTC(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… DRM_CAP_VBLANK_HIGH_CRTC(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this one's a tiny little corner of the DRM header files and it's honestly iconic in how small it is. Let's go 🫢


✨ NAME ✨

DRM_CAP_VBLANK_HIGH_CRTC β€” and that's literally it, no tagline, no description, the manpage just puts the name there and dips πŸ’€ (the original line is DRM_CAP_VBLANK_HIGH_CRTC - with nothing after the dash, and we're keeping it that way, no cap).


πŸ¦‹ SYNOPSIS πŸ¦‹

DRM_CAP_VBLANK_HIGH_CRTC

that's the whole synopsis. one line. main character energy, honestly πŸ‘‘


🌸 DESCRIPTION 🌸

okay so here's the tea:

  • If it's set to 1, the kernel supports specifying a CRTC index in the high bits of drm_wait_vblank_request.type. The docs write that CRTC index reference using the literal ref markup :ref:`CRTC index<crtc_index>` β€” yep, that exact string, character for character, iykyk πŸ”₯

and the second thing you need to know:

  • Starting kernel version 2.6.39, this capability is always set to 1. always. it's not a maybe, it's not a vibe check, it's just 1 forever πŸ’…
so like β€” if you're on anything even remotely modern, this bit is gonna be 1 when you read it. the kernel already decided. periodt. ✨

πŸŽ€ SEE ALSO πŸŽ€

all the neighbors, bestie, and there are so many of them β€” the whole DRM squad pulled up 😭


and that's the whole page, bestie β€” tiny page, huge friend group 🌈

signing off with the source/version vibes: ./tools/perf/trace/beauty/incl... and the date, October 2026 β€” luv u, go read about vblanks πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from