vidtv_psi_pat_write_into(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vidtv_psi_pat_write_into(9)

okay so this is a page from the Kernel API Manual and honestly bestie, it's a little niche but we're gonna make it make sense. buckle up πŸŽ€


✨ NAME ✨

vidtv_psi_pat_write_into β€” literally writes the PAT into a buffer as MPEG-TS packets. that's the whole vibe. πŸ’«


🌸 SYNOPSIS 🌸

u32 vidtv_psi_pat_write_into (struct vidtv_psi_pat_write_args *args );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • args β€” one (1) instance of struct vidtv_psi_pat_write_args, no more no less. this is the lil bundle of info the function needs to do its thing. 🫢

πŸ’– DESCRIPTION πŸ’–

so what this function actually does is write the MPEG TS packets for a PAT table into a buffer. yes, those MPEG TS packets. it's giving encoder energy. πŸ”₯

and here's the tea: calling code will usually generate the PAT via a call to its init function, which means the caller is responsible for freeing it. you made it, you own it, you clean it up. no cap. 🧹✨


πŸ‘‘ RETURN πŸ‘‘

the number of bytes written into the buffer. and hear me out bestie β€” this is NOT equal to the size of the PAT, because more space is needed for TS headers during TS encapsulation. so like, don't come for this number thinking it's the PAT size, it's just not. πŸ’€


🌈 SEE ALSO 🌈


aaaand that's the whole page, bestie, you ate that πŸ“πŸ’œ this lil cutie lives at ./drivers/media/test-drivers/v... and it's stamped October 2026, so go forth and write those PATs. mwah πŸ’‹πŸ¦‹

πŸ“¦ where this page comes from