mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: laurent.pinchart@skynet.be
Cc: linux-uvc-devel@lists.berlios.de, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: uvcvideo: Finally fix Logitech Quickcam for Notebooks Pro
Date: Tue, 6 Oct 2009 16:07:06 +0200	[thread overview]
Message-ID: <200910061607.07195.linux@rainbow-software.org> (raw)

Hello,
I have a Logitech Quickcam for Notebooks Pro camera (046d:08c3) which just 
does not work even with kernel 2.6.31 and has never worked well before.

On http://linux-uvc.berlios.de/, there are two problems listed. I want to 
really fix these two problems so the camera will just work after plugging in 
(and not disconnect). I started with problem no. 2 as this causes the camera 
not to work at all when plugged in:

usb 5-2.4: new high speed USB device using ehci_hcd and address 7
usb 5-2.4: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device <unnamed> (046d:08c3)
uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling 
workaround.
uvcvideo: Failed to query (129) UVC probe control : -110 (exp. 26).
uvcvideo: Failed to initialize the device (-5).

When I do "modprobe snd_usb_audio", then "rmmod snd_usb_audio" and 
finally "modprobe uvcvideo", it works. So it looks like snd_usb_audio does 
some initialization that allows uvcvideo to work. It didn't work at all I 
didn't have snd_usb_audio module compiled.

What was the change that supposedly broke this in 2.6.22?

-- 
Ondrej Zary

             reply	other threads:[~2009-10-06 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06 14:07 Ondrej Zary [this message]
2009-10-07 12:59 ` [PATCH] " Ondrej Zary
     [not found]   ` <561c252c0910070612v6c7f6363xbb9548f62c834fbd@mail.gmail.com>
2009-10-07 13:34     ` [Linux-uvc-devel] " Ondrej Zary
2009-10-08 23:04   ` Laurent Pinchart
2009-10-09  6:32     ` Ondrej Zary
2009-10-11 22:01       ` Laurent Pinchart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200910061607.07195.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=laurent.pinchart@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-uvc-devel@lists.berlios.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome