From: Jean-Francois Moine <moinejf@free.fr>
To: <luca.risolia@studio.unibo.it>
Cc: Sylwester Nawrocki <snjw23@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [RFC] JPEG encoders control class
Date: Tue, 29 Nov 2011 18:53:36 +0100 [thread overview]
Message-ID: <20111129185336.31543872@tele> (raw)
In-Reply-To: <4ED3D77C.2020109@studio.unibo.it>
On Mon, 28 Nov 2011 19:48:28 +0100
Luca Risolia <luca.risolia@studio.unibo.it> wrote:
> > Note that et61x251 and sn9c102 are going to be deprecated and removed at some
> > time in the future (gspca will support these devices).
>
> Has this been discussed yet? Also, last time I tried the gspca driver
> with a number of V4L2-compliant applications, it did not support at all
> or work well for all the sn9c1xx-based devices I have here, which are
> both controllers and sensors the manufacturer sent to me when developing
> the driver with their collaboration. I also don't understand why the
> gspca driver has been accepted in the mainline kernel in the first
> place, despite the fact the sn9c1xx has been present in the kernel since
> long time and already supported many devices at the time the gspca was
> submitted. Maybe it's better to remove the duplicate code form the gspca
> driver and add the different parts (if any) to the sn9c1xx.
Hi Luca,
Removing the sn9c102 is on the way for a long time. I think we were just
waiting for a message from you!
Why is gspca in the kernel? Because of its design: all the system / v4l2
interface are in the main driver, while the subdrivers only deal with
the specific device exchanges. This simplifies development and
maintenance.
At the beginning, the gspca did not handle the sn9c102 webcams (but
some Sonix based webcams were already handled only by gspca). From time
to time, there were users saying that their webcams did not work
correctly with the sn9c102, and that they worked better with gspca. So,
we moved their IDs to gspca.
Now, the sonixjb and sonixj subdrivers handle many more sensors than
the sn9c102 with less problems. Indeed, there are still problems, but,
as I have only 3 webcams (none with Sonix chips), I must wait for user
reports and fix them.
As you have some Sonix based webcams, and as you had contact with the
manufacturers, you should easily find if there are wrong sequences in
the gspca subdrivers and/or what could be done for a better support.
This would help...
Regards.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2011-11-29 17:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 19:46 [RFC] JPEG encoders control class Sylwester Nawrocki
2011-11-26 18:43 ` Sakari Ailus
2011-11-26 20:59 ` Sylwester Nawrocki
2011-11-28 12:20 ` Hans Verkuil
2011-11-28 12:51 ` Sylwester Nawrocki
2011-11-28 18:48 ` Luca Risolia
2011-11-29 17:53 ` Jean-Francois Moine [this message]
2011-12-27 19:43 ` [RFC/PATCHv1 0/4] JPEG codecs " Sylwester Nawrocki
2011-12-27 19:43 ` [PATCH 1/4] V4L: Add JPEG compression " Sylwester Nawrocki
2011-12-30 21:42 ` Sakari Ailus
2011-12-31 11:54 ` Sylwester Nawrocki
2011-12-27 19:43 ` [PATCH 2/4] V4L: Add the JPEG compression control class documentation Sylwester Nawrocki
2011-12-27 19:43 ` [PATCH 3/4] gspca: sonixj: Add V4L2_CID_JPEG_COMPRESSION_QUALITY control support Sylwester Nawrocki
2011-12-27 19:43 ` [PATCH 4/4] gspca: zc3xx: " Sylwester Nawrocki
2012-01-06 18:14 ` [PATCH/RFC v2 0/4] JPEG codecs control class Sylwester Nawrocki
2012-01-06 18:14 ` [PATCH/RFC v2 1/4] V4L: Add JPEG compression " Sylwester Nawrocki
2012-01-06 18:14 ` [PATCH/RFC v2 2/4] V4L: Add JPEG compression control class documentation Sylwester Nawrocki
2012-01-06 18:14 ` [PATCH/RFC v2 3/4] gspca: sonixj: Add V4L2_CID_JPEG_COMPRESSION_QUALITY control support Sylwester Nawrocki
2012-01-14 8:47 ` Jean-Francois Moine
2012-01-14 17:42 ` Sylwester Nawrocki
2012-01-14 18:24 ` Jean-Francois Moine
2012-01-14 19:35 ` [PATCH/RFC v3 0/3] JPEG codecs control class Sylwester Nawrocki
2012-01-14 19:35 ` [PATCH/RFC v3 1/3] V4L: Add JPEG compression " Sylwester Nawrocki
2012-01-14 19:35 ` [PATCH/RFC v3 2/3] V4L: Add JPEG compression control class documentation Sylwester Nawrocki
2012-01-14 19:35 ` [PATCH/RFC v3 3/3] gspca: zc3xx: Add V4L2_CID_JPEG_COMPRESSION_QUALITY control support Sylwester Nawrocki
2012-01-14 19:53 ` [PATCH/RFC v4 " Sylwester Nawrocki
2012-01-21 14:45 ` Sylwester Nawrocki
2012-01-25 11:49 ` Jean-Francois Moine
2012-01-14 20:07 ` [PATCH/RFC v2 3/4] gspca: sonixj: " Sylwester Nawrocki
2012-01-06 18:14 ` [PATCH/RFC v2 4/4] gspca: zc3xx: " Sylwester Nawrocki
2012-01-14 8:47 ` Jean-Francois Moine
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=20111129185336.31543872@tele \
--to=moinejf@free.fr \
--cc=linux-media@vger.kernel.org \
--cc=luca.risolia@studio.unibo.it \
--cc=snjw23@gmail.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;
as well as URLs for NNTP newsgroup(s).