[linux-dvb] Re: tzap not locking on

["Ivor Hewitt" <ivor@ivor.org>]

Huzzah, I can report success with that patch with my Avermedia card too in the
UK.

Fortuitous timing that post resurfacing, I've been trying to figure out at
what point my Avermedia card stopped working and was getting close to throwing
the card out of the window.
I have a Nova-T and an Avermedia, however at some point in the past few months
the Avermedia stopped working and I've been stepping backwards through patches
to try and locate the change. (I was trying to fix some power management and
SATA problems and hadn't tested the video capture for ages and when I did it
didn't!)

So I can confirm that patch fixes my problem too. Yay.

Cheers,
Ivor.

-- 
http://ivor.org - leylandii hedge -- http://ivor.it - technology

SquirrelMail - webmail for nuts.

> The only other person who's actually said this fixed anything for them,
> was Hamish Moffatt, another Australian. So Australia seems to be a
> common factor between people having problems with this -- maybe
> something to do with our 7MHz channels?
>
> Anything less than 350ms seemed to caused tuning to take a while, quite
> often.
>
> Marty.
>
> Johannes Stezenbach wrote:
>
>>Martin Kenny wrote:
>>
>>
>>>I think you might be helped by a patch I submitted a while back (but I
>>>think got lost in the noise) for
>>>linux/drivers/media/dvb/frontends/sp887x.c. It's probably out of sync
>>>with CVS (and maybe kernel 2.6.7) right now, but it should be pretty
>>>easy to apply by hand.
>>>
>>>See
>>>http://www.linuxtv.org/mailinglists/linux-dvb/2004/06-2004/msg00055.html
>>>for details.
>>>
>>>
>>
>>--- sp887x.c.old        2004-06-01 22:50:06.000000000 +0930
>>+++ sp887x.c    2004-06-02 18:03:51.154418192 +0930
>>@@ -636,9 +636,9 @@
>>       case FE_GET_TUNE_SETTINGS:
>>       {
>>               struct dvb_frontend_tune_settings* fesettings = (struct
>> dvb_frontend_tune_settings*) arg;
>>-               fesettings->min_delay_ms = 50;
>>-               fesettings->step_size = 0;
>>-               fesettings->max_drift = 0;
>>+               fesettings->min_delay_ms = 350;
>>+               fesettings->step_size = 166666*2;
>>+               fesettings->max_drift = (166666*2)+1;
>>               return 0;
>>       }
>>
>>
>>Hm, step_size and max_drift > 0 means that the frontend core will
>>do zig-zag scanning, which I thought was not very useful for DVB-T.
>>Also 350ms delay seems a bit long.
>>
>>Anyway, if someone else can confirm that this improves tuning, I
>>would just commit it.
>>
>>
>>Johannes
>>
>>
>>
>>
>
>