nal_h264_read_filler(9)

💅 nal_h264_read_filler(9) — read filler data RBSP 🎀

okay bestie, welcome to the nal_h264_read_filler(9) page from the Kernel API Manual! this one is short, sweet, and absolutely does its little job. ✨

---

✨ NAME ✨

nal_h264_read_filler — Read filler data RBSP 💖

📜 SYNOPSIS 📜

ssize_t nal_h264_read_filler (const struct device *dev , void *src ,
size_t n );

🧚 ARGUMENTS 🧚

• dev — device pointer 🫶
• src — buffer with RBSP data that is read 🌸
• n — maximum size of src that shall be read 🎀

🌸 DESCRIPTION 🌸

Read a filler data RBSP from src up to a maximum size of n bytes and return the size of the filler data in bytes including the marker. periodt. 💅

This function is used to parse filler data and skip the respective bytes in the RBSP data. it's literally the parse-and-skip bestie, no cap. 🧹✨

The RBSP format of the filler data is specified in Rec. ITU-T H.264 (04/2017) 7.3.2.7 Filler data RBSP syntax. iconic reference behavior. 📚👑

🎀 RETURN 🎀

number of filler data bytes (including marker) or negative error. that's the whole vibe check: bytes on success, negative error when it's not slaying. 😭💖

🔥 SEE ALSO 🔥

Kernel file ./drivers/media/platform/allegro-dvt/nal-h264.c — the source file bestie, go look. 👀

• nal_h264_write_sps(9)
• nal_h264_read_sps(9)
• nal_h264_write_pps(9)
• nal_h264_read_pps(9)
• nal_h264_write_filler(9)

---

mwah 💋 that's the page! source/version: ./drivers/media/platform/alleg... and date: October 2026 — manual name nal_h264_read_filler(9), and yes, it ate. 🫶🌈