[linux-dvb] Q: to Frontend_info structure

[Rainer.Scherg@t-online.de (Rainer.scherg)]

Hi, 

I have some questions to the frontend-info structure in the current
dvb-api3:

How are the following frequency-variables defined?

--- snip ---
2.1.3 frontend information

struct dvb_frontend_info {
  char name[128];
  fe_type_t type;
  uint32_t frequency_min;
  uint32_t frequency_max;
  uint32_t frequency_stepsize;
  uint32_t frequency_tolerance;
  uint32_t symbol_rate_min;
  uint32_t symbol_rate_max;
  uint32_t symbol_rate_tolerance; /* ppm */
  uint32_t notifier_delay; /* ms */
  fe_caps_t caps;
};
--- snap ---


My guess is QPSK (fe_type) == MHz and  kHz for dvb-c and dvb-t.

But does this also apply to frequency_tolerance and
frequency_stepsize? My guess here is, ..._stepsize always is
in kHz and ..._tolerance is in Hz.

Any hint appreciated.

cu & tia
 Rainer




e.g.:

# dvbsnoop -s feinfo
dvbsnoop V1.2.76 -- http://dvbsnoop.sourceforge.net/ 
---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------
Name: "VES1893"
Frontend-type:       QPSK (DVB-S)
Frequency (min):     950.000 MHz
Frequency (max):     2150.000 MHz
Frequency stepsize:  250 kHz
Frequency tolerance: 29500 Hz
Symbol rate (min):     1.000000 MSym/s
Symbol rate (max):     45.000000 MSym/s
Symbol rate tolerance: 0 ppm
Notifier delay: 50 ms
Frontend capabilities:
    auto inversion
    FEC 1/2
    FEC 2/3
    FEC 3/4
    FEC 5/6
    FEC 7/8
    FEC AUTO
    QPSK
#


-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.