vmw_kms_update_layout_ioctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– vmw_kms_update_layout_ioctl(9) β€” Kernel API Manual πŸ’–

okay bestie, welcome to the group chat for the DRM_VMW_UPDATE_LAYOUT ioctl handler. this is the function that handles that call, and yes it's a whole vibe ✨


✨ NAME ✨

vmw_kms_update_layout_ioctl β€” it's literally the handler for the DRM_VMW_UPDATE_LAYOUT ioctl πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

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

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the drm device this ioctl is running on πŸ–₯️
  • data β€” the data pointer for the ioctl, iykyk πŸ“¦
  • file_priv β€” the drm file for the ioctl call πŸ—‚οΈ

🌸 DESCRIPTION 🌸

so what it does is update the preferred topology of the display unit to match whatever the ioctl request asked for. that's the whole assignment, no cap.

the topology comes in as an array of drm_vmw_rect, like this iconic little lineup:

[0 0 640 480] [640 0 800 600] [0 480 640 480]

πŸ‘‘ NOTE πŸ‘‘

listen up because this part is important fr fr:

  • the x and y offset (upper left) in drm_vmw_rect cannot be less than 0 πŸ™…β€β™€οΈ
  • besides the device limit on topology, x + w and y + h (lower right) cannot be greater than INT_MAX 😭

so if the topology goes beyond those limits, it comes back with an error. no slay, just nope.


πŸ”₯ RETURN πŸ”₯

  • 0 on success β€” we love a win πŸ’–
  • negative errno on failure β€” it's giving error, unfortunately πŸ’€

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/gpu/drm/vmwgfx/vmwgfx_kms.c β€” go read it if you're feeling curious 🧚

and here's the whole bestie list of related functions, every single one:


and that's the page, bestie 🫢 this cutie came from ./drivers/gpu/drm/vmwgfx, dated October 2026 β€” periodt πŸ’œ

πŸ“¦ where this page comes from