STRUCT VIDTV_TUNER_DEV(9)
π 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 thedvb_frontendstructure thatvidtv_demodallocated. 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. forvidtvspecifically,vidtv_bridgefills 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms