STRUCT VIDTV_TUNER_DEV(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct vidtv_tuner_dev(9) β€” straight from the Kernel API Manual πŸŽ€

okay bestie, sit down, because today we're meeting struct vidtv_tuner_dev β€” literally the tuner struct. no cap, that's its whole NAME: The tuner struct. iconic behavior honestly ✨


🌸 SYNOPSIS 🌸

here's the whole vibe, verbatim, don't touch:

struct vidtv_tuner_dev {
    struct dvb_frontend *fe;
    struct vidtv_tuner_hardware_state hw_state;
    struct vidtv_tuner_config config;
 };

three members, three little besties, all living in one struct 🫢


πŸ¦‹ Members πŸ¦‹

  • fe β€” a pointer to the dvb_frontend structure that vidtv_demod allocated. it's giving "handed down from the demod department" πŸ’…
  • hw_state β€” a struct that simulates the tuner's hardware state, as if we actually had physical tuner hardware sitting there. pretend hardware, real struct, we love a simulation moment 🧚
  • config β€” the config used to start the tuner module, usually filled in by a bridge driver. for vidtv specifically, vidtv_bridge fills this in before the tuner module gets probed. so yes, it's pre-filled, it's prepared, it's main character energy πŸ‘‘

⭐ SEE ALSO ⭐

  • Kernel file ./drivers/media/test-drivers/vidtv/vidtv_tuner.c
  • struct vidtv_tuner_hardware_state(9)
go read that other struct too bestie, iykyk πŸ”₯

and that's the whole page, fr fr πŸ’– this was pulled straight from ./drivers/media/test-drivers/v... and dated October 2026 β€” so like, future-coded but make it kernel. the page itself is struct vidtv_tuner_dev(9), and it ate. periodt πŸ’€πŸŒΈ

πŸ“¦ where this page comes from