STRUCT DVB_FRONTEND_INFO(9)
πΈ struct dvb_frontend_info β from the Kernel API Manual β¨
okay bestie, so this is the struct dvb_frontend_info(9) page, straight out of the Kernel API Manual, and it's basically the little ID card your frontend hands you so you know what it can and can't do π
π NAME
struct dvb_frontend_info β frontend properties and capabilities. that's it, that's the whole vibe: it's the glow-up resume of your frontend π
β¨ SYNOPSIS
here's the whole struct, bestie, no cap β every field exactly as it lives in the header:
struct dvb_frontend_info {
char name[128];
enum fe_type type;
__u32 frequency_min;
__u32 frequency_max;
__u32 frequency_stepsize;
__u32 frequency_tolerance;
__u32 symbol_rate_min;
__u32 symbol_rate_max;
__u32 symbol_rate_tolerance;
__u32 notifier_delay;
enum fe_caps caps;
};
π«Ά Members
nameβ the name of the frontend. literally its government name πͺͺtypeβ DEPRECATED, bestie, do not use this on modern programs π a frontend can have more than one type, so this field just cannot keep up. if you wanna know what delivery systems a given frontend actually supports, useDTV_ENUM_DELSYSinstead β that's the main character here πfrequency_minβ minimal frequency supported by the frontend.frequency_maxβ minimal frequency supported by the frontend. (yes, the page actually says "minimal" here too β I'm not gaslighting you, that's just what the doc says π I'm literally the messenger)frequency_stepsizeβ all frequencies are multiples of this value. everything lines up on the grid, periodt πfrequency_toleranceβ the frequency tolerance.symbol_rate_minβ minimal symbol rate, in bauds (for Cable/Satellite systems).symbol_rate_maxβ maximal symbol rate, in bauds (for Cable/Satellite systems).symbol_rate_toleranceβ maximal symbol rate tolerance, in ppm (for Cable/Satellite systems).notifier_delayβ DEPRECATED, and not used by any driver. it's giving retired legend π«‘capsβ the capabilities supported by the frontend, as specified inenum fe_caps. this is the moment the frontend flexes π₯
π¦ Description
β οΈ note, and this part matters so listen up bestie: 1. the frequencies are specified in Hz for Terrestrial and Cable systems. 2. the frequencies are specified in kHz for Satellite systems. same struct, different units depending on the system β check before you math, fr fr π
π SEE ALSO
kernel file ./include/uapi/linux/dvb/frontend.h, plus the whole friend group:
enum fe_caps(9)struct dvb_diseqc_master_cmd(9)struct dvb_diseqc_slave_reply(9)enum fe_sec_voltage(9)enum fe_sec_tone_mode(9)enum fe_sec_mini_cmd(9)enum fe_status(9)enum fe_spectral_inversion(9)enum fe_code_rate(9)enum fe_modulation(9)enum fe_transmit_mode(9)enum fe_guard_interval(9)enum fe_hierarchy(9)enum fe_interleaving(9)enum fe_pilot(9)enum fe_rolloff(9)enum fe_delivery_system(9)enum atscmh_sccc_block_mode(9)enum atscmh_sccc_code_mode(9)enum atscmh_rs_frame_ensemble(9)enum atscmh_rs_frame_mode(9)enum atscmh_rs_code_mode(9)enum fecap_scale_params(9)struct dtv_stats(9)struct dtv_fe_stats(9)struct dtv_property(9)struct dtv_properties(9)
like, that's a whole group chat right there π«Ά
and that's the page!! π this one lives at ./include/uapi/linux/dvb and it's dated October 2026 β go off, kernel docs, you ate πβ¨
π¦ 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