From: MK <halfcountplus@intergate.com>
To: Theodore Kilgore <kilgota@banach.math.auburn.edu>
Cc: "Hans de Goede" <j.w.r.degoede@hhs.nl>,
"Erik Andrén" <erik.andren@gmail.com>,
video4linux-list@redhat.com, linux-media@vger.kernel.org
Subject: Re: working on webcam driver
Date: Sun, 17 May 2009 12:08:30 -0400 [thread overview]
Message-ID: <1242576510.1986.0@lhost.ldomain> (raw)
In-Reply-To: <alpine.LNX.2.00.0905141424460.11396@banach.math.auburn.edu> (from kilgota@banach.math.auburn.edu on Thu May 14 15:57:07 2009)
Thanks much for the feedback! Here's what happened:
Because the vendor id (0c45) is listed by the gspca website but not
the product (612a), I decided to try inserting the id into one of the
drivers/media/video/gspca. When I actually grepped (had not grepped
the tree itself yet), low and behold 612a is in sonixj. The module
compiles and responds to the camera, although the results in gstreamer,
et. al, are disappointing -- the camera is not really usable, I suspect
from the output it is the kernel driver, but I am not sure. Since I
didn't write this stuff, I think working alone it will be more trouble
than it is worth to track the problem down, esp. if this is mostly a
problem with an (obscure) inexpensive item that few linux users
actually possess.
So, I am going to cut my "loses" early on this project and cop out.
I've learned a bunch about the kernel and in the process written some
nifty little char drivers that are probably more useful to me than a
webcam anyway. I think my time would be better spent on other things,
eg, I might become useful in someone else's (more significant) linux
kernel/driver project. I will have a look around.
But thanks again! You were much nicer than mr Greg Kroah-Hartman ;) :0
Sincerely, Mark Eriksen (getting his feet wet)
next prev parent reply other threads:[~2009-05-17 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:45 working on webcam driver MK
2009-05-11 18:50 ` Erik Andrén
2009-05-14 16:00 ` MK
2009-05-14 17:26 ` Hans de Goede
2009-05-14 19:57 ` Theodore Kilgore
2009-05-17 16:08 ` MK [this message]
2009-05-17 22:31 ` leandro Costantino
2009-05-19 20:35 ` What is libv4lconvert/sn9c202x.c for? Theodore Kilgore
2009-05-20 18:38 ` Hans de Goede
2009-05-20 19:53 ` Theodore Kilgore
2009-05-23 22:12 ` [PATCH] to libv4lconvert, to do decompression for sn9c2028 cameras Theodore Kilgore
2009-05-24 9:49 ` Hans de Goede
2009-05-24 17:22 ` Theodore Kilgore
2009-05-24 17:32 ` Hans de Goede
2009-05-24 22:26 ` Theodore Kilgore
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=1242576510.1986.0@lhost.ldomain \
--to=halfcountplus@intergate.com \
--cc=erik.andren@gmail.com \
--cc=j.w.r.degoede@hhs.nl \
--cc=kilgota@banach.math.auburn.edu \
--cc=linux-media@vger.kernel.org \
--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