headers
Jesko Schwarzer | 1 Jul 2009 12:28
Picon

Newbe question: How are SOC cameras integrated ? How to connect an FPGA to the video interface ?

Hello,

we currently use an OMAP Zoom board and want to connect an FPGA board to the
video interface.
One idea is to simulate an SOC camera like the MT9V022 device, but we don't
know exacly how it is managed to from driver view.
We use a 2.6.28 kernel and managed to integrate v4l2 and the SOC devices;
but we did not get an /dev/video device ...
And then, how to get a virtual MT9V022 running ? How to select ?

Thanks in advance
/Jesko

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 1 comment |
headers
Vlastimil Labsky | 2 Jul 2009 21:11
Picon

[PATCH] Add support for WinFast DTV2000H rev. J

I updated and simplyfied patch from Zbynek Hrabovsky for recent
kernel. It enables autodetection of card, sound in analog TV , sound
in FM radio and switching between antenna and cable RF input. Radio
tuner still doesn't work, I don't even know how it works. Some guys
wrote me that FM radio works with TV tuner used instead of radio part
(symlink video0 -> radio0).

Signed-off-by: Vlastimil Labsky <vlasta.labsky <at> gmail.com>

--- a/drivers/media/video/cx88/cx88-cards.c	2009-06-10 05:05:27.000000000 +0200
+++ b/drivers/media/video/cx88/cx88-cards.c	2002-01-02 22:35:26.000000000 +0100
 <at>  <at>  -1283,6 +1283,51  <at>  <at>  static const struct cx88_board cx88_boar
 		},
 		.mpeg           = CX88_MPEG_DVB,
 	},
