Looks like VTUNER driver has changed during transition from 2.6.18-7.3 to 2.6.18-7.4 (that is, during transition to API5).
I see in the log that VTUNER is sending message with ID # 16 (10 times, just before the tuning attempt).
While in usbtuner (or extuner) all message IDs are defined only up to 14.
I guess, if #16 exists, #15 exist as well.
But these changes were not documented anywhere. At least I can not find any info.
Anybody knows where to look for this info?
and how to modify usbtuner/extuner to be able to work in 2.6.18-7.4 ?
Added:
Is this msg #16 the same as S2API is using to setup advanced properties of the tuning (FE_SET_PROPERTY)?
I also saw msg #17. Is it FE_GET_PROPERTY?
what's the format of the message? how "dtv_properties" is pushed into this msg?
is it something like this?
struct {
int type;
union {
struct dvb_frontend_parameters feparms;
fe_status_t status;
__u32 ber;
__u16 ss, snr;
__u32 ucb;
fe_sec_tone_mode_t tone;
fe_sec_voltage_t voltage;
fe_sec_mini_cmd_t burst;
unsigned short pidlist[MAX_PIDS];
unsigned char pad[60];
struct dtv_properties; // <--- new type of parameter for S2API tuning setup
} body;
} msg;
Alles anzeigen
then this msg #16 (if it's FE_SET_PROPERTY) should be called only once.
But it's called up to 10 times, as if it use "dtv_property" as a parameter (and not "dtv_properties"). That is, each S2API specific parameter is sent in a separate #16 message.
Can you please give som documentation on that?