jpeg_v5_3_0...ing_get_rptr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– jpeg_v5_3_0_dec_ring_get_rptr β€” get read pointer πŸ’–

okay so bestie, you're in the Kernel API Manual and this is page jpeg_v5_3_0...ing_get_rptr(9) β€” yes the title gets truncated like that, it's giving main-character-with-a-long-name energy and we're rolling with it πŸŽ€


✨ NAME ✨

jpeg_v5_3_0_dec_ring_get_rptr β€” literally just get the read pointer, that's the whole gig 🫢


🌸 SYNOPSIS 🌸

uint64_t jpeg_v5_3_0_dec_ring_get_rptr (struct amdgpu_ring *ring );

that's it. one function, one arg, returns a uint64_t. slay πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ring β€” an amdgpu_ring pointer, iykyk. it's the ring you're asking about, the whole main character of this call ✨

⭐ DESCRIPTION ⭐

Returns the current hardware read pointer. that's it, that's the vibe β€” no cap, no side quests, just the read pointer, fresh from the hardware 🩷


πŸŽ€ SEE ALSO πŸŽ€

the source lives here, go peek if you want the lore:

  • Kernel file ./drivers/gpu/drm/amd/amdgpu/jpeg_v5_3_0.c

and the whole friend group, bestie 😭:

like the wptr one is literally right there, they're a matching set πŸ’œ


fr fr though β€” this page is from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it's titled jpeg_v5_3_0...ing_get_rptr(9). read pointer acquired, era concluded, periodt πŸŒˆπŸ‘‘
πŸ“¦ where this page comes from