vkms_crtc_init(9)
β¨ vkms_crtc_init(9) β¨
okay so this is a page from the Kernel API Manual, bestie, and it's literally all about vkms_crtc_init β the glow-up moment where a CRTC gets born into the VKMS world π
no cap, it's a constructor and it's iconic for it.
π NAME π
vkms_crtc_init β Initialize a CRTC for VKMS
like⦠that's the whole vibe. it makes a CRTC. for VKMS. slay.
π¦ SYNOPSIS π¦
struct vkms_output * vkms_crtc_init (struct drm_device *dev , struct
drm_plane *primary , struct drm_plane *cursor );
so you call it, you hand it three things, and it gives you back a struct vkms_output * π«Ά that's the whole deal, fr fr.
πΈ ARGUMENTS πΈ
okay bestie let's go through what you're passing in, one by one, no skipping π
devβ the DRM device that's associated with the VKMS buffer. it's giving "who do you belong to" energy and honestly? valid.primaryβ the primary plane you're attaching to the CRTC. main character plane, obviously πcursorβ the plane you're attaching to the CRTC. yes queen, the cursor gets to come too π±οΈβ¨
lowkey important:primaryis the primary plane,cursoris a plane β the wording is different in the original and I'm not about to lie to you about it π
π SEE ALSO π
the group chat of related things π¬ all of these live in the kernel file ./drivers/gpu/drm/vkms/vkms_drv.h, and here's the full squad β not one of them is getting left on read:
struct vkms_frame_info(9)struct pixel_argb_u16(9)pixel_write_t(9)enum pixel_read_direction(9)pixel_read_line_t(9)struct conversion_matrix(9)struct vkms_plane_state(9)struct vkms_crtc_state(9)struct vkms_output(9)struct vkms_device(9)vkms_create(9)vkms_destroy(9)vkms_output_init(9)vkms_plane_init(9)
and that's the whole page, bestie π this lil' beauty comes to you from ./drivers/gpu/drm/vkms, dated October 2026 β so yeah, future vibes only π§ββοΈβ¨ mwah, go init some CRTCs, ily π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms