public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: amol verule <amol.debian@gmail.com>
Cc: Denis Loginov <dinvlad@gmail.com>,
	Linux Media <linux-media@vger.kernel.org>
Subject: Re: driver for 041e:4055 Creative Technology, Ltd Live! Cam Video IM
Date: Fri, 31 Jul 2009 10:38:08 +0200	[thread overview]
Message-ID: <20090731103808.46480a31@tele> (raw)
In-Reply-To: <77ca8eab0907302124n50bb8122p128f6f6934b2faf5@mail.gmail.com>

On Fri, 31 Jul 2009 09:54:19 +0530
amol verule <amol.debian@gmail.com> wrote:

> thanks denis,
>                        after following these steps it worked me to
> detect device but not to read or get picture from device. it is
> giving error as usb 5-5: new high speed USB device using ehci_hcd and
> address 3 usb 5-5: configuration #1 chosen from 1 choice
> Linux video capture interface: v2.00
> gspca: main v2.7.0 registered
> gspca: probing 041e:4055
> zc3xx: Sensor Tas5130 (VF0250)
> gspca: probe ok
> usbcore: registered new interface driver zc3xx
> zc3xx: registered
> usb 5-5: USB disconnect, address 3
> gspca: usb_submit_urb alt 2 err -19
> gspca: disconnect complete
> gspca: open failed err -19
> gspca: open failed err -19
>                                what this error means ..i think
> problem in device driver it is not able to open device..how to
> resolve this error???
>  
> On Sun, Jul 26, 2009 at 6:34 PM, Denis Loginov <dinvlad@gmail.com>
> wrote:
> 
> > Actually, according to http://linux-uvc.berlios.de/ , you can just
> > try 'USB
> > Video Class' Driver, i.e. Device Drivers -> Multimedia Devices ->
> > Video Capture Adapters -> V4L USB Devices -> (M) USB Video Class
> > (UVC) & (y) UVC input events device support
> > (CONFIG_USB_VIDEO_CLASS=m & USB_VIDEO_CLASS_INPUT_EVDEV=y).

Hello Amol and Denis,

This webcam is not handled by gspca (it is VF0230, and not VF0250).

I already got a usbsnoop and I may say that it if not UVC compliant too.

With the usbsnoop and the register names in the V0230Dev.inf of the
ms-win driver, it should be easy to create a new driver, but:

- it seems it asks for a firmware which may be copyrighted,

- the images are compressed and the encoding is not known...

BTW, the linux video stuff is now discussed in the linux-media mailing
list (see Cc:).

Best regards.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

  reply	other threads:[~2009-07-31  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 13:04 driver for 041e:4055 Creative Technology, Ltd Live! Cam Video IM Denis Loginov
2009-07-31  4:24 ` amol verule
2009-07-31  8:38   ` Jean-Francois Moine [this message]
2009-08-01  8:11   ` Jean-Francois Moine
  -- strict thread matches above, loose matches on Subject: below --
2009-07-25 21:32 Denis Loginov
     [not found] <77ca8eab0907230657t7d284a6cqac2da26d4d80b8d4@mail.gmail.com>
2009-07-23 14:02 ` amol verule

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=20090731103808.46480a31@tele \
    --to=moinejf@free.fr \
    --cc=amol.debian@gmail.com \
    --cc=dinvlad@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /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