From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: linux-media@vger.kernel.org
Cc: mchehab@infradead.org, hdegoede@redhat.com
Subject: How to add support for the em2765 webcam Speedlink VAD Laplace to the kernel ?
Date: Mon, 20 Aug 2012 13:41:14 +0200 [thread overview]
Message-ID: <5032225A.9080305@googlemail.com> (raw)
Hi,
after a break of 2 1/2 kernel releases (sorry, I was busy with another
project), I would like to bring up again the question how to add support
for this device to the kernel.
See
http://www.mail-archive.com/linux-media@vger.kernel.org/msg44417.html
("Move em27xx/em28xx webcams to a gspca subdriver ?") for the previous
discussion.
Current status is, that I've reverse-engineered the Windows driver and
written a new gspca-subdriver for testing, which is feature complete and
working stable (will send a patch shortly !).
The device uses an em2765-bridge, so my first idea was of course to
modify/extend the em28xx-driver.
But during the reverse-engineering-process, it turned out that writing a
new gspca-subdriver was much easier than modifying the em28xx-driver.
The device has the following special characteristics:
- supports only bulk transfers (em28xx driver supports ISOC only)
- uses "proprietary" read/write procedures for the sensor
- uses 16bit eeprom
- em25xx-eeprom with different layout
- sensor OV2640
- different frame processing
- 3 buttons (snapshot, mute, light) which need special treatment
(GPIO-polling, status-reseting, ...)
Another important point to mention: you can see from the USB-logs
(sensor probing) that there must be at least 3 other webcam devices.
Some pros and cons for both solutions:
em28xx:
+ one driver for all 25xx/26xx/27xx/28xx devices
+ no duplicate code (bridge register defines, bridge read/write fcns)
+ other devices COULD benefit from the new functions/code
- big task/lots of work
- code gets bloated with stuff, which is only needed by a few special
devices
gspca:
+ driver already exists (see patch)
+ default driver for webcams
+ much easier to understand and extend
+ same or even less amount of new code lines
+ keeps em28xx-code "simple"
- code duplication
- support for em28xx-webcams spread over to 2 different drivers
I have no strong opinion whether support for this device should finally
be added to em28xx or gspca and
I'm willing to continue working on both solutions as much as my time
permits and as long as I'm having fun (I'm doing this as a hobby !).
Anyway, the em28xx driver is very complex and I really think it would
take several further kernel releases to get the job done...
I would also be willing to spend some time for moving the em28xx-webcam
code to a gspca subdriver, but I don't have any of these devices for
testing.
What do you think ?
Regards,
Frank Schäfer
next reply other threads:[~2012-08-20 11:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 11:41 Frank Schäfer [this message]
2012-08-20 13:02 ` How to add support for the em2765 webcam Speedlink VAD Laplace to the kernel ? Hans de Goede
2012-08-20 19:21 ` Mauro Carvalho Chehab
2012-08-20 20:46 ` Hans de Goede
2012-08-20 21:10 ` Mauro Carvalho Chehab
2012-08-21 11:35 ` Frank Schäfer
2012-08-21 12:32 ` Mauro Carvalho Chehab
2012-08-21 16:04 ` Frank Schäfer
2012-08-21 17:29 ` Mauro Carvalho Chehab
2012-08-22 7:53 ` Frank Schäfer
2012-08-22 18:15 ` Mauro Carvalho Chehab
2012-08-26 18:53 ` Frank Schäfer
2012-09-23 14:03 ` Frank Schäfer
2012-10-06 11:56 ` Mauro Carvalho Chehab
2012-10-06 14:45 ` Mauro Carvalho Chehab
2012-10-07 2:56 ` Devin Heitmueller
2012-10-07 13:53 ` Frank Schäfer
2012-10-07 13:41 ` Frank Schäfer
2012-10-07 16:08 ` Mauro Carvalho Chehab
2012-10-08 19:45 ` Frank Schäfer
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=5032225A.9080305@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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;
as well as URLs for NNTP newsgroup(s).