From: Luca Risolia <luca.risolia@linux-projects.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [RFC PATCH 1/2] sn9c102: prepare for removal by moving it to staging.
Date: Sat, 14 Dec 2013 18:13:45 +0100 [thread overview]
Message-ID: <1628977.YDkQVgTYrx@laptop> (raw)
In-Reply-To: <1386850822-3487-2-git-send-email-hverkuil@xs4all.nl>
> From: Hans Verkuil <hans.verkuil@cisco.com>
>
> During the last media summit meeting it was decided to move this driver to
> staging as the first step to removing it altogether.
>
> Most webcams covered by this driver are now supported by gspca. Nobody has
> the hardware to convert the remaining devices to gspca.
I have all the boards given by the manufacturer. Last time I tried the gspca
driver it certainly did not work with most of the sn9c1xx-based models the
gspca driver claims to be supporting (which were a subset of the devices
actually supported by sn9c102).
> This driver needs a major overhaul to have it conform to the latest
> frameworks and compliancy tests.
What is not compliant? I will offer my help to update the driver in case but
cannot give my help to fix or test all the boards again with the gspca, as it
would be a considerable amount of extra work.
> Without hardware, however, this is next to impossible. Given the fact that
> this driver seems to be pretty much unused (it has been removed from Fedora
> several versions ago and nobody complained about that), we decided to drop
> this driver.
As no one has the hardware, what is the reason why the sn9c102 has been moved
into gspca, although the sn9c102 driver has been already present in the kernel
since years before?
In my opinion the fact that the module has been removed from Fedora does not
imply that the driver is unused. For sure that does not mean the sn9c102
driver is unuseful, since gspca does not work properly with all the devices,
as I mentioned.
Regards
Luca
next prev parent reply other threads:[~2013-12-14 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 12:20 [RFC PATCH 0/2] Move sn9c102 and omap24xx/tcm825x to staging Hans Verkuil
2013-12-12 12:20 ` [RFC PATCH 2/2] omap24xx/tcm825x: move to staging for future removal Hans Verkuil
[not found] ` <1386850822-3487-2-git-send-email-hverkuil@xs4all.nl>
2013-12-14 17:13 ` Luca Risolia [this message]
2013-12-15 11:18 ` [RFC PATCH 1/2] sn9c102: prepare for removal by moving it to staging Hans Verkuil
2013-12-15 13:55 ` Luca Risolia
2013-12-16 9:11 ` Hans Verkuil
2013-12-15 14:44 ` 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=1628977.YDkQVgTYrx@laptop \
--to=luca.risolia@linux-projects.org \
--cc=hans.verkuil@cisco.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--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