From: Jean-Francois Moine <moinejf@free.fr>
To: "T.P. Reitzel" <4066724035@vzwmail.net>
Cc: linux-media@vger.kernel.org
Subject: Re: gspca_spca505
Date: Tue, 20 Jan 2009 09:22:29 +0100 [thread overview]
Message-ID: <20090120092229.57d6fbfc@free.fr> (raw)
In-Reply-To: <49751737.1020101@vzwmail.net>
On Mon, 19 Jan 2009 17:13:43 -0700
"T.P. Reitzel" <4066724035@vzwmail.net> wrote:
> I just pulled mercurial's v4l-dvb for Bluewhite64's 2.6.27.7 kernel.
> This spca505 driver for Intel's PC Camera Pro, 0733:0430 isn't even
> functioning. The MMAP feature of this driver just displays a screen of
> horizontal green lines. Furthermore, M. Xhaard stripped the external
> composite feature from this driver a few years ago and no one has yet
> added it back. If you visit the original website for this driver on
> sourceforge.net, you'll see the original driver for this video camera
> including composite support. As it is, the driver for this camera is
> totally inoperative.
What do you mean by "composite support"?
Otherwise, none of the webcams of the spca505 subdriver have been
tested since the conversion from v1 to v2. I'd be glad to have more
information about what happens with this subdriver. May you read the
gspca_README.txt from my page (see below) and send me the results?
Thank you.
--
Ken ar c'hentan | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2009-01-20 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 0:13 gspca_spca505 T.P. Reitzel
2009-01-20 8:22 ` Jean-Francois Moine [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 1:38 gspca_spca505 T.P. Reitzel
2009-01-21 18:47 ` gspca_spca505 Jean-Francois Moine
2009-01-21 22:07 gspca_spca505 T.P. Reitzel
2009-01-22 12:33 ` gspca_spca505 Jean-Francois Moine
2009-01-22 18:56 gspca_spca505 T.P. Reitzel
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=20090120092229.57d6fbfc@free.fr \
--to=moinejf@free.fr \
--cc=4066724035@vzwmail.net \
--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