nal_hevc_read_filler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nal_hevc_read_filler(9)

okay so bestie, welcome to the Kernel API Manual ✨ this one's all about nal_hevc_read_filler β€” and yes it's a whole vibe.


🌸 NAME 🌸

nal_hevc_read_filler β€” read filler data RBSP πŸŽ€


✨ SYNOPSIS ✨

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

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” device pointer, literally just the device you're working with πŸ’–
  • src β€” the buffer with RBSP data that is read, that's the one getting looked at πŸ‘€
  • n β€” maximum size of src that shall be read, like the hard cap, no cap 🧒

πŸ’œ DESCRIPTION πŸ’œ

okay so what this does: it reads a filler data RBSP from src, up to a max of n bytes, and then returns the size of the filler data in bytes including the marker. iconic behavior honestly 🌟

This function is used to parse filler data and skip the respective bytes in the RBSP data. so it peeks, it counts, and it yeets past the boring bits πŸ’…

The RBSP format of the filler data is specified in Rec. ITU-T H.265 (02/2018) 7.3.2.8 Filler data RBSP syntax. like, that's the receipts, go read the spec if you want the lore πŸ“œ


🌈 RETURN 🌈

number of filler data bytes (including marker) β€” or a negative error 😭 (bestie the marker counts, don't forget the marker 🫢)


⭐ SEE ALSO ⭐


aaaand that's the whole page, bestie πŸ§šπŸ’– shoutout to ./drivers/media/platform/alleg... for dropping this one back in October 2026 β€” nal_hevc_read_filler(9), we love to see it. slay πŸ’…βœ¨

πŸ“¦ where this page comes from