Hans Verkuil wrote:
On Sunday 22 February 2009 12:17:58 Hans de Goede wrote:
<snipped a large part we agree upon (hurray!) >
Agreed, but it still is something which should be avoided if possible,
implementing polling also means adding a lot of IMHO unneeded code on the
userspace side.
I would prefer to make the "realtime" pivotting state available to the
app by adding flags containing the pivotting state at frame capture to
the v4l2_buf flags.
But if people dislike this, libv4l can simple poll the input now and
then.
I think this should be prototyped. Compare polling vs. putting the state in
the v4l2_buf flags and see if that makes a lot of difference in the user
experience compared to polling once a second. If it clearly improves things
for the user, then I have no objections to adding bits to v4l2_buf.
This is were the difficulties start, doing this 1 per second requires making
clock() calls and comparing timestamps (always tricky to get right). We could
do this once every X frames, but framerates can vary wildly with webcams.
My biggest concern is not the user experience, but the fact that needing to
poll uglyfies the userspace code. However thinking about this more, I guess we
could just poll every frame. That makes the polling code simple and should give
a good user experience.
<snip of more things we agree up on>
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
