vkms_config_create(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ vkms_config_create(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’… β€” today we're looking at vkms_config_create, and honestly? it's giving "small function, big main character energy" πŸŽ€


🌸 NAME 🌸

vkms_config_create β€” literally just Create a new VKMS configuration πŸ’– that's it, that's the whole job, and she does it slayfully ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct vkms_config * vkms_config_create (const char *dev_name );

no cap, that's the whole signature πŸ‘‘ one argument, one pointer back, we love a low-effort icon πŸ™ˆ


πŸ’œ ARGUMENTS πŸ’œ

  • dev_name β€” the Name of the device 🏷️ that's the whole description bestie, she's a simple girl, she just wants to know what to call this thing ✨

πŸ”₯ RETURN πŸ”₯

You get the new vkms_config back πŸŽ‰ β€” or, plot twist, an error 😭 (yes, it can just Not Work, vibe check failed πŸ’€).

⚠️ important bestie, do not forget this part: call vkms_config_destroy to free the returned configuration 🫢 like, she's yours now, you gotta take her out on the responsible-memory-management date, fr fr 🌸

🌈 SEE ALSO 🌈

okay this list is LONG and honestly iconic, buckle up 🎒 first the header file itself:

  • Kernel file ./drivers/gpu/drm/vkms/vkms_config.h β€” the mothership πŸ›Έ

then the structs πŸ‘‘:

  • struct vkms_config(9)
  • struct vkms_config_plane(9)
  • struct vkms_config_crtc(9)
  • struct vkms_config_encoder(9)
  • struct vkms_config_connector(9)

then the for-each iterators, the little loops that could πŸŒ€:

then the lifecycle besties πŸ’–:

then planes πŸ›©οΈ:

then CRTCs 🎬:

then encoders πŸ”Œ:

and finally connectors πŸŽ€:

like I said. A LOT. but every single one of them ate πŸ’…


and that's the page, bestie!! 🌟 this one came from ./drivers/gpu/drm/vkms, dated October 2026, and it's the vkms_config_create(9) manual page β€” go forth and create your configs responsibly, mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from