Hi Florian, Thanks for the patch.
On Thursday 09 September 2010 11:30:41 Florian Echtler wrote: > Hello everybody, > > since the topic of still image support has come up time and again, I've > decided to give it a shot. After reading the UVC spec, it seems that > there isn't too much difference to the normal operation, so I created a > new set of functions from uvc_probe_video, uvc_commit_video and friends. > These are called uvc_probe_still, uvc_commit_still and additionally > uvc_trigger_still. > > Just for testing, I replaced the original functions with calls to the > still image functions and got somewhat mixed results with my two cams: > > - the builtin camera in my Lenovo netbook doesn't really behave any > different, it still streams images as before > > - my Quickcam S5500 doesn't do anything, guvcview complains: > Could not grab image (select timeout): Resource temporarily unavailable > > I'm aware that this is a really ugly hack right now, but maybe it > provides a starting point for those of you with more insight into how > the driver works. I'd be glad for some hints as to how to proceed! The patch looks good to me, except of course that it's a hack :-) The real question we need to answer is how to expose the still image capture function to userspace. Should a new video node be created for still image capture ? The new video node could be linked to the existing one using the media controller API. Or should we use multiple open on a single video node ? In that case, how would we select video/still image capture ? I'm really open to suggestions here. We also need to remember that capturing a still image with method 2 (unlike method 3) will stop the live video stream for a brief time. Is that acceptable ? -- Regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
