* EM28xx based device support
@ 2011-06-27 15:40 Andrea De Marsi
2011-06-27 17:55 ` Devin Heitmueller
0 siblings, 1 reply; 2+ messages in thread
From: Andrea De Marsi @ 2011-06-27 15:40 UTC (permalink / raw)
To: Linux Media Mailing List
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: EM28xx based device support
2011-06-27 15:40 EM28xx based device support Andrea De Marsi
@ 2011-06-27 17:55 ` Devin Heitmueller
0 siblings, 0 replies; 2+ messages in thread
From: Devin Heitmueller @ 2011-06-27 17:55 UTC (permalink / raw)
To: Andrea De Marsi; +Cc: Linux Media Mailing List
On Mon, Jun 27, 2011 at 11:40 AM, Andrea De Marsi
<andrea.demarsi@gmail.com> wrote:
> 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?
A screenshot of what you are seeing would be useful (as well as the
dmesg output showing driver load as well as after your attempt to
capture)
Also, given your device I would assume that ".has_tuner" would
probably be zero and the tda9887_conf should not be populated at all.
And does the device really have two inputs?
Devin
--
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-06-27 17:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-06-27 15:40 EM28xx based device support Andrea De Marsi
2011-06-27 17:55 ` Devin Heitmueller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox