vmw_stdu_pl...date_surface(9)
π vmw_stdu_plane_update_surface(9) β like, the Kernel API Manual, but make it cute
Okay bestie, buckle up π this is a page straight out of the Kernel API Manual, and it's all about vmw_stdu_plane_update_surface β the little function that updates your display unit for a surface-backed framebuffer. Yes, that's a lot of words. No, we're not skipping any of them. Let's go β¨
πΈ NAME πΈ
vmw_stdu_plane_update_surface β update the display unit for a surface-backed framebuffer, periodt π
β¨ SYNOPSIS β¨
int vmw_stdu_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 );
That's the whole vibe check right there β one function, five arguments, zero chill π«Ά
π¦ ARGUMENTS π¦
Breaking it down one bestie at a time:
dev_privβ the device private. Your main character device data, lowkey the source of truth πplaneβ the plane state. Not a literal airplane, we're talking DRM planes here βοΈold_stateβ the old plane state. Yes, we keep the receipts of what it used to be πvfbβ the framebuffer which is blitted to the display unit. She's getting copied over, iconic behavior πout_fenceβ if this is non-NULL, it will return a ref-counted pointer tovmw_fence_obj. And ngl, heads up: the returned fence pointer may be NULL, in which case the device has already synchronized. Not a bug, just the plot twist π
π RETURN π
0 on success, or a negative error code on failure. That's it, that's the whole mood β slay if it's zero, cry if it's negative π
π₯ SEE ALSO π₯
The whole friend group, in order, no one left out π β kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c, plus:
struct vmw_stdu_dirty(9)struct vmw_screen_target_display_unit(9)vmw_stdu_crtc_destroy(9)vmw_stdu_define_st(9)vmw_stdu_bind_st(9)vmw_stdu_populate_update(9)vmw_stdu_update_st(9)vmw_stdu_destroy_st(9)vmw_stdu_crtc_mode_set_nofb(9)vmw_stdu_bo_cpu_clip(9)vmw_stdu_bo_cpu_commit(9)vmw_kms_stdu_readback(9)vmw_kms_stdu_surface_clip(9)vmw_kms_stdu_surface_fifo_commit(9)vmw_kms_stdu_surface_dirty(9)vmw_stdu_encoder_destroy(9)vmw_stdu_connector_destroy(9)vmw_stdu_primary_plane_cleanup_fb(9)vmw_stdu_primary_plane_prepare_fb(9)vmw_stdu_plane_update_bo(9)vmw_stdu_primary_plane_atomic_update(9)vmw_stdu_init(9)vmw_stdu_destroy(9)vmw_kms_stdu_init_display(9)
Like, that's the entire group chat, and they all ate π β¨
fr fr, if you're digging into the vmwgfx display unit code, this list is your bestie for the restie β read them all before you touch anything π§
Okay bye, ily, go read the source π«Ά This cutie of a page lives over in ./drivers/gpu/drm/vmwgfx, dated October 2026, and it's signing off β 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