So where are the logs?
Can you give me the link to the sattelite you're using on lyngsat site? There are many Atlantic (Birds) sats so I don't know which one you're referring to.
I'm sure Manu knows much more about that driver than I am, but I think the code takes the clock into consideration when calculating parameters for search algorithm.
On Sun, Oct 5, 2008 at 4:13 PM, Emmanuel ALLAUD <eallaud@xxxxxxxx> wrote:
Le 02.10.2008 01:38:03, Alex Betis a écrit :
> Manu,I loaded stb* with debug=5 IIRC.
>
> Please specify what sattelite and what frequency cause problems.
> Specify also a "good" transponder that locks.
> Can you send me the stb0899 module logs (with debug severity)?
The sats are in western Atlantic (I live in the Caribbean Islands):
good transponders: freqs=11093,11555,11675, bad one:11495.
As I said Carrier is detected but the data search algo fails, and, as
the only difference is th FEC, I guess that should be the problem.
Moreover as you probably have already noticed, the init values are
really different between mantis and TT-3200. Manu told me that it is
because they use different freq (99MHz for TT and 108MHz for Mantis),
but the handling of the registers are so different there might be other
differences also. Anyway it seems that both cards have some problematic
locking for some transponders so the fix might work for both.
I could do some further testing (even spreading printks in the code is
doable for me).
Bye
Manu
_______________________________________________
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
