Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: Missing LOCK with tda10045h



On Friday 20 June 2003 21:13, Ben McKeegan wrote:
> On Fri, 20 Jun 2003, Henning Glawe wrote:
> > > > so it seems to upload the tda10045h firmware with each line of the
> > > > tzap output...
> > >
> > > Thats weird. Unless its failing to upload properly, I'm not sue how
> > > that can happen. You're definitely using the latest version of it?
> >
> > just installed 2.15a; the problem seems to be the same (dvb kernel
> > driver, checked out this morning).
>
> For what it's worth, mine still does this as well, but only when it fails
> to lock on to a signal (i.e. when I've got the wrong settings)
>
> > ...
> > status 00 | signal c2c2 | snr fcfc | ber 000040f8 | unc 00000000 |
> > status 00 | signal c3c3 | snr fdfd | ber 000040f8 | unc 00000000 |
> > status 00 | signal c2c2 | snr fdfd | ber 000040f8 | unc 00000000 |
> > status 00 | signal c2c2 | snr fdfd | ber 000040f8 | unc 00000000 |
> > status 00 | signal c3c3 | snr 5050 | ber 00000000 | unc 00000000 |
> > status 00 | signal c3c3 | snr 5b5b | ber 00000000 | unc 00000000 |
> > ...
>
> I get exactly the same ber pattern of a 000040f8, followed by 00000000.
> It is only when the ber changes to 00000000 that the driver starts calling
> tda10045h_init on each iteration.

Apologies for taking a while to get back on this, but I've been too busy at 
work.

OK..... theres a flag in the driver which prevents tda10045h_init() being 
called more than once. The only time this is reset is if the upper layers of 
DVB tuning code resets the tda10045h with FE_RESET. I'll have a look into 
this issue.



-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index