public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea De Marsi <andrea.demarsi@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: EM28xx based device support
Date: Mon, 27 Jun 2011 17:40:19 +0200	[thread overview]
Message-ID: <4E08A463.2050101@gmail.com> (raw)

Dear all,

I recently tried to have a wireless microscope working with the em28xx 
driver; the device is the following:

http://www.cosview.com/cp/html/?3.html

it is listed in the usb bus with vendor id 14c3 and product id 2301.
Looking the .inf of the MS windows driver I noticed that it seems to be 
based on a Empia em2860 chipset, therefore I modified the em28xx driver 
of the 2.6.24 linux kernel (specifically 2.6.24-28-generic linux kernel 
in a Ubuntu Hardy distribution) so that this particular vendor id and 
product id are associated to that driver (pls find patch below).

In fact this trick has worked, at least as far as the images are 
concerned (there is also a button to take picture which I will be 
working on later), and I've been able to see the images with the 
following parameters of mplayer:

mplayer -tv driver=v4l2:device=/dev/video0:norm=NTSC -vo x11 tv://

I now need to upgrade the linux kernel to a newer version (2.6.32 or 
newer); I followed the same path that was working with 2.6.24 (which is 
basically have the device recognized as an empia device) and in fact 
some images are visible but they are not stable; it seems as the new 
driver version was not capble of managing the NTSC format (in fact I 
noticed there is no more .norm field in the initialization structure).
Do you have any advice?

Thanks in advance,

Andrea


diff em28xx-modified/em28xx-cards.c em28xx-orig/em28xx-cards.c
266,283d265
<     [EM2861_BOARD_COSVIEW] = {
<         .name         = "Cosview Driver",
<         .is_em2800    = 0,
<         .vchannels    = 2,
<         .norm         = VIDEO_MODE_NTSC,
<         .tda9887_conf = TDA9887_PRESENT,
<         .has_tuner    = 1,
<         .decoder      = EM28XX_SAA7113,
<         .input           = {{
<             .type     = EM28XX_VMUX_COMPOSITE1,
<             .vmux     = SAA7115_COMPOSITE0,
<             .amux     = 1,
<         },{
<             .type     = EM28XX_VMUX_SVIDEO,
<             .vmux     = SAA7115_SVIDEO3,
<             .amux     = 1,
<         }},
<     },
295,296d276
<     { USB_DEVICE(0x2040, 0x6502), .driver_info = 
EM2880_BOARD_HAUPPAUGE_WINTV_HVR_900 },
<     { USB_DEVICE(0x14c3, 0x2301), .driver_info = EM2861_BOARD_COSVIEW },
diff em28xx-modified/em28xx.h em28xx-orig/em28xx.h
49d48
< #define EM2861_BOARD_COSVIEW            14


             reply	other threads:[~2011-06-27 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 15:40 Andrea De Marsi [this message]
2011-06-27 17:55 ` EM28xx based device support Devin Heitmueller

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=4E08A463.2050101@gmail.com \
    --to=andrea.demarsi@gmail.com \
    --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