nal_hevc_write_filler(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– nal_hevc_write_filler(9) πŸ’–

okay bestie, welcome to the Kernel API Manual β€” this one's short but it's lowkey iconic. we're writing filler data, and yes, filler can slay. ✨


✨ NAME ✨

nal_hevc_write_filler β€” write filler data RBSP πŸŽ€

🌸 SYNOPSIS 🌸

ssize_t nal_hevc_write_filler (const struct device *dev , void *dest ,
       size_t n );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” device pointer. yeah, the device. it's giving "who am I? the device." πŸ’…
  • dest β€” buffer to fill with filler data. this is where the filler goes, bestie 🫢
  • n β€” size of the buffer to fill with filler data. how many bytes of filler we're serving up πŸ“

πŸ‘‘ DESCRIPTION πŸ‘‘

so what this does: it writes a filler data RBSP to dest with a size of n bytes, then returns the number of written filler data bytes. literally that simple, no cap ✨

Use this function to generate dummy data in an RBSP data stream that can be safely ignored by hevc decoders. not me writing data that everyone just agrees to ignore 😭 it's giving "background character energy" but honestly? needed. the stream stays valid, the decoders stay unbothered, everyone wins πŸ’œ

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 β€” so if you wanna get into the nitty-gritty of the format, that's your reference, iykyk πŸ“–

🧚 RETURN 🧚

number of filler data bytes (including marker) or negative error. so either you get your byte count β€” marker included, don't forget the marker!! β€” or you get a negative error and it's giving πŸ˜­πŸ’€

🌈 SEE ALSO 🌈


lowkey reminder: n is the size of the buffer, and the return is the number of bytes written including the marker β€” don't mix those up, bestie, fr fr πŸ’…

that's the whole page!! brought to you by ./drivers/media/platform/alleg... (yes it's truncated in the footer, she's mysterious like that 🌈), October 2026 era β€” and the page name itself is nal_hevc_write_filler(9), so you always know exactly where you are πŸ’œ mwah, go write some filler, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from