vmw_fifo_caps(9)

✨ NAME ✨

okay bestie, welcome to vmw_fifo_caps(9) from the Kernel API Manual 💅 this one is giving “small function, big main character energy”: vmw_fifo_caps gets the capabilities of the FIFO command queue, or returns 0 if fifo memory isn't present. periodt.

📜 SYNOPSIS 📜

uint32_t vmw_fifo_caps (const struct vmw_private *dev_priv );

like, that's the whole call ✨ and yes, it hands you back a uint32_t.

🫶 ARGUMENTS 🫶

• dev_priv — the device private context. that's the const struct vmw_private * bestie 🎀

🌈 RETURN 🌈

the capabilities of the FIFO command, or 0 if fifo memory is not present. no cap, that 0 is your “fifo memory isn't here” signal 💀

👑 SEE ALSO 👑

if you're doing the lore dive, this page points you here, and we're keeping every single one:

• Kernel file ./drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
• struct vmw_resource(9)
• struct vmw_surface_metadata(9)
• struct vmw_surface(9)
• struct vmw_res_cache_entry(9)
• enum vmw_dma_map_mode(9)
• struct vmw_sg_table(9)
• struct vmw_piter(9)
• struct vmw_sw_context(9)
• enum vmw_sm_type(9)
• has_sm4_context(9)
• has_sm4_1_context(9)
• has_sm5_context(9)
• has_gl43_context(9)
• vmw_resource_mob_attached(9)
• vmw_is_cursor_bypass3_enabled(9)
• vmw_piter_next(9)
• vmw_piter_dma_addr(9)
• vmw_piter_page(9)
• struct vmw_diff_cpy(9)
• VMW_DEBUG_USER(9)
• VMW_DEBUG_KMS(9)
• vmw_fifo_mem_read(9)
• vmw_fifo_mem_write(9)

cute footer sign-off time 🎀 source/version vibe: ./drivers/gpu/drm/vmwgfx, dated October 2026, and the page itself is vmw_fifo_caps(9) — mwah 💋✨