Hi Samir, On Monday 26 November 2007 10:40, Samir Ibradzic wrote: > Hello there, this is my first post here (& ever on berilos), sorry for > any inconvenience & ignorance...
No worries. You didn't cause any inconvenience. Your report is clear and includes all the information I need. > I have this cellphone whose camera can work as UVC device (at least in > windows it does). Have been playing a bit with uvcvideo driver, but this > camera doesn't seem to be supported (tried builds 141 & 147)... > > Thank you for all UVC supporting efforts! You're welcome :-) > Btw, what is the meaning of 'Failed to initialize the device (-5).' ? You can find a description of the error codes printed by the Linux UVC driver in errno.h. In this case, -5 is -EIO (I/O error). This means the driver failed to initialize the device because of an unexpected error during communication with the camera. > here's dmesg info; > > [ 5954.620000] usb 2-1: new full speed USB device using uhci_hcd and > address 11 > [ 5954.796000] usb 2-1: configuration #1 chosen from 1 choice > [ 5954.800000] uvcvideo: Probing generic UVC device 1 > [ 5954.800000] uvcvideo: Found format MJPEG. > [ 5954.800000] uvcvideo: - 320x240 (15.0 fps) > [ 5954.800000] uvcvideo: Found UVC 1.10 device au W33SA (0474:0722) > [ 5954.800000] uvcvideo: Scanning UVC chain: OT 3 <- PU 2 <- IT 1 > [ 5954.800000] uvcvideo: Found a valid video chain (1 -> 3). > [ 5954.804000] uvcvideo: Failed to query (135) UVC control 1 (unit 0) : > -32 (exp. 34). > [ 5954.804000] uvcvideo: Failed to query (129) UVC control 1 (unit 0) : > -32 (exp. 34). > [ 5954.804000] uvcvideo: Failed to initialize the device (-5). The last message is merely a summary of the previous two messages. Your camera stalled when queried for its default (135) and current (129) configurations. The driver starts by querying the default configuration, and falls back to current configuration if the first request fails. As the first request isn't issued by the Windows UVC driver, it might confuse the camera and make it fail responding to the second request. This can be checked by trying the attached patch which issues the second request only. Best regards, Laurent Pinchart
Index: uvc_video.c =================================================================== --- uvc_video.c (revision 147) +++ uvc_video.c (working copy) @@ -897,8 +897,7 @@ /* Some webcams don't suport GET_DEF request on the probe control. We * fall back to GET_CUR if GET_DEF fails. */ - if ((ret = uvc_get_video_ctrl(video, probe, 1, GET_DEF)) < 0 && - (ret = uvc_get_video_ctrl(video, probe, 1, GET_CUR)) < 0) + if ((ret = uvc_get_video_ctrl(video, probe, 1, GET_CUR)) < 0) return ret; /* Check if the default format descriptor exists. Use the first
_______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
