2011/3/6 adq <adq@xxxxxxxxxxxxx>: > 2011/3/6 Antti Palosaari <crope@xxxxxx>: >> On 03/06/2011 02:24 PM, adq wrote: >>> >>> Another issue I've noticed just now: The UCBLOCKS measure isn't reset: >>> it seems to be an accumulative counter, which isn't correct from the >>> DVB API (if I remember correctly). >>> >>> This explains why tvheadend's "quallity" measure gradually tends to 0, >>> since it is assuming UCBLOCKS is non-accumulative. >> >> 2.2.7 FE READ UNCORRECTED BLOCKS DESCRIPTION >> This ioctl call returns the number of uncorrected blocks detected by the >> device driver during its lifetime. For meaningful measurements, the >> incrementin block count during a specific time interval should be >> calculated. For this command, read-only access to the device is sufficient. >> Note that the counter will wrap to zero after its maximum count has been >> reached. > > (this time to the list as well) > > Hah! Sorry, its been a while :) > > In that case, I need to look at the tvheadend source. Hmm, lots of the frontend drivers have this incorrect then. e.g. tda10021.c resets the UCBLOCKS counter on every read. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
