nal_h264_read_pps(9)
π nal_h264_read_pps(9) π
okay so bestie, welcome to the Kernel API Manual entry for nal_h264_read_pps β yes that's a mouthful, yes it's iconic, and yes i'm gonna walk you through it like we're texting at 2am π«Ά
β¨ NAME β¨
nal_h264_read_pps β the girlie that reads a PPS NAL unit out of RBSP format. no cap, that's literally her whole job π
πΈ SYNOPSIS πΈ
ssize_t nal_h264_read_pps (const struct device *dev , struct
nal_h264_pps *pps , void *src , size_t n );
look at her signature, she's serving β¨
π ARGUMENTS π
devβ the device pointer, aka the plug. it's aconst struct device *, so hands off, don't go modifying her π«Άppsβ thestruct nal_h264_ppsthat gets filled up from the RBSP data. she's the empty cup, the data's the drink, iykyk π₯€srcβ the buffer holding the RBSP data. the source of truth, the main character honestly πnβ size ofsrc, in bytes. gotta know how much you're working with, periodt π
π¦ DESCRIPTION π¦
so what she does is: read the RBSP data out of src, and use it to fill in pps. that's it, that's the whole vibe check. lowkey simple, highkey essential π₯
β RETURN β
she returns the number of bytes read from src... or a negative error code if things went sideways π so yeah, check that return value, bestie, don't just ignore her π
π SEE ALSO π
- Kernel file
./drivers/media/platform/allegro-dvt/nal-h264.cβ go read the source, it's giving lore π nal_h264_write_sps(9)nal_h264_read_sps(9)nal_h264_write_pps(9)nal_h264_write_filler(9)nal_h264_read_filler(9)
the whole NAL friend group, fr fr π
ok that's the whole page bestie, go forth and parse those PPS NAL units πβ¨
mwah π this has been nal_h264_read_pps(9) from ./drivers/media/platform/alleg..., dated October 2026, in the Kernel API Manual β slay, bye ππ
π¦ 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