Hi, I am working on a ARM board and have patched its kernel to support V4L2 with help of Mr. Hans Verkuil (here is the discussion: http://comments.gmane.org/gmane.linux.drivers.video-input-infrastructure/80350). The problem I have now is the actual frame rate is divided by a factor of 2.5. For instance, when I set the framerate to be @25fps, I can capture images at exact 10fps. Here is more results showing the framerate reported by "v4l2-ctl -P" command vs. the measured framerate inside my C++ code (I capture each image and throw them away to eliminate irrelevant times in measuring fps): Reported by v4l2-ctl: 10 fps -> Actual: 4 fps Reported by v4l2-ctl: 15 fps -> Actual: 6 fps Reported by v4l2-ctl: 25 fps -> Actual: 10 fps Reported by v4l2-ctl: 30 fps -> Actual: 12 fps This seems to be a clocking issue. Is there any constant multiplier in V4L2 (or UVC?) code which depends on the hardware and be cause of this problem? Thanks, Isaac -- 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