+	[CX88_BOARD_WINFAST_DTV2000H_J] = {
+		.name           = "WinFast DTV2000 H rev. J",
+		.tuner_type     = TUNER_PHILIPS_FMD1216ME_MK3,
+		.radio_type     = UNSET,
+		.tuner_addr     = ADDR_UNSET,
+		.radio_addr     = ADDR_UNSET,
+		.tda9887_conf   = TDA9887_PRESENT,
+		.input          = {{
+			.type   = CX88_VMUX_TELEVISION,
+			.vmux   = 0,
+			.gpio0  = 0x00017300,
+			.gpio1  = 0x00008207,
+			.gpio2	= 0x00000000,
+			.gpio3  = 0x02000000,
+		},{
(Continue reading)

Permalink | Reply | 10 comments |
headers
Devin Heitmueller | 3 Jul 2009 00:00
Gravatar

Re: [PARTIALLY SOLVED] Can't use my Pinnacle PCTV HD Pro stick - what am I doing wrong?

On Thu, Jun 25, 2009 at 10:34 AM, George Adams<g_adams27 <at> hotmail.com> wrote:
> Y'all are very kind to help - thank you.  I am indeed running Ubuntu Hardy
> (8.04.2 LTS), kernel on a quad-core Q9550 box.  I'll be happy to provide any
> other system details that may assist.  "uname -a" returns:
>
> Linux spurgeon 2.6.24-24-server #1 SMP Wed Apr 15 16:36:01 UTC 2009 i686
> GNU/Linux

George,

FYI:  The fix got merged into the mainline two days ago, so if you
update to the latest v4l-dvb code, the analog support should now be
working properly under your Ubuntu Hardy setup.

Cheers,

Devin

--

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
vasaka | 3 Jul 2009 03:05
Picon

Re: video loopback device

On Wed, Jun 3, 2009 at 1:02 AM, Stefano
Sabatini<stefano.sabatini-lala <at> poste.it> wrote:
> Hi all,
>
> I'm looking for an application/driver which let to create a
> virtual device where to send the video output of an application or of
> another video device.
>
> Typical application would be for example to capture from a webcam,
> apply some filter to it, and finally pulish it to another application
> reading from a video device.
>
> I see there are at least three distinct projects which provides a
> video for loopback device:
>
> * video4linux loopback device/vloopback:
>  http://www.lavrsen.dk/twiki/bin/view/Motion/VideoFourLinuxLoopbackDevice
>
>  Seems to be unmaintained, also if I'm not wrong it only supports
>  video4linux and not video4linux 2 API.
>
> * video4linux2 virtual device
>  http://sourceforge.net/projects/v4l2vd/
>
>  This should be the successor of vloopback, unfortunately it seem not
>  to work with linux 2.6.26:
>  https://sourceforge.net/forum/forum.php?thread_id=2897804&forum_id=579262
>
>  and also seems a little unmaintained.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Lamarque Vieira Souza | 3 Jul 2009 04:09
Picon

Re: [PATCH] Implement V4L2_CAP_STREAMING for zr364xx driver

	Hi all,

	I have noticed the patch mentioned in the subject was not included in 2.6.30. 
Do you plan to add it to 2.6.31?

Em Saturday 28 March 2009, Lamarque Vieira Souza escreveu:
> This patch implements V4L2_CAP_STREAMING for the zr364xx driver, by
> converting the driver to use videobuf.
>
> Tested with Creative PC-CAM 880.
>
> It basically:
> . implements V4L2_CAP_STREAMING using videobuf;
>
> . re-implements V4L2_CAP_READWRITE using videobuf;
>
> . copies cam->udev->product to the card field of the v4l2_capability
> struct. That gives more information to the users about the webcam;
>
> . moves the brightness setting code from before requesting a frame (in
> read_frame) to the vidioc_s_ctrl ioctl. This way the brightness code is
> executed only when the application requests a change in brightness and
> not before every frame read;
>
> . comments part of zr364xx_vidioc_try_fmt_vid_cap that says that Skype +
> libv4l do not work.
>
> This patch fixes zr364xx for applications such as mplayer,
> Kopete+libv4l and Skype+libv4l can make use of the webcam that comes
> with zr364xx chip.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Mauro Carvalho Chehab | 3 Jul 2009 08:21
Favicon

Re: eMPIA Silvercrest 2710

Hi Joel,

Em Fri, 7 Nov 2008 10:10:45 +0000
Joel Jordan <zcacjxj <at> hotmail.com> escreveu:

 
>   Has there been any work done on the eMPIA Silvercrest EM2710 (device for webcams)?

I borrowed a Silvercrest 1.3 Mpix camera, based on em2710 and mt9v011 with a
friend, at the end of a conference that happened last week. After spending some
spare time on it at the airplane while returning back home, I discovered how to
enable stream on it.

Basically, there were just a very few registers that was needing a different
initialization, plus a driver to the sensor inside.

Could you please test the latest development code and see if this works for you also?

It is at:
	http://linuxtv.org/hg/v4l-dvb

The driver is the em28xx. As the camera uses the generic vendor usb id
(eb1a:2820), you'll need to force the driver to load the proper card
parameters, by using card=71 at module probing. This can be done by calling:

	modprobe em28xx card=71

Or by adding an options line on your /etc/modprobe.conf (or the equivalent file on your machine):
	options em28xx card=71
(Continue reading)

Permalink | Reply | 703 comments |
headers
Wally | 3 Jul 2009 09:45
Picon

microscope camera eb1a:2750 eMPIA


I want to use a microscope camera with Opensuse linux.

Actually i get a green screen on mplayer and black with tiny white stripes 
on other applications. I can see that the camera response to light chnges 
here. 

The device is identified by lsusb as 
ID eb1a:2750 eMPIA Technology, Inc. ECS Elitegroup G220 integrated webcam

the em28xx kernelmodule driver are loaded and reports dmesg :

usb 5-2: new high speed USB device using ehci_hcd and address 2
usb 5-2: configuration #1 chosen from 1 choice
usb 5-2: New USB device found, idVendor=eb1a, idProduct=2750
usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Linux video capture interface: v2.00
em28xx v4l2 driver version 0.0.1 loaded
em28xx: new video device (eb1a:2750): interface 0, class 255
em28xx: device is attached to a USB 2.0 bus
em28xx #0: Alternate settings: 8
em28xx #0: Alternate setting 0, max size= 0
em28xx #0: Alternate setting 1, max size= 0
em28xx #0: Alternate setting 2, max size= 1448
em28xx #0: Alternate setting 3, max size= 2048
em28xx #0: Alternate setting 4, max size= 2304
em28xx #0: Alternate setting 5, max size= 2580
em28xx #0: Alternate setting 6, max size= 2892
em28xx #0: Alternate setting 7, max size= 3072
em28xx #0: V4L2 device registered as /dev/video0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hans de Goede | 3 Jul 2009 11:05
Picon
Favicon

Re: eMPIA Silvercrest 2710

Hi,

On 07/03/2009 08:21 AM, Mauro Carvalho Chehab wrote:
> Hi Joel,
>
> Em Fri, 7 Nov 2008 10:10:45 +0000
> Joel Jordan<zcacjxj <at> hotmail.com>  escreveu:
>
>
>>    Has there been any work done on the eMPIA Silvercrest EM2710 (device for webcams)?
>
> I borrowed a Silvercrest 1.3 Mpix camera, based on em2710 and mt9v011 with a
> friend, at the end of a conference that happened last week. After spending some
> spare time on it at the airplane while returning back home, I discovered how to
> enable stream on it.
>

My that webcam has done some interesting travelling (me -> Dough -> you), I'm glad
it finally ended at someone who has managed to get it to produce a picture under Linux.

> Basically, there were just a very few registers that was needing a different
> initialization, plus a driver to the sensor inside.
>
> Could you please test the latest development code and see if this works for you also?
>
> It is at:
> 	http://linuxtv.org/hg/v4l-dvb
>
> The driver is the em28xx. As the camera uses the generic vendor usb id
> (eb1a:2820), you'll need to force the driver to load the proper card
(Continue reading)

Permalink | Reply | 2 comments |
headers
Hugo | 3 Jul 2009 11:21

em28xx device problem since 2.6.30 kernel

Hi,

I have a  em28xx based device : Pinnacle PCTV USB 2 worked great before
kernel 2.6.30
On 2.6.30 and 2.6.31 kernel, device don't work...

dmesg :

[ 1822.572852] em28xx: New device Pinnacle Systems GmbH PCTV USB2 PAL  <at> 
480 Mbps (2304:0208, interface 0, class 0)
[ 1822.572856] em28xx #0: Identified as Pinnacle PCTV USB 2 (card=3)
[ 1822.573037] em28xx #0: chip ID is em2820
[ 1822.678037] em28xx #0: i2c eeprom 00: 1a eb 67 95 04 23 08 02 10 00
1e 03 98 1e 6a 2e
[ 1822.678049] em28xx #0: i2c eeprom 10: 00 00 06 57 6e 00 00 00 8e 00
00 00 07 00 00 00
[ 1822.678059] em28xx #0: i2c eeprom 20: 16 00 01 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 1822.678250] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 10 01
00 00 00 00 00 00
[ 1822.678261] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 1822.678271] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[ 1822.678280] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00
2e 03 50 00 69 00
[ 1822.678290] em28xx #0: i2c eeprom 70: 6e 00 6e 00 61 00 63 00 6c 00
65 00 20 00 53 00
[ 1822.678300] em28xx #0: i2c eeprom 80: 79 00 73 00 74 00 65 00 6d 00
73 00 20 00 47 00
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mauro Carvalho Chehab | 3 Jul 2009 13:00
Favicon

Re: eMPIA Silvercrest 2710

Em Fri, 03 Jul 2009 11:05:29 +0200
Hans de Goede <hdegoede <at> redhat.com> escreveu:

> My that webcam has done some interesting travelling (me -> Dough -> you), I'm glad
> it finally ended at someone who has managed to get it to produce a picture under Linux.

Yes. Thank you for borrow it!

> Hmm, having to specify the card=71 parameter, sucks, that makes this a very non plug
> and play / not just working experience for end users. Question would it be possible to
> modify the em28xx driver to, when it sees the generic usb-id, setup the i2c controller
> approriately and then check:
> 1) If there is anything at the i2c address of the mt9v011 sensor
> 2) Read a couple of identification registers (often sensors have special non changing
>     registers for this)
> 3) If both the 1 and 2 test succeed set card to 71 itself ?

The mt9v011 sensor has an unique ID, that can be read via register 0. One of the
issues is that it is using the same address as tvp5150 (that can also be
probed, since it also provides an unique ID via some register).

> This is how we handle the problem of having one generic usb-id for a certain bridge, with
> various different sensors used in different cams, I know the em28xx is a lot more complicated
> as it does a lot more, but this may still work ?

Yes, it may work. with the new i2c binding method, it would not be that hard to
do such method, but it would require some rework at em28xx-cards, since some
boards require a pre-i2c binding initialization, so board detection happens too
early inside the driver.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane