vidtv_psi_pmt_write_into(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vidtv_psi_pmt_write_into(9) β€” the kernel API manual moment

okay bestie, so you've wandered into the kernel API manual (that's the manual name, iykyk) and landed on this little icon: vidtv_psi_pmt_write_into. let's get into it ✨


✨ NAME ✨

vidtv_psi_pmt_write_into β€” writes a PMT as MPEG-TS packets into a buffer. literally that's the whole job, and she does it flawlessly πŸŽ€


🌸 SYNOPSIS 🌸

u32 vidtv_psi_pmt_write_into (struct vidtv_psi_pmt_write_args *args );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • args β€” an instance of struct vidtv_psi_pmt_write_args. that's your little bundle of everything the function needs. hand her the struct, she does the rest 🫢

πŸ’– DESCRIPTION πŸ’–

so this function writes out the MPEG TS packets for a PMT section into a buffer. that's it. that's the vibe.

the tea though β˜•: calling code will usually generate the PMT section via a call to its init function β€” which means the calling code is responsible for freeing it. not her. not the function. you. so don't forget, bestie, or that's a leak and the leak is giving 😭


πŸ”₯ RETURN πŸ”₯

the number of bytes written into the buffer πŸ’«

and no, before you ask β€” this is NOT equal to the size of the PMT section, because more space is needed for TS headers during TS encapsulation. so the number is bigger than the section. that's on purpose. periodt.


🌈 SEE ALSO 🌈

the whole friend group, in order, no cap:


ok and one last thing before you go β€” this page came from ./drivers/media/test-drivers/v... and it's dated October 2026, so screenshot it, cite it, whatever, because that's the source and the version and she's iconic for it πŸ’œ

stay hydrated, free your PMT sections, and slay the encapsulation baybee 🧚⭐

πŸ“¦ where this page comes from