Hi, On Monday 17 November 2008, [EMAIL PROTECTED] wrote: > 2008/11/14 <[EMAIL PROTECTED]>: > > 2008/11/12 Laurent Pinchart <[EMAIL PROTECTED]>: > >> On Tuesday 11 November 2008, [EMAIL PROTECTED] wrote: > >>> Dear Laurent and other developers of linux-uvc: > >>> > >>> I was talking with my mentor. We are interesting in: > >>> · Still Image capture: method 2 and method 3, but we don't know which > >>> camera can use method 3. > >> > >> Here's a non exhaustive list of webcams that support (or at least claim > >> to support) still capture method 2. > >> > >> 0402:5606 ALi Corp. > >> 0408:030c Quanta Computer, Inc. > >> 046d:0994 Logitech, Inc. > >> 046d:09a1 Logitech, Inc. > >> 046d:09b2 Logitech, Inc. > >> 0471:0332 Philips > >> 04f2:b016 Chicony Electronics Co., Ltd > >> 05ac:8502 Apple Computer, Inc. > >> 064e:a110 Suyin Corp. > >> 0ac8:332d Z-Star Microelectronics Corp. > >> 0ac8:3343 Z-Star Microelectronics Corp. > >> 0ad2:933d Service & Quality Technology Co., Ltd > >> 0c45:62e0 Microdia > >> 0c45:63e0 Microdia > >> 145f:013e Unknown > >> 145f:013f > >> 174f:5931 Syntek > >> 174f:5a31 > >> 174f:8a33 > >> 1871:0306 > >> 1c4f:3000 > >> 1cac:a332 > >> 1cac:b288 > >> 5986:0104 Bison > >> 5986:0200 > >> 5986:0202 Bison > >> 5986:0240 Bison > >> 5986:0300 > >> 5986:0303 Bison > >> I don't know of any camera supporting still image capture method 3. > > > > I want to know what is method 0. I think that it's when webcam hasn't > > any button => no interruption point. Is it true? > > > > I will use this list for buy a good webcam for do this work. How can I > > be the developer of "Still Image" methods? The most interesting for me > > is the method 2. > > I think that method 0, 1 and 2 can be interesting for us. But the most > interesting is method 2.
Method 1 is quite straightforward and could be used to implement the userspace interface. Methid 2 is a bit more complex and could be implemented once method 1 works. > >>> · Clock: I can see an example in documentation of UVC 1.1 (Class and > >>> FAQ) with clock reference, but it's only a unique (and duplicated) > >>> example with stream payload. > >> > >> See section 2.4.3.4 in the UVC 1.1 specification. > > > > I'll read this section in this weekend. > > In addition of delay+SCR+PTS, I see more problems of synchronization > in FAQ document at 2.12, but I have to read it more detailed. In this > part of the document, LPF and PLL are presented but I didn't know > nothing about it before. I've never said it was straightforward :-) PLL stands for Phase-Locked Loop. See http://en.wikipedia.org/wiki/PLL. > >>> · UVC stub: My mentor is thinking about have a software UVC (like > >>> mac80211 for wifi devices) that show you usb trams. It can be > >>> interesting for learning and for debugging. > >> > >> I'm not sure to understand. Could you please elaborate ? > > > > My mentor is interesting in get a "software" USB device for get the > > information of USB trams (USB controller <-> USB device). Like > > mac80211 Test Driver ( > > http://kernelnewbies.org/KernelProjects/Mac80211TestDriver ) but for > > UVC. Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
