[linux-dvb] Re: "Video datastream broken" the legend continues...

[Philippe Gramoullé <philippe.gramoulle@mmania.com>]

Hello Hermann,

On Fri, 30 Jul 2004 15:08:33 +0200
Hermann Gausterer <mrq1@gmx.net> wrote:

  | On Friday 30 July 2004 14:34, Joerg Riechardt wrote:
  | > yes, that compiled, thanks.
  | > But now I get no output when I run it ...
  | > Would you mind to make a binary for 2 cards?
  | 
  | on line 29, there is the "#define MAXDEVICE 3" 
  | you should put it this number to the actual number
  | of dvb cards in you system (2 in you two card system)..

i've set it to 1 , as i only have 1 Rev 1.3 board.

Currently i'm using 2.4 dvb-kernel CVS with the original unpatched ves1x93 frontend driver ( not the moded alps_bsrv2 driver
from Alfred Zastrow ),

Though i don't see any automatic channels zapping yet, here is a sample output of the modified szap:

# ./szap-status-time
1091588228.942824 Status Change: Adapter 0 | 00 -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588229.237403 Status Change: Adapter 0 | 1f -> 0c | fe_no__signal| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588229.257379 Status Change: Adapter 0 | 0c -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588231.137414 Status Change: Adapter 0 | 1f -> 0c | fe_no__signal| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588231.157379 Status Change: Adapter 0 | 0c -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588233. 37402 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588233. 57381 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588234.937402 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588234.957378 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588236.837403 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588236.857379 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588238.737402 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588238.757377 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
etc...

With the linux-dvb drivers from 2003-11-08 ( original unpatched alps_bsrv2 frontend driver ), i get this:


# ./szap-status-time
1091588741.740477 Status Change: Adapter 0 | 00 -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588754.397413 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588754.417386 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588772. 67409 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588772. 87384 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588774.727409 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588774.747385 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588792.787409 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588792.807385 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588796.197416 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588796.217386 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588801.327410 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588801.347385 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK
1091588803.227410 Status Change: Adapter 0 | 1f -> 0d | FE_HAS_SIGNAL| fe_no__carrier| FE_HAS_VITERBI| FE_HAS_SYNC| fe_no__lock
1091588803.247385 Status Change: Adapter 0 | 0d -> 1f | FE_HAS_SIGNAL| FE_HAS_CARRIER| FE_HAS_VITERBI| FE_HAS_SYNC| FE_HAS_LOCK


It grabs the FE_HAS_LOCK flag much longer with the later frontend driver.

Hope that helps ( and will gladly test out any patch set that would help nail those Rev1.3/ves1x93 issues )

Thanks,

Philippe