[linux-dvb] atscscan for testing QAM256

[Michael Krufky]

Mac Michaels wrote:

>On Sunday 19 June 2005 11:21 pm, Michael Krufky wrote:
>  
>
>>What does lock status 0x0c, 0x0d, and 0x04 mean?  These
>>are what I am mostly getting on each channel, along with
>>(tuning failed).
>>    
>>
>
>from file:
>
>/usr/src/linux/include/linux/dvb/frontend.h
>
>These are actually a set of values. 0x1F means everything is 
>OK.
>
>typedef enum fe_status {
>	FE_HAS_SIGNAL     = 0x01,   /*  found something above the 
>noise level */
>	FE_HAS_CARRIER    = 0x02,   /*  found a DVB signal  */
>	FE_HAS_VITERBI    = 0x04,   /*  FEC is stable  */
>	FE_HAS_SYNC       = 0x08,   /*  found sync bytes  */
>	FE_HAS_LOCK       = 0x10,   /*  everything's working... */
>	FE_TIMEDOUT       = 0x20,   /*  no lock within the last ~2 
>seconds */
>	FE_REINIT         = 0x40    /*  frontend was reinitialized,  
>*/
>} fe_status_t;
>  
>
This answers the meaning of 0x04 ... but what about 0x0c and 0x0d?  
Perhaps this is a good sign that I'm close to getting lgdt3302 code 
working correctly with thomson ddt7611 tuner?

-- 
Michael Krufky