vmw_cursor_...atomic_check(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vmw_cursor_plane_atomic_check πŸ’…

okay so bestie, welcome to the vmw_cursor_...atomic_check(9) page from the Kernel API Manual β€” yes the title is literally abbreviated like that, it's giving "we ran out of room on the header" energy πŸŽ€ but don't worry, the full name is right down there and it slays.


✨ NAME ✨

vmw_cursor_plane_atomic_check β€” literally just checking if the new state is okay. that's it. that's the whole job. vibe check for your cursor plane πŸ¦‹


🌸 SYNOPSIS 🌸

int vmw_cursor_plane_atomic_check (struct drm_plane *plane , struct
       drm_atomic_commit *state );

copy that exactly btw, don't get creative with the spacing, she's written like that on purpose πŸ’€


πŸŽ€ ARGUMENTS πŸŽ€

  • plane β€” the cursor plane, the main character of this whole operation πŸ‘‘
  • state β€” all the info on the new plane state, like the receipts for what the plane's about to become πŸ”₯

🧚 DESCRIPTION 🧚

so this function is your moment β€” this is the chance to fail if the new cursor state does not fit our requirements πŸ’… like genuinely, this is where you're allowed to say "nope, that doesn't work for us" before anything gets committed.

it's the vibe check before the glow-up, iykyk 🌈

Returns 0 on success ✨ β€” zero means we're good, we're slaying, we're moving on.

lowkey important: this is described as a chance to fail. so if the new state doesn't fit the requirements, this is where it gets caught. no cap.

πŸ‘‘ SEE ALSO πŸ‘‘

go read those too, they're all part of the same friend group fr fr 🫢


and that's the page!! sourced from ./drivers/gpu/drm/vmwgfx, dated October 2026 β€” icons only, no notes πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from