En/na Richard Scobie ha escrit:
status 03 | signal 8675 | snr 0000 | ber 001fffff | unc 00000000 |
status 1f | signal 8435 | snr 0000 | ber 00000000 | unc 00000013 |
FE_HAS_LOCK
status 1f | signal 8455 | snr 0000 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal 844e | snr 0000 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
The crucial ones here are ber and unc.
These values are useless anyway: no driver (or at least none of the one
I looked at to write my own) complies with the specification of the api,
so the magnitudes aren't comparable between one card and the other. In
fact, if you want to know how a driver is to scale the values you have
to look at an older specification of the api, since the current one
doesn't give any hint on the scale of these values.
As a side note, the api spec says that unc should be cumulative during
the lifetime of the frontend, so this driver (and probably most others)
is wrong, since the value cannot go back to 0 after being 13.
Bye
--
Luca
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
