[linux-dvb] Re: 2.6 driver + stv0299(wintv-nova) + channel change time too long

[Andrew de Quincey <adq_dvb@lidskialf.net>]

> but then the rest are allways the same :(
>
> abr 26 22:56:48 Dymony vdr[6525]: switching to channel 4
> Apr 26 22:56:49 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:49 Dymony kernel: dvb_frontend_get_event
> Apr 26 22:56:49 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:49 Dymony kernel: update_delay
> Apr 26 22:56:50 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:50 Dymony kernel: dvb_frontend_get_event
> Apr 26 22:56:50 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:50 Dymony kernel: update_delay
> Apr 26 22:56:51 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:51 Dymony kernel: dvb_frontend_get_event 		scratching my
> nose... Apr 26 22:56:51 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:51 Dymony kernel: update_delay
> Apr 26 22:56:52 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:52 Dymony kernel: dvb_frontend_get_event
> Apr 26 22:56:52 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:52 Dymony kernel: update_delay
> Apr 26 22:56:53 Dymony kernel: dvb_frontend_ioctl				here i go drink
> something Apr 26 22:56:53 Dymony kernel: dvb_frontend_get_event
> Apr 26 22:56:53 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:53 Dymony kernel: update_delay
> Apr 26 22:56:54 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:54 Dymony kernel: dvb_frontend_get_event
> Apr 26 22:56:54 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:54 Dymony kernel: update_delay
> Apr 26 22:56:55 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:55 Dymony kernel: dvb_frontend_get_event		yawns com to me
> Apr 26 22:56:55 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:55 Dymony kernel: update_delay
> Apr 26 22:56:56 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:56 Dymony kernel: dvb_frontend_get_event
> Apr 26 22:56:56 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:56 Dymony kernel: update_delay
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_call_frontend_notifiers
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_add_event
> Apr 26 22:56:57 Dymony kernel: dvb_call_frontend_notifiers
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_add_event
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_call_frontend_notifiers
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_autotune: drift:0 bending:0
> inversion:0 auto_step:0 auto_sub_step:0
> started_auto_step:0
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_ioctl
> Apr 26 22:56:57 Dymony kernel: dvb_frontend_internal_ioctl
>
>
> 			AND TUNED!! XD
>
> If u need more log will put one entire.. but it is toooo long

That is a bit weird.. as far as I can see, VDR is the bit doing the waiting 
there... 

From 22:56:48->22:56:57 it just seems to be calling FE_GET_EVENT... so its not 
going to tune as it hasn't issued the IOCTL to tell the frontend to tune yet.

The calls at 22:56:57 are the ones which actually do the tuning, and they take 
less than a second. 

Can you enable any sort of debugging in VDR? 


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