So sometimes, just sometimes uvcapture runs through.... Not sure why or how yet. I get a file, which is attached, but it either contains junk or something strange. It's not a jpeg anyway. Anyone have any ideas what it is?
Cheers, James. Laurent Pinchart wrote:
Hi James,see attached for a svn diff. Be aware that I've not much idea what I'm doing with this code, blindly fumbling in the dark at the moment, so I'm certainly not advocating what I've changed! The changes do make the camera load though.Having a look at the descriptors, the device shouldn't require an entry in the USB IDs list.I added it to the list so it would have the UVC_QUIRK_PROBE_MINMAX, without it it doesn't get far at all. It seems the camera just doesn't support GET_DEF.Nice to know. The Apple iSight was high on the list of broken cams, but it seems the Microsoft ones might beat it :-)There is a command line capture program called uvccapture, you could try it.Excellent, that's just the kind of thing I was looking for. So the light on the camera comes on and stays on but it seems like uvccapture is hanging. Ctrl-c doesn't kill it but disconnecting the camera does. This is the command line and the error I get, before pulling out the cable: ./uvccapture -x640 -y480 -t0 ioctl querycontrol error 22 This is the dmesg output up to the disconnect: [17260296.440000] uvcvideo: Trying format 0x47504a4d (MJPG): 10000x10000. [17260296.440000] uvcvideo: Using default frame interval 133333.3 us (7.5 fps). [17260298.644000] uvcvideo: Trying format 0x47504a4d (MJPG): 10000x10000. [17260298.644000] uvcvideo: Using default frame interval 133333.3 us (7.5 fps). [17260826.716000] uvcvideo: Trying format 0x47504a4d (MJPG): 640x480. [17260826.716000] uvcvideo: Using default frame interval 33333.3 us (30.0 fps). [17260826.772000] uvcvideo: Control 0x00980913 not found. [17260849.252000] usb 5-2: USB disconnect, address 33 I've not had a chance to look into the ioctl error or the control error yet. I can't really play too much with this at work. I'll look into it soon though.The control shouldn't be an issue. It just means the camera doesn't implement V4L2_CID_GAIN.What happens when you run Ekiga ? The dmesg log doesn't show anything wrong. I assume it fails, but you didn't give any error message or failure description.Nothing really. No errors anywhere I can find. No video either, just the icon moving up and down in the video panel. Basically it's not too helpful at all.However, the camera supports MJPEG only. It can't stream YUV images.So I'm guessing that means it won't work with that gstreamer line then? I'll stick to uvccapture for now, it's simple and I like that. I'll look at other programs once that works.Could you raise the trace level to 255 (modprobe uvcvideo trace=255) ? The driver should get much more verbose then.By the way, the button on the camera is found and I get messages in dmesg when it's pressed. The mic works well too.So the only working features are either unusable (the button currently logs a message but doesn't do anything else) or out of the Linux UVC driver scope (audio is handled by the USB audio driver). Nice :-)Cheers, Laurent Pinchart -- This email has been verified as Virus free Virus Protection and more available at http://www.plus.net
<<attachment: snap.jpg>>
_______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
