packed_pixels_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… packed_pixels_addr β€” Kernel API Manual (section 9, bestie)

okay so this is packed_pixels_addr from the Kernel API Manual, section 9, and we're gonna get through it together, no cap πŸ’–

✨ NAME ✨

packed_pixels_addr β€” the function that hands you the pointer to the block containing the pixel at the coordinates you asked for 🎯

✨ SYNOPSIS ✨

void packed_pixels_addr (const struct vkms_frame_info *frame_info , int
x , int y , int plane_index , u8 **addr , int *rem_x , int *rem_y );

πŸŽ€ ARGUMENTS πŸŽ€

  • frame_info β€” the buffer metadata, like the vibe check for your whole buffer 🫢
  • x β€” the x (width) coordinate inside the plane
  • y β€” the y (height) coordinate inside the plane
  • plane_index β€” which plane we're on, the index of it πŸ‘‘
  • addr β€” the returned pointer, this is where the answer lands ✨
  • rem_x β€” the returned X coordinate of the requested pixel in the block
  • rem_y β€” the returned Y coordinate of the requested pixel in the block

🌸 DESCRIPTION 🌸

So it takes everything stored in the frame_info, plus a pair of coordinates, and it returns two things: the address of the block that contains this pixel, and the pixel's position inside that block. literally two-for-one, we love a multitasker πŸ’…

For the deets on how rem_x/rem_y actually behave, go check packed_pixels_offset β€” it's giving "read that one next" πŸ“–

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/gpu/drm/vkms/vkms_formats.c β€” that's the one, the source file, iykyk πŸ—‚οΈ


and that's the whole page, bestie, you ate that πŸ“ this lil masterpiece lives in ./drivers/gpu/drm/vkms, dated October 2026, and it is, of course, packed_pixels_addr(9) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from