Re: [Linux-uvc-devel] sanyo cg10
Il 19/11/2010 01:28, Laurent Pinchart ha scritto: Hi Riccardo, Hi Laurent, On Monday 01 November 2010 12:01:50 Riccardo Magliocchetti wrote: Il 30/10/2010 20:58, Laurent Pinchart ha scritto: On Friday 22 October 2010 21:19:22 Riccardo Magliocchetti wrote: Il 20/10/2010 01:48, Laurent Pinchart ha scritto: well, i've found that it's working fine out the box, it's actually a call to luvcview -L -d /dev/video1 that breaks it. I'm very surprised by that. luvcview -L doesn't modify the hardware state. Maybe only the first stream attempt succeeds ? Could you try running luvcview -d /dev/Video1 multiple times in a row ? You are right, the first time luvcview -d /dev/video1 works fine, the second it does not. So the hardware probably crashes when the stream is stopped. Bad hardware :-( This will be a bit hard to debug. We need to find out what makes the hardware crash. It's probably a command send by the driver when stopping the stream, or the lack of an expected command before restarting the stream. The easiest way I can think of to try and debug the problem would be to capture a USB trace when using the camera under Windows. Do you feel confident enough to try that ? Unfortunately I don't have a windows machine at hand, at work i have only mac os x machines. Are them any useful? thanks, riccardo ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Hi, 2010/11/19 Laurent Pinchart laurent.pinch...@ideasonboard.com: Hi Neil, On Thursday 18 November 2010 16:00:00 Paulo Assis wrote: Neil Hi, Could you please post the relevant dmesg output. Increasing uvcvideo verbosity would also be a good help. --- snip --- libv4lconvert: warning more framesizes then I can handle! libv4lconvert: warning more framesizes then I can handle! --- snip --- No problem with this, libv4l only handles a limit number of resolutions when enumerating video formats (apparently the limit is rather low for the current uvc camera models). Just out of curiosity, do you get the same warning when the camera is plugged into a USB 2.0 port ? This as been reported before: http://www.mail-archive.com/linux-me...@vger.kernel.org/msg19535.html and it should be fixed in the latest libv4l, but older versions will still have a 16 frame size limit. Best Regards, Paulo ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] sanyo cg10
Hi Riccardo, On Friday 19 November 2010 09:07:40 Riccardo Magliocchetti wrote: Il 19/11/2010 01:28, Laurent Pinchart ha scritto: On Monday 01 November 2010 12:01:50 Riccardo Magliocchetti wrote: Il 30/10/2010 20:58, Laurent Pinchart ha scritto: On Friday 22 October 2010 21:19:22 Riccardo Magliocchetti wrote: Il 20/10/2010 01:48, Laurent Pinchart ha scritto: well, i've found that it's working fine out the box, it's actually a call to luvcview -L -d /dev/video1 that breaks it. I'm very surprised by that. luvcview -L doesn't modify the hardware state. Maybe only the first stream attempt succeeds ? Could you try running luvcview -d /dev/Video1 multiple times in a row ? You are right, the first time luvcview -d /dev/video1 works fine, the second it does not. So the hardware probably crashes when the stream is stopped. Bad hardware :-( This will be a bit hard to debug. We need to find out what makes the hardware crash. It's probably a command send by the driver when stopping the stream, or the lack of an expected command before restarting the stream. The easiest way I can think of to try and debug the problem would be to capture a USB trace when using the camera under Windows. Do you feel confident enough to try that ? Unfortunately I don't have a windows machine at hand, at work i have only mac os x machines. It's becoming increasingly difficult to find Windows boxes ;-) Are them any useful? If the camcorder works correctly under Mac OS X, yes. I don't know of any USB sniffer for Mac though. -- Regards, Laurent Pinchart ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Update for supported devices list
Resending in archive due to mail-list restriction on message size. On Fri, Nov 19, 2010 at 14:24, Marat Buharov marat.buha...@gmail.com wrote: Attached to this message. On Fri, Nov 19, 2010 at 02:16, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Marat, On Wednesday 03 November 2010 08:34:26 Marat Buharov wrote: Device ID: 046d:0819 Name: Logitech Webcam C210 Manufacturer: Logitech Status: Device works Thanks for the report. Could you please send me the output of lsusb -v -d 046d:0819 Thanks. -- Regards, Laurent Pinchart lsusb_046d_0819.tar.lzma Description: Binary data ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Where have the patches from SVN gone?
Hi Laurent, On Fri, Nov 19, 2010 at 01:19:39 +0100, Laurent Pinchart wrote: The SVN repository has been taken offline as it had been deprecated for years. I confess I forgot about the patches :-) That's what I thought. Luckily that patch is quite widespread. Do you think it would be worth it making the 3 patches available again somewhere ? xawtv and tvtime are pretty much unmaintained, and mythtv seems to have been fixed. The tvtime packages are still being maintained by the distros' packagers. Indeed, they're fixing stuff and porting from OSS to ALSA mixers and the likes, so the program seems to be popular enough. I don't know if you still need to centrally provide that patch. It's not a bad idea, I guess. Apart from that, it's both in Mandriva and OpenSuSE, and you can now find it in the RedHat/Fedora bug database: https://bugzilla.redhat.com/show_bug.cgi?id=655038 as I have taken the liberty to file a ticket. Thanks, Moritz ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
snip No problem with this, libv4l only handles a limit number of resolutions when enumerating video formats (apparently the limit is rather low for the current uvc camera models). Just out of curiosity, do you get the same warning when the camera is plugged into a USB 2.0 port ? No it works fine on a USB2.0 port with both cameras libv4l2: error turning on stream: Invalid argument Unable to start capture: Invalid argument This seems to be the problem, but you need to check dmesg for the cause of the invalid argument error. Most likely this is related to the usb core and not to the driver itself, but it's hard to say without more info. Could you please increase the driver verbosity (65535 is fine) and post the messages printed to the kernel log by the driver when you try to run luvcview ? On it now -- Regards, Laurent Pinchart ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
snip This as been reported before: http://www.mail-archive.com/linux-me...@vger.kernel.org/msg19535.html and it should be fixed in the latest libv4l, but older versions will still have a 16 frame size limit. However this is just a warning though? From what I understand, the camera will still operate - is that true? Best Regards, Paulo ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Hi, 2010/11/19 Neil Benn neil.b...@gmail.com: snip This as been reported before: http://www.mail-archive.com/linux-me...@vger.kernel.org/msg19535.html and it should be fixed in the latest libv4l, but older versions will still have a 16 frame size limit. However this is just a warning though? From what I understand, the camera will still operate - is that true? Yes, I had the same warning with older libv4l versions and everything worked fine. Regards, Paulo Best Regards, Paulo ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
On Friday 19 November 2010 15:53:24 Paulo Assis wrote: Hi, 2010/11/19 Neil Benn neil.b...@gmail.com: snip This as been reported before: http://www.mail-archive.com/linux-me...@vger.kernel.org/msg19535.html and it should be fixed in the latest libv4l, but older versions will still have a 16 frame size limit. However this is just a warning though? From what I understand, the camera will still operate - is that true? Yes, I had the same warning with older libv4l versions and everything worked fine. What surprises me is that the warning only appears when the camera is plugged in a USB 3.0 port. Neil, could you please send me the output of 'lsusb -v -d 046d:0825' for both the USB 2.0 and USB 3.0 ports ? -- Regards, Laurent Pinchart ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Hello, Here is the output: USB2 port dmesg (trace 65535) [ 368.667150] usb 1-4: new high speed USB device using ehci_hcd and address 5 [ 369.015422] uvcvideo: Probing generic UVC device 4 [ 369.015435] uvcvideo: Found format YUV 4:2:2 (YUYV). [ 369.015440] uvcvideo: - 640x480 (30.0 fps) [ 369.015444] uvcvideo: - 160x120 (30.0 fps) [ 369.015447] uvcvideo: - 176x144 (30.0 fps) [ 369.015450] uvcvideo: - 320x176 (30.0 fps) [ 369.015454] uvcvideo: - 320x240 (30.0 fps) [ 369.015457] uvcvideo: - 352x288 (30.0 fps) [ 369.015461] uvcvideo: - 432x240 (30.0 fps) [ 369.015464] uvcvideo: - 544x288 (30.0 fps) [ 369.015468] uvcvideo: - 640x360 (30.0 fps) [ 369.015471] uvcvideo: - 752x416 (25.0 fps) [ 369.015475] uvcvideo: - 800x448 (25.0 fps) [ 369.015479] uvcvideo: - 800x600 (20.0 fps) [ 369.015482] uvcvideo: - 864x480 (20.0 fps) [ 369.015486] uvcvideo: - 960x544 (15.0 fps) [ 369.015490] uvcvideo: - 960x720 (10.0 fps) [ 369.015493] uvcvideo: - 1024x576 (10.0 fps) [ 369.015497] uvcvideo: - 1184x656 (10.0 fps) [ 369.015501] uvcvideo: - 1280x720 (10.0 fps) [ 369.015504] uvcvideo: - 1280x960 (5.0 fps) [ 369.015508] uvcvideo: Found format MJPEG. [ 369.015511] uvcvideo: - 640x480 (30.0 fps) [ 369.015515] uvcvideo: - 160x120 (30.0 fps) [ 369.015519] uvcvideo: - 176x144 (30.0 fps) [ 369.015522] uvcvideo: - 320x176 (30.0 fps) [ 369.015526] uvcvideo: - 320x240 (30.0 fps) [ 369.015530] uvcvideo: - 352x288 (30.0 fps) [ 369.015533] uvcvideo: - 432x240 (30.0 fps) [ 369.015536] uvcvideo: - 544x288 (30.0 fps) [ 369.015540] uvcvideo: - 640x360 (30.0 fps) [ 369.015543] uvcvideo: - 752x416 (30.0 fps) [ 369.015546] uvcvideo: - 800x448 (30.0 fps) [ 369.015549] uvcvideo: - 800x600 (30.0 fps) [ 369.015553] uvcvideo: - 864x480 (30.0 fps) [ 369.015556] uvcvideo: - 960x544 (30.0 fps) [ 369.015559] uvcvideo: - 960x720 (30.0 fps) [ 369.015563] uvcvideo: - 1024x576 (30.0 fps) [ 369.015567] uvcvideo: - 1184x656 (30.0 fps) [ 369.015570] uvcvideo: - 1280x720 (30.0 fps) [ 369.015573] uvcvideo: - 1280x960 (30.0 fps) [ 369.015582] uvcvideo: Found a Status endpoint (addr 87). [ 369.015586] uvcvideo: Found UVC 1.00 device unnamed (046d:0825) [ 369.015595] uvcvideo: Added control ----0101/2 to device 4 entity 2 [ 369.015600] uvcvideo: Added control ----0101/3 to device 4 entity 2 [ 369.015605] uvcvideo: Added control ----0101/7 to device 4 entity 2 [ 369.015610] uvcvideo: Added control ----0101/8 to device 4 entity 2 [ 369.015615] uvcvideo: Added control ----0101/10 to device 4 entity 2 [ 369.015620] uvcvideo: Added control ----0101/1 to device 4 entity 2 [ 369.015625] uvcvideo: Added control ----0101/4 to device 4 entity 2 [ 369.015630] uvcvideo: Added control ----0101/5 to device 4 entity 2 [ 369.015635] uvcvideo: Added control ----0101/11 to device 4 entity 2 [ 369.015643] uvcvideo: Added control ----0001/2 to device 4 entity 1 [ 369.015648] uvcvideo: Added control ----0001/3 to device 4 entity 1 [ 369.015653] uvcvideo: Added control ----0001/4 to device 4 entity 1 [ 369.015662] uvcvideo: Scanning UVC chain: OT 5 - XU 4 (- XU 6 XU 7) - PU 2 (- XU 3) - IT 1 [ 369.015678] uvcvideo: Found a valid video chain (1 - 5). [ 369.112136] input: UVC Camera (046d:0825) as /devices/pci:00/:00:1a.7/usb1/1-4/1-4:1.0/input/input7 [ 369.112203] uvcvideo: UVC device initialized. [ 369.114019] uvcvideo: uvc_v4l2_open [ 369.114047] uvcvideo: uvc_v4l2_ioctl(VIDIOC_QUERYCAP) [ 369.114104] uvcvideo: uvc_v4l2_release [ 370.107636] 5:3:1: cannot set freq 16000 to ep 0x86 [ 371.104246] 5:3:2: cannot set freq 24000 to ep 0x86 [ 372.101253] 5:3:3: cannot set freq 32000 to ep 0x86 [ 373.098400] 5:3:4: cannot set freq 48000 to ep 0x86 USB2 port - entry in /var/log/kernel.log Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 820.926845] usb 1-4: new high speed USB device using ehci_hcd and address 6 Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275363] uvcvideo: Probing generic UVC device 4 Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275376] uvcvideo: Found format YUV 4:2:2 (YUYV). Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275380] uvcvideo: - 640x480 (30.0 fps) Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275384] uvcvideo: - 160x120 (30.0 fps) Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275388] uvcvideo: - 176x144 (30.0 fps) Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275391] uvcvideo: - 320x176 (30.0 fps) Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275395] uvcvideo: - 320x240 (30.0 fps) Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275399] uvcvideo: - 352x288 (30.0 fps) Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275402] uvcvideo: - 432x240 (30.0 fps) Nov 19 15:27:27
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Hello, Apologies, the framesizes warning also happens in USB2 as in USB3 - my bad apologies for that. Cheers, Neil On Fri, Nov 19, 2010 at 12:26 AM, Laurent Pinchart laurent.pinch...@ideasonboard.com wrote: Hi Neil, On Thursday 18 November 2010 16:00:00 Paulo Assis wrote: Neil Hi, Could you please post the relevant dmesg output. Increasing uvcvideo verbosity would also be a good help. --- snip --- libv4lconvert: warning more framesizes then I can handle! libv4lconvert: warning more framesizes then I can handle! --- snip --- No problem with this, libv4l only handles a limit number of resolutions when enumerating video formats (apparently the limit is rather low for the current uvc camera models). Just out of curiosity, do you get the same warning when the camera is plugged into a USB 2.0 port ? libv4l2: error turning on stream: Invalid argument Unable to start capture: Invalid argument This seems to be the problem, but you need to check dmesg for the cause of the invalid argument error. Most likely this is related to the usb core and not to the driver itself, but it's hard to say without more info. Could you please increase the driver verbosity (65535 is fine) and post the messages printed to the kernel log by the driver when you try to run luvcview ? -- Regards, Laurent Pinchart ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Actually this section is different: [ 541.295541] xhci_hcd :03:00.0: WARN: short transfer on control ep [ 541.298560] xhci_hcd :03:00.0: WARN: short transfer on control ep [ 541.299468] usb 17-3: ep 0x87 - rounding interval to 128 microframes There was already some reports on linux-usb for similar issues with usb3 and uvc: http://www.spinics.net/lists/linux-usb/msg38205.html Best Regards, Paulo 2010/11/19 Neil Benn neil.b...@gmail.com: Hello, Here is more output; we diffed the files and they seem the same however. Cheers, Neil On Fri, Nov 19, 2010 at 3:32 PM, Neil Benn neil.b...@gmail.com wrote: Hello, Here is the output: USB2 port dmesg (trace 65535) [ 368.667150] usb 1-4: new high speed USB device using ehci_hcd and address 5 [ 369.015422] uvcvideo: Probing generic UVC device 4 [ 369.015435] uvcvideo: Found format YUV 4:2:2 (YUYV). [ 369.015440] uvcvideo: - 640x480 (30.0 fps) [ 369.015444] uvcvideo: - 160x120 (30.0 fps) [ 369.015447] uvcvideo: - 176x144 (30.0 fps) [ 369.015450] uvcvideo: - 320x176 (30.0 fps) [ 369.015454] uvcvideo: - 320x240 (30.0 fps) [ 369.015457] uvcvideo: - 352x288 (30.0 fps) [ 369.015461] uvcvideo: - 432x240 (30.0 fps) [ 369.015464] uvcvideo: - 544x288 (30.0 fps) [ 369.015468] uvcvideo: - 640x360 (30.0 fps) [ 369.015471] uvcvideo: - 752x416 (25.0 fps) [ 369.015475] uvcvideo: - 800x448 (25.0 fps) [ 369.015479] uvcvideo: - 800x600 (20.0 fps) [ 369.015482] uvcvideo: - 864x480 (20.0 fps) [ 369.015486] uvcvideo: - 960x544 (15.0 fps) [ 369.015490] uvcvideo: - 960x720 (10.0 fps) [ 369.015493] uvcvideo: - 1024x576 (10.0 fps) [ 369.015497] uvcvideo: - 1184x656 (10.0 fps) [ 369.015501] uvcvideo: - 1280x720 (10.0 fps) [ 369.015504] uvcvideo: - 1280x960 (5.0 fps) [ 369.015508] uvcvideo: Found format MJPEG. [ 369.015511] uvcvideo: - 640x480 (30.0 fps) [ 369.015515] uvcvideo: - 160x120 (30.0 fps) [ 369.015519] uvcvideo: - 176x144 (30.0 fps) [ 369.015522] uvcvideo: - 320x176 (30.0 fps) [ 369.015526] uvcvideo: - 320x240 (30.0 fps) [ 369.015530] uvcvideo: - 352x288 (30.0 fps) [ 369.015533] uvcvideo: - 432x240 (30.0 fps) [ 369.015536] uvcvideo: - 544x288 (30.0 fps) [ 369.015540] uvcvideo: - 640x360 (30.0 fps) [ 369.015543] uvcvideo: - 752x416 (30.0 fps) [ 369.015546] uvcvideo: - 800x448 (30.0 fps) [ 369.015549] uvcvideo: - 800x600 (30.0 fps) [ 369.015553] uvcvideo: - 864x480 (30.0 fps) [ 369.015556] uvcvideo: - 960x544 (30.0 fps) [ 369.015559] uvcvideo: - 960x720 (30.0 fps) [ 369.015563] uvcvideo: - 1024x576 (30.0 fps) [ 369.015567] uvcvideo: - 1184x656 (30.0 fps) [ 369.015570] uvcvideo: - 1280x720 (30.0 fps) [ 369.015573] uvcvideo: - 1280x960 (30.0 fps) [ 369.015582] uvcvideo: Found a Status endpoint (addr 87). [ 369.015586] uvcvideo: Found UVC 1.00 device unnamed (046d:0825) [ 369.015595] uvcvideo: Added control ----0101/2 to device 4 entity 2 [ 369.015600] uvcvideo: Added control ----0101/3 to device 4 entity 2 [ 369.015605] uvcvideo: Added control ----0101/7 to device 4 entity 2 [ 369.015610] uvcvideo: Added control ----0101/8 to device 4 entity 2 [ 369.015615] uvcvideo: Added control ----0101/10 to device 4 entity 2 [ 369.015620] uvcvideo: Added control ----0101/1 to device 4 entity 2 [ 369.015625] uvcvideo: Added control ----0101/4 to device 4 entity 2 [ 369.015630] uvcvideo: Added control ----0101/5 to device 4 entity 2 [ 369.015635] uvcvideo: Added control ----0101/11 to device 4 entity 2 [ 369.015643] uvcvideo: Added control ----0001/2 to device 4 entity 1 [ 369.015648] uvcvideo: Added control ----0001/3 to device 4 entity 1 [ 369.015653] uvcvideo: Added control ----0001/4 to device 4 entity 1 [ 369.015662] uvcvideo: Scanning UVC chain: OT 5 - XU 4 (- XU 6 XU 7) - PU 2 (- XU 3) - IT 1 [ 369.015678] uvcvideo: Found a valid video chain (1 - 5). [ 369.112136] input: UVC Camera (046d:0825) as /devices/pci:00/:00:1a.7/usb1/1-4/1-4:1.0/input/input7 [ 369.112203] uvcvideo: UVC device initialized. [ 369.114019] uvcvideo: uvc_v4l2_open [ 369.114047] uvcvideo: uvc_v4l2_ioctl(VIDIOC_QUERYCAP) [ 369.114104] uvcvideo: uvc_v4l2_release [ 370.107636] 5:3:1: cannot set freq 16000 to ep 0x86 [ 371.104246] 5:3:2: cannot set freq 24000 to ep 0x86 [ 372.101253] 5:3:3: cannot set freq 32000 to ep 0x86 [ 373.098400] 5:3:4: cannot set freq 48000 to ep 0x86 USB2 port - entry in /var/log/kernel.log Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 820.926845] usb 1-4: new high speed USB device using ehci_hcd and address 6 Nov 19 15:27:27 tim-H55N-USB3 kernel: [ 821.275363] uvcvideo: Probing
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Hello, Thanks for that; I'll ask on the linux usb group too. If I get anything of interest I'll report back here. Cheers, Neil On Fri, Nov 19, 2010 at 4:09 PM, Paulo Assis pj.as...@gmail.com wrote: Actually this section is different: [ 541.295541] xhci_hcd :03:00.0: WARN: short transfer on control ep [ 541.298560] xhci_hcd :03:00.0: WARN: short transfer on control ep [ 541.299468] usb 17-3: ep 0x87 - rounding interval to 128 microframes There was already some reports on linux-usb for similar issues with usb3 and uvc: http://www.spinics.net/lists/linux-usb/msg38205.html Best Regards, Paulo 2010/11/19 Neil Benn neil.b...@gmail.com: Hello, Here is more output; we diffed the files and they seem the same however. Cheers, Neil On Fri, Nov 19, 2010 at 3:32 PM, Neil Benn neil.b...@gmail.com wrote: Hello, Here is the output: USB2 port dmesg (trace 65535) [ 368.667150] usb 1-4: new high speed USB device using ehci_hcd and address 5 [ 369.015422] uvcvideo: Probing generic UVC device 4 [ 369.015435] uvcvideo: Found format YUV 4:2:2 (YUYV). [ 369.015440] uvcvideo: - 640x480 (30.0 fps) [ 369.015444] uvcvideo: - 160x120 (30.0 fps) [ 369.015447] uvcvideo: - 176x144 (30.0 fps) [ 369.015450] uvcvideo: - 320x176 (30.0 fps) [ 369.015454] uvcvideo: - 320x240 (30.0 fps) [ 369.015457] uvcvideo: - 352x288 (30.0 fps) [ 369.015461] uvcvideo: - 432x240 (30.0 fps) [ 369.015464] uvcvideo: - 544x288 (30.0 fps) [ 369.015468] uvcvideo: - 640x360 (30.0 fps) [ 369.015471] uvcvideo: - 752x416 (25.0 fps) [ 369.015475] uvcvideo: - 800x448 (25.0 fps) [ 369.015479] uvcvideo: - 800x600 (20.0 fps) [ 369.015482] uvcvideo: - 864x480 (20.0 fps) [ 369.015486] uvcvideo: - 960x544 (15.0 fps) [ 369.015490] uvcvideo: - 960x720 (10.0 fps) [ 369.015493] uvcvideo: - 1024x576 (10.0 fps) [ 369.015497] uvcvideo: - 1184x656 (10.0 fps) [ 369.015501] uvcvideo: - 1280x720 (10.0 fps) [ 369.015504] uvcvideo: - 1280x960 (5.0 fps) [ 369.015508] uvcvideo: Found format MJPEG. [ 369.015511] uvcvideo: - 640x480 (30.0 fps) [ 369.015515] uvcvideo: - 160x120 (30.0 fps) [ 369.015519] uvcvideo: - 176x144 (30.0 fps) [ 369.015522] uvcvideo: - 320x176 (30.0 fps) [ 369.015526] uvcvideo: - 320x240 (30.0 fps) [ 369.015530] uvcvideo: - 352x288 (30.0 fps) [ 369.015533] uvcvideo: - 432x240 (30.0 fps) [ 369.015536] uvcvideo: - 544x288 (30.0 fps) [ 369.015540] uvcvideo: - 640x360 (30.0 fps) [ 369.015543] uvcvideo: - 752x416 (30.0 fps) [ 369.015546] uvcvideo: - 800x448 (30.0 fps) [ 369.015549] uvcvideo: - 800x600 (30.0 fps) [ 369.015553] uvcvideo: - 864x480 (30.0 fps) [ 369.015556] uvcvideo: - 960x544 (30.0 fps) [ 369.015559] uvcvideo: - 960x720 (30.0 fps) [ 369.015563] uvcvideo: - 1024x576 (30.0 fps) [ 369.015567] uvcvideo: - 1184x656 (30.0 fps) [ 369.015570] uvcvideo: - 1280x720 (30.0 fps) [ 369.015573] uvcvideo: - 1280x960 (30.0 fps) [ 369.015582] uvcvideo: Found a Status endpoint (addr 87). [ 369.015586] uvcvideo: Found UVC 1.00 device unnamed (046d:0825) [ 369.015595] uvcvideo: Added control ----0101/2 to device 4 entity 2 [ 369.015600] uvcvideo: Added control ----0101/3 to device 4 entity 2 [ 369.015605] uvcvideo: Added control ----0101/7 to device 4 entity 2 [ 369.015610] uvcvideo: Added control ----0101/8 to device 4 entity 2 [ 369.015615] uvcvideo: Added control ----0101/10 to device 4 entity 2 [ 369.015620] uvcvideo: Added control ----0101/1 to device 4 entity 2 [ 369.015625] uvcvideo: Added control ----0101/4 to device 4 entity 2 [ 369.015630] uvcvideo: Added control ----0101/5 to device 4 entity 2 [ 369.015635] uvcvideo: Added control ----0101/11 to device 4 entity 2 [ 369.015643] uvcvideo: Added control ----0001/2 to device 4 entity 1 [ 369.015648] uvcvideo: Added control ----0001/3 to device 4 entity 1 [ 369.015653] uvcvideo: Added control ----0001/4 to device 4 entity 1 [ 369.015662] uvcvideo: Scanning UVC chain: OT 5 - XU 4 (- XU 6 XU 7) - PU 2 (- XU 3) - IT 1 [ 369.015678] uvcvideo: Found a valid video chain (1 - 5). [ 369.112136] input: UVC Camera (046d:0825) as /devices/pci:00/:00:1a.7/usb1/1-4/1-4:1.0/input/input7 [ 369.112203] uvcvideo: UVC device initialized. [ 369.114019] uvcvideo: uvc_v4l2_open [ 369.114047] uvcvideo: uvc_v4l2_ioctl(VIDIOC_QUERYCAP) [ 369.114104] uvcvideo: uvc_v4l2_release [ 370.107636] 5:3:1: cannot set freq 16000 to ep 0x86 [ 371.104246] 5:3:2: cannot set freq 24000 to ep 0x86 [ 372.101253] 5:3:3: cannot set freq 32000 to ep 0x86 [ 373.098400] 5:3:4: cannot set freq 48000 to ep 0x86 USB2 port -
Re: [Linux-uvc-devel] Trying to use a camera plugged into a USB3 socket
Hi Neil, On Friday 19 November 2010 17:17:59 Neil Benn wrote: Hello, Thanks for that; I'll ask on the linux usb group too. If I get anything of interest I'll report back here. It indeed looks like a problem at USB core. The usb_submit_urb() call in uvc_init_video() fails for some reason with a -EINVAL error code. You could try tracing inside the function to see what causes the failure. -- Regards, Laurent Pinchart ___ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
