From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Thomas Kaiser <linux-dvb@kaiser-linux.li>
Cc: Video 4 Linux <video4linux-list@redhat.com>
Subject: Re: gspca, what do I am wrong?
Date: Sat, 25 Oct 2008 10:38:39 +0200 [thread overview]
Message-ID: <4902DB0F.4000401@hhs.nl> (raw)
In-Reply-To: <49021251.8020402@kaiser-linux.li>
Thomas Kaiser wrote:
> Hello Jean-Francois
>
> I got some time and I would like to test the new gspca V2 v4l2 driver
> but with this issues I will get up soon :-(
>
> I have about 20 webcams laying around which I would like to test with
> the new gspca V2 "in kernel" drive with a "stock distribution (Ubuntu)"
> kernel.
>
Please don't give up we would really like to have you onboard, you did a greta
job with the gspcav1 pixart drivers and I'm sure you will make a valuable
contributor!
The problem is that gspca now is part of the v4l-dvb tree, so when you build it
now you rebuild the entire v4l subsystem really, this means that you must make
sure that all v4l modules, including videodev.ko are unloaded before trying to
modprobe for example gspca_pac207, so that the new version of videodev.ko gets
loaded.
This has been working fine for me both with older and newer kernels (on
Fedora), so if you are really sure no old modules are loaded, it might be there
is something funny / weird going on with the way your distribution provides
kernel sources for building out of tree modules (as Thierry hints at).
To give you an idea, here is how I test gspca:
--- begin test.sh ---
#!/bin/bash
set -e
make
sudo make install
sudo rmmod gspca_sonixb || :
sudo rmmod gspca_spca501 || :
sudo rmmod gspca_spca561 || :
sudo rmmod gspca_pac207 || :
sudo rmmod gspca_pac7311 || :
sudo rmmod gspca_ov519 || :
sudo rmmod gspca_zc3xx || :
sudo rmmod gspca_main || :
sudo rmmod tuner || :
sudo rmmod msp3400 || :
sudo rmmod bttv || :
sudo rmmod compat_ioctl32 || :
sudo rmmod videodev || :
sudo rmmod v4l1_compat || :
sudo rmmod ir_common || :
sudo modprobe gspca_main debug=15
sudo modprobe gspca_sonixb
sudo modprobe gspca_spca501
sudo modprobe gspca_spca561
sudo modprobe gspca_pac207
sudo modprobe gspca_pac7311
sudo modprobe gspca_ov519
sudo modprobe gspca_zc3xx
sudo modprobe bttv
--- end test.sh ---
Regards,
Hans
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-10-25 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 20:11 gspca, what do I am wrong? Thomas Kaiser
2008-10-23 21:33 ` Thierry Merle
2008-10-23 22:56 ` Thomas Kaiser
2008-10-24 19:07 ` Thierry Merle
2008-10-24 7:01 ` Jean-Francois Moine
2008-10-24 18:22 ` Thomas Kaiser
2008-10-25 8:38 ` Hans de Goede [this message]
2008-10-30 17:34 ` Thomas Kaiser
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=4902DB0F.4000401@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=linux-dvb@kaiser-linux.li \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox