- 29 Dec, 2008 40 commits
-
-
Manu Abraham authored
Thanks to Marko Schluessler <marco@lordzodiac.de> for pointing it out Signed-off-by:
Marko Schluessler <marco@lordzodiac.de> Signed-off-by:
Manu Abraham <manu@linuxtv.org> Signed-off-by:
Mauro Carvalho Chehab <mchehab@redhat.com>
-
Arvo Jarve authored
Signed-off-by:
Arvo Jarve <arvo@softshark.ee> Signed-off-by:
-
Manu Abraham authored
The Bug was found by Arvo Jarve <arvo@softshark.ee> It was a wonder how it worked in the case with this bug, STM verified this that this nibble was in fact insignificant and can be ignored. But still we need to fix all inconsistencies. Signed-off-by:
-
Arvo Jarve authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Arvo Jarve authored
In this case, we will be sure that there exists a carrier and the center frequency would be simply f1 - f2. In such a circumstance, the TR loop is simplified to doing a simple check for timing, rather than searching for the same. Signed-off-by:
-
Arvo Jarve authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Arvo Jarve authored
BUG! Setting CRL parameter overwrote the CR Algorithm type, eventually leading to wrong search algorithm to be employed in the DVB-S carrier loop optimization. Symptom: Once the CR optimization stage is passed either way, in a successful or failed manner, the very next carrier search will fail, due to no Carrier Search Algorithm specified. Signed-off-by:
-
Arvo Jarve authored
Signed-off-by:
-
Marko Schluessler authored
Signed-off-by:
-
Manu Abraham authored
* Saves 70 mS LOCK time on the STB6100 based * Saves 100 mS LOCK time on the TDA8261 based Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
which should have happenend in the DVB-S2 mode only, but reading it as it is for the other delivery systems causes nothing to say but LOCK_LOST, which just causes confusion amongst users. Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Thanks to Peter for the in depth explanation Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Need some thoughts, temporary for now .. Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
We need to check for tuner LOCK LOSS, especially in the case of simple PLL's Signed-off-by:
-
Manu Abraham authored
* Reduces szapping time a lot * increased stability at Low Symbol rates * overall increases reliability in tuning Signed-off-by:
-
Marko Schluessler authored
probably should stop fiddling with code late nights. :-( Thanks to Marco for pointing it out and fixing it. Signed-off-by:
-
Manu Abraham authored
V4L/DVB (9405): Practical tests show that the TT S2 3200 has I/Q inputs inverted, similar to the KNC1. Don't have this hardware and cannot verify this for myself, but from the reports this looks to be quite a reasonable and correct hypothesis. Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
Signed-off-by:
-
Manu Abraham authored
This is a racy situation. Inversion is default OFF on the TT S2 3200 hardware, unlike the KNC1 where it is default Inverted Signed-off-by:
-
Manu Abraham authored
Use an enumeration for I/Q Swap rather than an int, easier to spot the nasty ones Signed-off-by:
-
