[linux-dvb] Re: Missing LOCK with tda10045h

[Henning Glawe <glaweh@physik.fu-berlin.de>]

On Tue, Jun 17, 2003 at 09:59:55AM +0100, Andrew de Quincey wrote:
> > status 00 | signal 000b | snr 005d | ber 000040f8 | unc 00000000 |
> > status 00 | signal 000b | snr 005d | ber 000040f8 | unc 00000000 |
> If you see that kind of BER with this driver, it usually means one of the 
> other parameters is wrong (e.g. fec).
I just took the channels.conf for dvb-t in berlin from the DVB CVS, I
expected them to be working, though I don't know anything at all about
DVB :(

> > 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). 

# tzap ZDF
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 570000000 Hz
status 00 | signal c3c3 | snr 8c8c | ber 00000000 | unc ffffffff | 
status 00 | signal c3c3 | snr fdfd | ber 000040f8 | unc 00000000 | 
status 00 | signal c2c2 | snr fdfd | ber 000040f8 | unc 00000000 | 
status 00 | signal c3c3 | snr fcfc | ber 000040f8 | unc 00000000 | 
status 00 | signal c3c3 | snr fdfd | ber 000040f8 | unc 00000000 | 
status 00 | signal c3c3 | snr fdfd | ber 000040f8 | unc 00000000 | 
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 | 
status 00 | signal c3c3 | snr 4d4d | ber 00000000 | unc 00000000 | 
status 00 | signal c2c2 | snr 3d3d | ber 00000000 | unc 00000000 | 
status 00 | signal c3c3 | snr 5555 | ber 00000000 | unc 00000000 | 
status 00 | signal c1c1 | snr 5e5e | ber 00000000 | unc 00000000 | 
status 00 | signal c1c1 | snr 6363 | ber 00000000 | unc 00000000 | 
status 00 | signal c1c1 | snr 5757 | ber 00000000 | unc 00000000 | 
status 00 | signal c1c1 | snr 5e5e | ber 00000000 | unc 00000000 | 



# loaded modules are:

Module                  Size  Used by    Not tainted
dvb-ttpci-budget        5840   0  (unused)
saa7146_vv             32036   0  (unused)
saa7146                10048   0  [dvb-ttpci-budget saa7146_vv]
tda10045h               9572   1 
dvb-core               39136   0  [dvb-ttpci-budget tda10045h]
video-buf              10992   0  [saa7146_vv]
v4l2-common             2720   0  [saa7146_vv]
v4l1-compat            11432   0  [saa7146_vv]
videodev                5824   0  [saa7146_vv]

# I hope some _relevant_ log output, this repeats over and over again...

Jun 20 19:12:07 av kernel: tda10045h_read_byte: reg=0x7
Jun 20 19:12:07 av kernel: tda10045h_read_byte: success reg=0x7,
data=0x8, ret=2
Jun 20 19:12:07 av kernel: tda10045h_write_byte: reg=0x7, data=0x0
Jun 20 19:12:07 av kernel: tda10045h_write_byte: success reg=0x7,
data=0x0, ret=1
Jun 20 19:12:08 av kernel: tda10045h_init


Jun 20 19:12:08 av kernel: tda10045h_write_byte: reg=0xe, data=0x0
Jun 20 19:12:09 av kernel: tda10045h_write_byte: success reg=0xe,
data=0x0, ret=1
Jun 20 19:12:09 av kernel: tda10045h_init: fw_pos=0x40

Jun 20 19:12:09 av kernel: tda10045h_init: fw_pos=0x775b
Jun 20 19:12:09 av kernel: tda10045h_write_mask: reg=0x7, mask=0x10,
data=0x0
Jun 20 19:12:09 av kernel: tda10045h_read_byte: reg=0x7
Jun 20 19:12:09 av kernel: tda10045h_read_byte: success reg=0x7,
data=0x0, ret=2
Jun 20 19:12:09 av kernel: tda10045h_write_byte: reg=0x7, data=0x0



Why does the driver enter tda10045h_init so often ? 

-- 
c u
henning


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