From: Thierry Merle <thierry.merle@free.fr>
To: Linux and Kernel Video <video4linux-list@redhat.com>,
Jean-Francois Moine <moinejf@free.fr>,
Hans de Goede <j.w.r.degoede@hhs.nl>
Subject: [RFC] webcam sensor module
Date: Sat, 19 Jul 2008 10:08:09 +0200 [thread overview]
Message-ID: <4881A0E9.70607@free.fr> (raw)
Hello all,
While analyzing the w9968cf v4l1 module, I saw that my webcam commands a OV7620 sensor. This sensor has a specific module: ovcamchip (v4l1).
My webcam is a Creative Webcam Go Plus.
In gspca, the zc3xx driver addresses the same sensor, but in only one module containing USB bridge controls and sensor controls.
My question is: why gspca does not use the same infrastructure? I mean 1 module for the USB bridge (like w9968cf) and 1 module for the sensor (like ovcamchip).
My first thought was to re-write w9968cf in the gspca frame but I wanted to keep this modular way of life.
>From a high-level point of view it is similar to analog TV tuners: we have a modular separation between USB bridges (like usbvision) and video decoders (like saa7115).
During my vacation I will analyse a bit further if the gspca infrastructure can be improved to integrate the modular sensor model since it can save some code.
The final aim is to make the w9968cf compatible with the v4l2 decompression library (v4l2-apps/lib/libv4l) that requires that the driver shall be v4l2 compliant.
Cheers,
Thierry
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-07-19 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 8:08 Thierry Merle [this message]
2008-07-19 9:21 ` [RFC] webcam sensor module Hans de Goede
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=4881A0E9.70607@free.fr \
--to=thierry.merle@free.fr \
--cc=j.w.r.degoede@hhs.nl \
--cc=moinejf@free.fr \
--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