STRUCT VKMS_CONFIG_CRTC(9)

📦 version 7.3.1, in nixpkgs unstable

💅 struct vkms_config_crtc(9) 💅

okay so bestie, welcome to the Kernel API Manual — this is the page for struct vkms_config_crtc(9) and honestly? she's a whole vibe. get comfy 🫶

✨ NAME ✨

struct vkms_config_crtc — and that's… literally it 😭 the original left the description blank after the dash. no cap, zero notes. she said "my name is enough" and honestly? main character energy. 💅

🌸 SYNOPSIS 🌸

here's the struct in all her glory — copy it exactly, don't you dare touch a character 🔥

struct vkms_config_crtc {
    struct list_head link;
    struct vkms_config *config;
    bool writeback;
    struct vkms_output *crtc;
 };

🎀 Members 🎀

so every field is doing her own little job and here's the tea on each one 🍓

  • link — the link to the other CRTCs in vkms_config. she's holding hands with her sisters, it's giving chain of command ✨
  • config — the vkms_config that this CRTC belongs to. like, which family she's from. iykyk 💖
  • writeback — if true, a writeback buffer can be attached to the CRTC. yes bestie, she can write back. iconic behaviour 👑
  • crtc — ok this one is important, listen up 🙈 Internal usage. This pointer should never be considered as valid. she can be used to store a temporary reference to a VKMS CRTC during device creation, but that's it. this pointer is not managed by the configuration and must be managed by other means. not me warning you twice, but fr fr — do not trust her 💀
⚠️ real talk: that crtc pointer is a "temporary reference only, not managed by the config" situation — the manpage is extremely clear it should never be considered valid. handle her yourself or suffer 😭

🦋 SEE ALSO 🦋

literally the whole friend group, no gatekeeping 💜

🌈 and that's the page bestie!! shoutout to ./drivers/gpu/drm/vkms for being the source, October 2026 for the date, and the Kernel API Manual for hosting the whole thing. slay, bye 💖✨🎀

📦 where this page comes from