On 18:52 Sat 29 Dec 2007, George Peter Staplin wrote:
> Quoted Laurent Pinchart <[EMAIL PROTECTED]>:
>
> > Hi George,
>
> Hi Laurent,
>
> > On Saturday 29 December 2007, George Peter Staplin wrote:
> >> This is a followup to my message about the Creative VF0410 Live! Cam
> >> Video IM Pro (041e:4063)
> >>
> >> I changed the uvc_trace_param in uvc_driver.c, so that I could get
> >> more information about what is going on:
> >> unsigned int uvc_trace_param = UVC_TRACE_PROBE | UVC_TRACE_DESCR |
> >> UVC_TRACE_CONTROL | UVC_TRACE_FORMAT | UVC_TRACE_CAPTURE |
> >> UVC_TRACE_CALLS | UVC_TRACE_IOCTL | UVC_TRACE_FRAME;
> >>
> >> Now when I insmod the driver, and plug in the webcam I get:
> >>
> >> [ 2626.794551] usb 5-8: new high speed USB device using ehci_hcd and
> >> address 12
> >> [ 2626.968643] usb 5-8: configuration #1 chosen from 1 choice
> >> [ 2626.969218] uvcvideo: Probing generic UVC device 8
> >> [ 2626.969234] uvcvideo: Found format YUV 4:2:2 (YUYV).
> >> [ 2626.969239] uvcvideo: - 640x480 (30.0 fps)
> >> [ 2626.969243] uvcvideo: - 352x288 (30.0 fps)
> >> [ 2626.969247] uvcvideo: - 320x240 (30.0 fps)
> >> [ 2626.969250] uvcvideo: - 176x144 (30.0 fps)
> >> [ 2626.969253] uvcvideo: - 160x120 (30.0 fps)
> >> [ 2626.969257] uvcvideo: Found format MJPEG.
> >> [ 2626.969261] uvcvideo: - 640x480 (30.0 fps)
> >> [ 2626.969264] uvcvideo: - 352x288 (30.0 fps)
> >> [ 2626.969267] uvcvideo: - 320x240 (30.0 fps)
> >> [ 2626.969271] uvcvideo: - 176x144 (30.0 fps)
> >> [ 2626.969274] uvcvideo: - 160x120 (30.0 fps)
> >> [ 2626.969282] uvcvideo: Found a Status endpoint (addr 83).
> >> [ 2626.969286] uvcvideo: Found UVC 1.00 device VF0410 Live! Cam Video
> >> IM Pro (041e:4063)
> >> [ 2626.969296] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/2 to device 8 entity 3
> >> [ 2626.969302] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/3 to device 8 entity 3
> >> [ 2626.969309] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/6 to device 8 entity 3
> >> [ 2626.969315] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/7 to device 8 entity 3
> >> [ 2626.969322] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/8 to device 8 entity 3
> >> [ 2626.969330] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/9 to device 8 entity 3
> >> [ 2626.969339] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/1 to device 8 entity 3
> >> [ 2626.969348] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/4 to device 8 entity 3
> >> [ 2626.969357] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/5 to device 8 entity 3
> >> [ 2626.969366] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000001/2 to device 8 entity 1
> >> [ 2626.969375] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000001/4 to device 8 entity 1
> >> [ 2626.969386] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/11 to device 8 entity 3
> >> [ 2626.969395] uvcvideo: Added control
> >> 00000000-0000-0000-0000-000000000101/10 to device 8 entity 3
> >> [ 2626.969402] uvcvideo: Scanning UVC chain: OT 2 <- XU 5 <- XU 4 <-
> >> PU 3 <- IT 1
> >> [ 2626.969415] uvcvideo: Found a valid video chain (1 -> 2).
> >> [ 2626.975707] uvcvideo: UVC device initialized.
> >> [ 2627.004211] 12:3:1: cannot get freq at ep 0x84
> >>
> >> Any clue as to why 12:3:1 (what is that?) thinks the endpoint 0x84 is
> >> invalid for freq (fetching?)?
> >
> > The message is printed by the usbaudio driver. Don't worry about it.
> > usbaudio
> > has been fixed in 2.6.22 (or 2.6.23, can't remember from the top of my
> > head).
> > It shouldn't break anything anyway.
>
> Oh, I see.
>
> > Your webcam seems to be correctly detected and initialised by the
> > driver. It's
> > now time to try and use it. I suggest luvcview, uvccapture or ucview for a
> > first try. Let me know if it works.
>
> I see. lucview works. thank you :)
>
> Unfortunately some other tools fail that worked with another webcam.
> I'm finding that kopete (a KDE instant messaging program) prints this
> endlessly "read error 19, No such device"
>
> A tool called camstream also has a similar error 19.
>
> I just did an svn update to get rid of my local changes.
>
> I see: uvcvideo: uvc_v4l2_read: not implemented when using camstream
> and kopete.
>
> Does that mean that an mmap interface is the only interface supported?
Yes, UVC only implements the mmap() system call at this time.
[ I have patches that are mostly ready that convert UVC to use the
videobuf API but there are a few patches and fixes I would like to see
go in to videobuf before I ask Laurent to review my patches. The
videobuf conversion will add read() support. ]
> Or perhaps that these programs are using the old Video4Linux kernel
> API?
kopete should use v4l2 and it should really have mmap support. From
glancing at the camstream site it appears to only support v4l1.
Cheers,
Brandon
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
