vmw_send_define_cursor_cmd(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vmw_send_define_cursor_cmd(9) πŸ’…

okay so bestie, this page is from the Kernel API Manual β€” and it's giving "queue a define cursor command" energy. no cap, it's a tiny kernel API moment and we're gonna get you through it. 🫢


✨ NAME ✨

vmw_send_define_cursor_cmd β€” queue a define cursor command. literally the whole name, and the whole job. πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

here's the exact signature, bestie β€” don't let the spacing jump-scare you:

void vmw_send_define_cursor_cmd (struct vmw_private *dev_priv , u32
*image , u32 width , u32 height , u32 hotspotX , u32 hotspotY );

it's void, so no return value is coming back to you. it queues the command, periodt. ✨


πŸ’– ARGUMENTS πŸ’–

okay, the cast of characters β€” six args, all iconic, all necessary:

  • dev_priv β€” the private driver struct. that's the driver's own lil private zone. 🫢
  • image β€” buffer which holds the cursor image. yes bestie, the cursor image lives here. ✨
  • width β€” width of the mouse cursor image. how wide the vibe is. πŸ“
  • height β€” height of the mouse cursor image. how tall the vibe is. πŸ“
  • hotspotX β€” the horizontal position of mouse hotspot. x marks the spot. 🎯
  • hotspotY β€” the vertical position of mouse hotspot. y marks the spot too. 🎯

🌸 SEE ALSO 🌸

go read these next, bestie β€” the lore continues:


that's the whole page, bestie. source/version: ./drivers/gpu/drm/vmwgfx; date: October 2026; page: vmw_send_define_cursor_cmd(9). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from