vmw_sou_plan...date_surface(9)
π» vmw_sou_plane_update_surface β a little kernel-y moment π
okay so bestie, buckle up, because this one lives in the vmw_sou_plan...date_surface(9) manual (yes that's the truncated header name fr, it's giving "my name got cut off in the terminal") π It's part of the Linux Kernel API Manual and it is literally about updating the display unit for a surface backed framebuffer. slay.
β¨ NAME β¨
vmw_sou_plane_update_surface β update the display unit for a surface-backed fb π
like⦠it's the function that goes "hey display unit, new surface just dropped" and honestly? iconic.
πΈ SYNOPSIS πΈ
int vmw_sou_plane_update_surface (struct vmw_private *dev_priv , struct
drm_plane *plane , struct drm_plane_state *old_state , struct
vmw_framebuffer *vfb , struct vmw_fence_obj **out_fence );
it returns an int, bestie. remember that. π«Ά
π¦ ARGUMENTS π¦
dev_privβ the device private. it's the private β¨deviceβ¨ data, the main character of the whole driver ngl.planeβ the plane state. yes, plane like the display plane, not like an airplane πold_stateβ the old plane state. the before-pic, if you will. πvfbβ the framebuffer which is blitted to the display unit. this is the actual visual content being pushed out π«out_fenceβ if it's non-NULL, this will return a ref-counted pointer tovmw_fence_obj. and listen, the returned fence pointer may beNULL, in which case the device has already synchronized. so like, don't panic if it'sNULL, that's just the device saying "already handled it, we're good" π
β RETURN β
0 on success, or a negative error code on failure. that's it, that's the whole vibe check π₯
π SEE ALSO π
kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c, plus the whole friend group:
struct vmw_kms_sou_surface_dirty(9)vmw_sou_crtc_mode_set_nofb(9)vmw_sou_crtc_helper_prepare(9)vmw_sou_crtc_atomic_disable(9)vmw_sou_primary_plane_cleanup_fb(9)vmw_sou_primary_plane_prepare_fb(9)vmw_sou_plane_update_bo(9)vmw_sou_surface_fifo_commit(9)vmw_sou_surface_clip(9)vmw_kms_sou_do_surface_dirty(9)vmw_sou_bo_fifo_commit(9)vmw_sou_bo_clip(9)vmw_kms_sou_do_bo_dirty(9)vmw_sou_readback_fifo_commit(9)vmw_sou_readback_clip(9)vmw_kms_sou_readback(9)
no cap, that's a whole squad π«Ά
π real talk though:out_fencemay hand you aNULLpointer and that is not an error, it just means the device already synchronized. don't @ me, it's in the docs.
and that's the whole page, bestie! this one's from ./drivers/gpu/drm/vmwgfx, dated October 2026, and the manual page itself is vmw_sou_plan...date_surface(9) π go forth and update those surfaces, ily, mwah πβ¨πΈ
π¦ 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