BTW: now that the patch has been submitted, will appropriate updates
also be made to the corresponding issue in bugzilla?
https://bugzilla.kernel.org/show_bug.cgi?id=44191
There's also an Ubuntu launchpad bug tied to this kernel bug report.
The original patch already fell by the wayside,
On 07/17/2012 10:47 PM, Alan Stern wrote:
On Tue, 17 Jul 2012, Laurent Pinchart wrote:
Alan, what do you think about this approach ? I'm not sure whether we need to
include the early UVC models that advertise a vendor-specific class in the
list.
The general approach is okay. The details
On 07/15/2012 08:21 PM, Laurent Pinchart wrote:
On Thursday 12 July 2012 16:05:47 Eric Ding wrote:
So... now what, then? Who decides which is the better of two evils:
obvious code duplication vs. layering violation? FWIW, it does seem
like the number of Logitech webcams which aren't
On 07/09/2012 10:17 PM, Alan Stern wrote:
On Sun, 8 Jul 2012, Jonathan Nieder wrote:
Eric Ding wrote:
So it looks like you'd have to both look for USB_CLASS_VIDEO and check
uvc_ids[] too... which becomes somewhat hairy, since I assume you don't
realy want usb_detect_quirks() to reference
On 07/08/2012 02:52 PM, Oleksij Rempel (fishor) wrote:
Hi, can you please do one more test.
Try to reproduce it with MJPEG stream. Use this command:
luvcview -f jpg -C
it will force jpeg (i think your cam support it) and store each frame
separately. If you can reproduce it, please send me
On 07/09/2012 08:38 AM, Alan Stern wrote:
On Sun, 8 Jul 2012, Laurent Pinchart wrote:
this quirks also affect snd_usb_audio module. If for some reasons
uvcvideo is not loaded, snd_usb_audio will fail - i mean haw mysterious
sound problems.
Good point. If we load the uvcvideo driver while
On 07/07/2012 06:09 PM, Oleksij Rempel wrote:
On 07.07.2012 11:20, Eric Ding wrote:
On 07/06/2012 11:47 PM, Alan Stern wrote:
On Fri, 6 Jul 2012, Alan Cox wrote:
Yes, but we still need to know the reason why. Neither Rafael nor I
has been able to figure out why that commit messed things up
On 07/08/2012 09:52 AM, Alan Stern wrote:
On Sat, 7 Jul 2012, Rafael J. Wysocki wrote:
Well, the quirk does make sense. What doesn't make sense is why moving
the runtime PM operation pointers from usb_bus_type to usb_device_type
should cause any change in the autosuspend behavior. That's
On 07/08/2012 03:18 AM, Alan Stern wrote:
Apparently the behavior before commit e1620d5 was that the webcam
didn't get suspended, and after the commit it did. Unfortunately
the usbmon traces do not explain this difference; all they show is
when/whether a suspend took place.
For example,
