[linux-dvb] increasing frontend polling frequency for femon (wait queses in driver)?

thomas schorpp t.schorpp at gmx.de
Sun Jul 24 18:20:04 CEST 2005


Andrew de Quincey wrote:
>>claimed MTBF is surely 5-10 years for such chips.
>>more likely your card got overheated in summer in the pc case... ;)
>>this would cause chip damage, or electrostatics.
> 
> 

> The machines are well ventilated: they're in air conditioned comms. rooms at 
> multiple sites - I don't think they're overheating. It is a major pain 
> though :(
> 
> 

so. back.

with heatsink. picture attached. -no difference at all and the ves is at
25° with heatsink, without surely below 60° C (limit).

xxx

Q: i want to increase femon polling frequency to plot graphs, changed in
femon code (usleep 100000), but the driver reports only 1/sec, therere
some "wait" queues but i cant find constants, where to change that? thx.

xxx

BTW, the sun came out half an hour before and i had reception on ard
digital 1+ , now clouds are back and reception is gone again, look at
this (str):

ard digital 1 extra channel:

tatus 1f | signal ffff | snr c4c4 | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal ffff | snr c2c2 | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal ffff | snr bfbf | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal ffff | snr b9b9 | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 00 | signal a9a9 | snr b3b3 | ber 009ffff6 | unc ffffffff |
status 00 | signal a6a6 | snr b3b3 | ber 009ffff6 | unc ffffffff |
status 1e | signal fcfc | snr baba | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 1f | signal ffff | snr bcbc | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 1e | signal ffff | snr b6b6 | ber 009ffff6 | unc ffffffff |
FE_HAS_LOCK
status 00 | signal adad | snr b4b4 | ber 009ffff6 | unc ffffffff |
status 00 | signal aaaa | snr b4b4 | ber 009ffff6 | unc ffffffff |
status 00 | signal a6a6 | snr b4b4 | ber 009ffff6 | unc ffffffff |
status 00 | signal a3a3 | snr b5b5 | ber 009ffff6 | unc ffffffff |
status 00 | signal a0a0 | snr b5b5 | ber 009ffff6 | unc ffffffff |
status 00 | signal 9d9d | snr b6b6 | ber 009ffff6 | unc ffffffff |
status 00 | signal 9a9a | snr b7b7 | ber 009ffff6 | unc ffffffff |
status 00 | signal 9797 | snr b4b4 | ber 009ffff6 | unc ffffffff |
status 00 | signal 9494 | snr b4b4 | ber 009ffff6 | unc ffffffff |
status 00 | signal 9191 | snr b6b6 | ber 009ffff6 | unc ffffffff |
status 00 | signal 8e8e | snr b8b8 | ber 009ffff6 | unc ffffffff |
status 00 | signal 8b8b | snr b7b7 | ber 009ffff6 | unc ffffffff |
status 06 | signal 8787 | snr b6b6 | ber 009ffff6 | unc ffffffff |
status 00 | signal 8585 | snr b7b7 | ber 009ffff6 | unc ffffffff |
status 00 | signal 8282 | snr b7b7 | ber 009ffff6 | unc ffffffff |

see the signal? its floating!

is ber 009ffff6 a special signal? which?

kerrang! channel:

schorpp at tom1:~$ femon
using '/dev/dvb/adapter0/frontend0'
FE: VLSI VES1820 DVB-C (CABLE)
FE_HAS_LOCK
status 1f | signal ffff | snr e8e8 | ber 000015c2 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr eaea | ber 0000023a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr e9e9 | ber 0000023a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr e9e9 | ber 0000023a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr eaea | ber 000004ec | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr eaea | ber 000004ec | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr eaea | ber 000002ee | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr eaea | ber 000002ee | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr e8e8 | ber 000002ee | unc 00000000 |
FE_HAS_LOCK

schorpp at tom1:~$

there is no problem with the card, its the provider - kabelbw.

q.e.d.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: img_00081.jpg
Type: image/jpeg
Size: 17183 bytes
Desc: not available
Url : http://www.linuxtv.org/pipermail/linux-dvb/attachments/20050724/c07f0b24/img_00081.jpg


More information about the linux-dvb mailing list