sti_vtg_get_pixel_number(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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