> What about the v4l2_buffer.sequence field? I always assumed this is the
> number of transmitted, not read frames.
Exactly.
> > > And to answer your question, with USB webcams you cannot infer the
> > > timeperframe from any other fields in the V4L(2) API.
> >
> > Ok, then lets keep it.
>
> You do know v4l2_captureparm.timeperframe was intended to request a
> different frame period (frame skipping on the driver side, reducing the
> bus load) I suppose.
Oops, yes. I forgot that, sorry. So maybe add some bit to v4l_std_id
for "other" which can be used by the usb cams then?
Gerd
--
You can't please everybody. And usually if you _try_ to please
everybody, the end result is one big mess.
-- Linus Torvalds, 2002-04-20
_______________________________________________
Video4linux-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/video4linux-list
