On Tue, Dec 2, 2008 at 6:34 PM, Christoph Pfister <christophpfister@xxxxxxxxx> wrote:
2008/11/17 e9hack <e9hack@xxxxxxxxxxxxxx>:
> Hi,
>
> if the current tuned transponder is scanned only and the output needs the frequency of the
> transponder, it is used the last frequency, which is found during the NIT scanning. This
> is wrong. The attached patch will fix this problem.
I probably missed that post (or forgot about it already :)).
What scan is being discused? dvb-apps scan utility (or the scan-s2 that I maintain)?
Any opinion about this patch? It seems ok from a quick look, so I'll
apply it soon if nobody objects.
I don't understand what's wrong with NIT advartised frequency?
For example, many satelite sites (such as lyngsat) have different frequencies listed for the same channel, generally a difference of 1 MHz here and there. That's probably caused since wide scans are probably done on all the possible frequencies.
Since driver tunning algorithm can zigzag in some frequency bounds it will probably be able to lock on the channel if you'll specify frequencies such as the following, assuming the real channel frequency is 12000000:
11998000
11999000
12000000
12001000
12002000
NIT specifies the correct frequency and that one should be used next time to tune.
Am I missing something?
> Regards,
> Hartmut
Thanks,
Christoph
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
