vidtv_psi_nit_write_into(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vidtv_psi_nit_write_into

okay bestie, welcome to the vidtv_psi_nit_write_into page from the Kernel API Manual β€” yes the whole manual, we're being fancy today ✨


🌸 NAME 🌸

vidtv_psi_nit_write_into β€” literally writes a NIT out as MPEG-TS packets into a buffer. That's the whole job. She's focused, she's iconic, she does one thing πŸ’–


✨ SYNOPSIS ✨

u32 vidtv_psi_nit_write_into(struct vidtv_psi_nit_write_args *args);

πŸŽ€ ARGUMENTS πŸŽ€

  • args β€” an instance of struct vidtv_psi_nit_write_args. That's your little bundle of everything the function needs, no cap 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

So basically, this function writes the MPEG TS packets for a NIT table into a buffer. NIT, packets, buffer β€” done πŸ’…

And here's the part you actually need to remember: calling code will usually generate the NIT via a call to its init function, and therefore it is the caller's responsibility to free it. Yes bestie, you made it, you clean it up. No leaving your NIT lying around like last time 😭


πŸ”₯ RETURN πŸ”₯

Returns the number of bytes written into the buffer, as a u32.

Heads up, this is NOT equal to the size of the NIT β€” because more space is needed for TS headers during TS encapsulation. So don't come for her when the numbers don't match, the headers are eating the extra bytes, periodt πŸ’€

🌈 SEE ALSO 🌈


aaaand that's the page πŸ§šπŸ’œ before you go β€” the source path up top got all shy and abbreviated as ./drivers/media/test-drivers/v..., the version stamp says October 2026, and this was page vidtv_psi_nit_write_into(9) all along, iykyk πŸŽ€ go free your NITs, bestie, mwah πŸ«ΆπŸ’–

πŸ“¦ where this page comes from