sti_vtg_get_pixel_number(9)
π NAME π
sti_vtg_get_pixel_number β okay so bestie, the manpage literally leaves this bit blank (just a lonely little dash, rip π), so all we've got is the name itself. It's the pixel-number getter for the STI VTG situation, and the full tea is right below π
β¨ SYNOPSIS β¨
u32 sti_vtg_get_pixel_number(struct drm_display_mode mode, int x);
π ARGUMENTS π
modeβ the display mode you're working with, i.e. the vibe of your screen setup π₯οΈxβ the row. Yep, the row. That's the whole description, she's concise π
πΈ DESCRIPTION πΈ
So what it does is: returns the pixel number according to the display mode, and it takes into account the Sync and Back Porch info π«Ά β like, it actually does the math instead of just raw-dogging the coordinate, iconic behavior honestly.
And the important bit: pixels are counted from 0 β. Zero-indexed, no cap, don't come for me with your 1-based nonsense π
π¦ SEE ALSO π¦
- Kernel file
./drivers/gpu/drm/sti/sti_vtg.cβ go read the source, bestie, it's literally right there π sti_vtg_get_line_number(9)β the sibling function, the line-number counterpart, matching set energy π
β¨ friendly reminder that this is Kernel API Manual territory β we're in the kernel, be normal, be careful, and keep those pixels zero-indexed π
and that's the whole page fr fr π β brought to you by the fine folks at ./drivers/gpu/drm/sti, dated October 2026, version vibes only, slay π
π
π¦ 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