intel_vgpu_...rimary_plane(9)
π intel_vgpu_...rimary_plane(9)
okay so first things first, the header at the top of this page literally reads intel_vgpu_...rimary_plane(9) (yes bestie, it's truncated like that, that's just the title doing its thing) and it lives in the Kernel API Manual. anyways. let's get into it π«Ά
β¨ NAME β¨
intel_vgpu_decode_primary_plane β Decode primary plane. that's the whole vibe. it decodes. the primary plane. slay π
πΈ SYNOPSIS πΈ
int intel_vgpu_decode_primary_plane (struct intel_vgpu *vgpu , struct
intel_vgpu_primary_plane_format *plane );
like, look at her. returns an int, takes two pointers, absolutely iconic signature ngl β¨
π ARGUMENTS π
vgpuβ input vgpu. that's it, that's the arg β it's the inputvgpu, she goes in πplaneβ primary plane to save decoded info. this is where the decoded stuff gets stashed. This function is called for decoding plane. iykyk π¦
β RETURN β
0 on success, non-zero if failed. no cap, that's the whole contract β zero means we ate, anything else means something went sideways ππ₯
π SEE ALSO π
- Kernel file
./drivers/gpu/drm/i915/gvt/fb_decoder.cπ intel_vgpu_decode_cursor_plane(9)β her sister function, go say hi π§
ok that's the whole page, no extra lore, i'm not out here inventing behaviour fr fr π
and that's a wrap bestie!! this page came from the kernel source tree at ./drivers/gpu/drm/i915/gvt, dated October 2026, and the header/footer both spell the name intel_vgpu_...rimary_plane(9) β go forth and decode those planes, 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