STRUCT VIDTV_MUX_SI(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct vidtv_mux_si(9) β€” Kernel API Manual

okay bestie, buckle up, because we're diving into the Kernel API Manual together and this one's a struct page 🌸 (yes, the header said struct vidtv_mux_si(9), and yes it's giving very much "let me explain the lore").


✨ NAME ✨

struct vidtv_mux_si β€” literally just here to store the PSI context. that's the whole job. icon behavior πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the whole shape of it, no cap, copy it exactly:

struct vidtv_mux_si {
    struct vidtv_psi_table_pat *pat;
    struct vidtv_psi_table_pmt **pmt_secs;
    struct vidtv_psi_table_sdt *sdt;
    struct vidtv_psi_table_nit *nit;
    struct vidtv_psi_table_eit *eit;
 };

like, five pointers. five little main characters. we love to see it πŸ’–


πŸŽ€ Members πŸŽ€

let's meet the cast, shall we? 🫢

  • pat β€” the PAT currently in use by the muxer. that's her job, that's her vibe.
  • pmt_secs β€” the PMT sections in use by the muxer. and listen, it's one for each program in the PAT β€” so if the PAT has a whole friend group, pmt_secs is carrying all of them 😭
  • sdt β€” the SDT in use by the muxer. showing up, doing the thing.
  • nit β€” the NIT in use by the muxer. also present. also thriving.
  • eit β€” the EIT in use by the muxer. (the original literally wrote it lowercase, "the EIT", and honestly? relatable. we keep it.)

πŸ’€ Description πŸ’€

so what is this thing for? lowkey simple: it stores the PAT, the PMT sections, and the SDT in use by the muxer. that's the whole assignment and she ate πŸ”₯

now for the fun part β€” how does the muxer even get these? bestie, it goes looking into the hardcoded channels in vidtv_channel, and then it periodically sends the TS packets for them πŸ‘€ that's the whole loop. no guessing, that's just what it says.

ngl this is a struct page, so don't come here looking for exit statuses or signals β€” there aren't any. only vibes and pointers 🧚

🌈 SEE ALSO 🌈

go read these next, i'm obsessed with cross-references honestly:

  • the Kernel file ./drivers/media/test-drivers/vidtv/vidtv_mux.h
  • struct vidtv_mux_timing(9)
  • struct vidtv_mux_pid_ctx(9)
  • struct vidtv_mux(9)
  • struct vidtv_mux_init_args(9)

and that's the page!! πŸŽ€ source/version line was ./drivers/media/test-drivers/v... and the date stamp said October 2026, so like… mark your calendar bestie, and remember: struct vidtv_mux_si(9) forever πŸ¦‹βœ¨πŸ’œ

πŸ“¦ where this page comes from