tegra_ivc_r...t_next_frame(9)
πΈ tegra_ivc_read_get_next_frame(9) πΈ
okay bestie so you've stumbled into the Kernel API Manual and the page you want is tegra_ivc_read_get_next_frame(9) β yeah the header is a little mangled up there, that's just how it renders, we move π
β¨ NAME β¨
tegra_ivc_read_get_next_frame β peek at the next frame to receive @ivc pointer of the IVC channel π
like, literally just look, don't touch, don't take it out of the queue, we're window shopping here ποΈ
π SYNOPSIS π
int tegra_ivc_read_get_next_frame (struct tegra_ivc *ivc , struct
iosys_map *map );
π¦ ARGUMENTS π¦
ivcβ-- undescribed --π no cap, the original page literally does not describe this one. Not me making something up though, we're keeping it 100.mapβ-- undescribed --π same energy, no description given. iykyk.
π DESCRIPTION π
Peek at the next frame to be received, without removing it from the queue. It's giving "look with your eyes, not your hands" β¨
Returns a pointer to the frame, or an error encoded pointer. so like, if things went off, what you get back is an error dressed up as a pointer β the vibes will tell you π
π SEE ALSO π
Kernel file ./include/soc/tegra/ivc.h and honestly the whole friend group:
tegra_ivc_read_advance(9)tegra_ivc_write_get_next_frame(9)tegra_ivc_write_advance(9)tegra_ivc_notified(9)tegra_ivc_reset(9)
and that's the whole page bestie, mwah π«Ά this one lives over in ./include/soc/tegra, dated October 2026, and yeah the footer is out here spelling it tegra_ivc_r...t_next_frame(9) β the truncation is real, we don't gatekeep, we just scream internally ππ
π¦ 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