All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Pickworth <ian@pickworth.me.uk>
To: video4linux-list@redhat.com
Subject: Re: zc3xx webcam (041e:4034 Creative Webcam Instant) stopped working some time ago (since gspca kernel integration?)
Date: Wed, 17 Dec 2008 13:41:22 +0000	[thread overview]
Message-ID: <49490182.3000507@pickworth.me.uk> (raw)
In-Reply-To: <4948F603.1070906@wakelift.de>

Timo Paulssen wrote:
> Hello,
> 
> I recently tried using my webcam, the Creative Webcam Instant (usb ID
> 041e:4034) again, but I can't get it to work any more.
> 
> When I started using this webcam, i could get it to work with the
> spca5xx driver, which I usually compiled per hand and inserted into the
> kernel. Then came gspcav1, which worked, too. But with the gspca, that
> is integrated in the kernel now (I'm using 2.6.27.9 retrieved from
> kernel.org) the webcam won't work.
> 

I'm not a developer, so can't explain what the change is, but there is a
significant change to where the webcam data gets processed which was
introduced with the move of the gspca drivers into the kernel.

Basically, you now need a user space driver library - libv4l - to do the
work. You can get the library from here:

http://people.atrpms.net/~hdegoede/libv4l-0.5.7.tar.gz

After making it, you preload it when running spcaview like this:

LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so spcaview -d /dev/video_webcam

as an example.

Regards
Ian

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-12-17 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 12:52 zc3xx webcam (041e:4034 Creative Webcam Instant) stopped working some time ago (since gspca kernel integration?) Timo Paulssen
2008-12-17 13:41 ` Ian Pickworth [this message]
2008-12-17 14:04   ` Timo Paulssen
2008-12-17 14:25     ` Ian Pickworth

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=49490182.3000507@pickworth.me.uk \
    --to=ian@pickworth.me.uk \
    --cc=video4linux-list@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.