> Hi everyone,
>
> I've been using a Logitech Sphere for years on various projects. This
> model is probably from the first batch ever made. In lsusb it shows up
> as
>
> 046d:08b5 Logitech, Inc. QuickCam Sphere
>
> It's a bit troublesome, because on older kernel versions (~2.4.x,
> ~2.6.2x) I never had a single issue with this hardware at all, on
> several different platforms ranging from x86 to x86_64, to arm
> (ep93xx), etc. However, somewhere between then and now, the pwc driver
> underwent some changes rendering this device unusable in any recent
> kernel. All of my old apps and new apps (including cheese, mplayer,
> etc) simply hang indefinitely waiting to read a single frame (using
> the v4l2 mmap api). The v4l2 read api also hangs indefinitely (using
> pwcgrab). A few of the very old apps that I have also use the v4l1
> api, with a 2.4.26 kernel, and that actually works.
>
> I can verify that the hardware itself is fine on windows (also using
> very old drivers from Logitech).
>
> Who has been working on this driver? What were the major changes that
> have been applied? I'm guessing that the bridge / sensor init sequence
> has been messed up somehow. Any ideas?
You're in luck. I fixed this last weekend. It turns out that the
/dev/videoX device is created too soon and the HAL daemon starts to use it
immediately causing some initialization to go wrong or something like
that. Moving the creation of /dev/videoX to the end fixed this issue.
This bug has been there probably for a long time, but it is only triggered
if some other process opens the device node immediately.
Check out the pwc patch I posted last weekend.
Regards,
Hans
>
> Cheers,
>
> Chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Hans Verkuil - video4linux developer - sponsored by TANDBERG, part of Cisco
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
