Introduce omap_vout_vrfb.c and omap_vout_vrfb.h, for all VRFB related API's,
making OMAP_VOUT driver independent from VRFB. This is required for OMAP4 DSS,
since OMAP4 doesn't have VRFB block.
Added new enum vout_rotation_type and "rotation_type" member to omapvideo_info,
this is initialized based
Move some inline functions from omap_vout.c to omap_voutdef.h and independent
functions like omap_vout_alloc_buffer/omap_vout_free_buffer to omap_voutlib.c.
Signed-off-by: Archit Taneja
---
drivers/media/video/omap/omap_vout.c| 109 ---
drivers/media/video/omap/o
Introduce omap_vout_vrfb.c and omap_vout_vrfb.h, for all VRFB related API's,
making OMAP_VOUT driver independent from VRFB. This is required for OMAP4 DSS,
since OMAP4 doesn't have VRFB block.
A new enum called vout_rotation_type is introduced to differentiate between no
rotation and vrfb rotation
hi, Guennadi:
thanks for your comments.
I converted it to videobuf2 and send it out in another thread.
[PATCH] V4L/DVB: v4l: Add driver for Marvell PXA910 CCIC
would you please review ? thanks
2011/5/18 Guennadi Liakhovetski :
> Hi Kassey
>
> On Wed, 18 May 2011, Ka
This driver exports a video device node per each CCIC
(CMOS Camera Interface Controller)
device contained in Marvell Mobile PXA910 SoC
The driver is based on v4l2-mem2mem framework, and only
USERPTR is supported.
Signed-off-by: Kassey Lee
---
arch/arm/mach-mmp/include/mach/camera.h | 33 +
dri
On 26/05/11 19:24, javier Martin wrote:
> On 25 May 2011 15:38, Koen Kooi wrote:
>> >
>> > Op 25 mei 2011, om 13:16 heeft Javier Martin het volgende geschreven:
>> >
>>> >> It includes several fixes pointed out by Laurent Pinchart. However,
>>> >> the BUG which shows artifacts in the image (horiz
On 05/27/2011 12:25 AM, Nicolas WILL wrote:
Just installed mine for MythTV.
Works great on the first try!
Many, many thanks!
Thank you for the feedback!
:)
It will get also remote controller support and I also changed LNA (low
noise amplifier) behind module parameter. After those patches [
Aside from the initial "hey, lets make sure we've flushed any
pre-existing data on the device" call to mce_sync_in, every other one of
the calls was entirely superfluous. Ergo, remove them all, and rename
the one and only (questionably) useful one to reflect what it really
does. Verified on both ge
There's an SMK-device-id remote kit from I-O Data avaiable primarily in
Japan, which appears to have no tx hardware, but has rx functionality
that works with the mceusb driver by simply adding its device ID.
http://www.iodata.jp/product/av/tidegi/gv-mc7rckit/
Reported-by: Jeremy Kwok
Signed-off-
Using dev_dbg is more complexity than many users are able to deal with.
Make it easier to get debug spew feedback from them by adding an mce_dbg
printk macro that spews using dev_info when debug=1 is set for the
mceusb module.
Signed-off-by: Jarod Wilson
---
drivers/media/rc/mceusb.c | 44
Just installed mine for MythTV.
Works great on the first try!
Many, many thanks!
Nico
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This patch replaces my previous patch https://patchwork.kernel.org/patch/816592/
It adds the rc_dev->dev.parent definition missing in the previous version.
---
drivers/media/dvb/mantis/hopper_cards.c|2 +-
drivers/media/dvb/mantis/mantis_cards.c| 27 +++-
drivers/medi
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Thu May 26 19:00:48 CEST 2011
git hash:f9b51477fe540fb4c65a05027fdd6f2ecce4db3b
gcc version: i686-linux-gcc (GCC) 4.5
On May 26, 2011, at 10:25 AM, Jerry Geis wrote:
...
>>> Is there a way I can just compile the linux/drivers/media/video/uvc ?
>>>
>>
>> Edit the .config file, disable anything you don't want to build.
>>
>>
>>> thats all I need. How do I do that?
>>>
>>
>> Another option you can try is
Dan Carpenter wrote:
In the original code, if the allocation failed we dereference "rr3"
when it was NULL.
D'oh, yeah, thanks for the fix.
Acked-by: Jarod Wilson
--
Jarod Wilson
ja...@redhat.com
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a mess
Dan Carpenter wrote:
If change_protocol() fails and we goto out_raw, then it calls unlock
twice.
Gah, good catch, I gotta quit adding new bugs... ;)
I noticed that the other time we called change_protocol() we
held the &dev->lock, so I changed it to hold it here too.
Signed-off-by: Dan Carp
Hi Arnd and others,
On Thu, May 26, 2011 at 11:20:41AM +0200, Arnd Bergmann wrote:
> On Thursday 26 May 2011, Laurent Pinchart wrote:
> > On Thursday 26 May 2011 01:50:07 Mauro Carvalho Chehab wrote:
> > > Em 25-05-2011 20:43, Laurent Pinchart escreveu:
> > > > Issues arise when devices have float
Jarod,
Jarod Wilson wrote:
On May 26, 2011, at 9:11 AM, Jerry Geis wrote:
I am using centos 5.6 (older kernel) and I get compile errors when I grabbed
the latest from http://linuxtv.org/hg/v4l-dvb (which I expect as I have an
older 2.6.18 kernel)
Okay, but do realize that it hasn't
On May 26, 2011, at 9:11 AM, Jerry Geis wrote:
> I am using centos 5.6 (older kernel) and I get compile errors when I grabbed
> the latest from http://linuxtv.org/hg/v4l-dvb (which I expect as I have an
> older 2.6.18 kernel)
Okay, but do realize that it hasn't been updated in ages, and its
comp
On May 26, 2011, at 2:49 AM, jean-francois Moine wrote:
> On Wed, 25 May 2011 17:34:32 -0400
> Jarod Wilson wrote:
>
>> diff --git a/drivers/media/video/gspca/kinect.c
>> b/drivers/media/video/gspca/kinect.c
>> index 66671a4..26fc206 100644
>> --- a/drivers/media/video/gspca/kinect.c
>> +++ b/d
I am using centos 5.6 (older kernel) and I get compile errors when I
grabbed
the latest from http://linuxtv.org/hg/v4l-dvb (which I expect as I have
an older 2.6.18 kernel)
All I need is uvc so I thought I would do "make menuconfig" and turn
everything off
but v4l/UVC stuff.
when I do make I
Hi Laurent,
> Hi Daniel,
>
> On Thursday 26 May 2011 10:57:39 Daniel Lundborg wrote:
> >
> > Hello,
> >
> > I am developing a camera sensor driver for the Aptina MT9V034. I am
only
> > using it in snapshot mode and I can successfully trigger the sensor
and
> > receive pictures using the latest
On 05/26/2011 12:05 PM, Hans Verkuil wrote:
On Thursday, May 26, 2011 07:09:30 vipul kumar samar wrote:
Hello,
On 05/25/2011 06:13 PM, Martin Bugge (marbugge) wrote:
Hello
To be honest I became a bit disengaded after all the discussion.
What caused me a lot of problems was the request for AV
OK, I think I've found the problem with the power management.
As it is stated in mt9p031 datasheet [3] p 59, a sequence involving
[VAA,VAA_PIX,VDD_PLL], [VDD,VDD_IO], [Reset] and [Ext Clk] must be
followed in order to properly power up or down the sensor.
If we take a look to the LI-5M031 schemat
Hi Dan,
On 05/26/2011 10:44 AM, Dan Carpenter wrote:
> If the tvp->cmd == DTV_MAX_COMMAND then we read past the end of the
> array.
>
> Signed-off-by: Dan Carpenter
>
> diff --git a/drivers/media/dvb/dvb-core/dvb_frontend.c
> b/drivers/media/dvb/dvb-core/dvb_frontend.c
> index 9827804..607e293
Hi Daniel,
On Thursday 26 May 2011 10:57:39 Daniel Lundborg wrote:
>
> Hello,
>
> I am developing a camera sensor driver for the Aptina MT9V034. I am only
> using it in snapshot mode and I can successfully trigger the sensor and
> receive pictures using the latest omap3isp driver from
> git://li
Arnd Bergmann wrote:
>On Thursday 26 May 2011, Laurent Pinchart wrote:
>> On Thursday 26 May 2011 01:50:07 Mauro Carvalho Chehab wrote:
>> > Em 25-05-2011 20:43, Laurent Pinchart escreveu:
>> > > Issues arise when devices have floating point registers. And yes,
>that
>> > > happens, I've learnt t
Op 26 mei 2011, om 11:27 heeft javier Martin het volgende geschreven:
> On 26 May 2011 10:51, Koen Kooi wrote:
>>
>> Op 26 mei 2011, om 09:24 heeft Javier Martin het volgende geschreven:
>>
>>> Hi Koen,
>>>
>>> On 25 May 2011 15:38, Koen Kooi wrote:
Op 25 mei 2011, om 13:16 heeft
On Thursday 26 May 2011 11:35:59 Guennadi Liakhovetski wrote:
> On Thu, 26 May 2011, javier Martin wrote:
> > Are you using a LI-5M03 module?
> > (https://www.leopardimaging.com/Beagle_Board_xM_Camera.html)
> > I also added pull ups to the I2C2 line so that I could communicate with
> > mt9p031.
>
On Thu, 26 May 2011, javier Martin wrote:
> Are you using a LI-5M03 module?
> (https://www.leopardimaging.com/Beagle_Board_xM_Camera.html)
> I also added pull ups to the I2C2 line so that I could communicate with
> mt9p031.
Hm, strange, I didn't have to solder anything.
Thanks
Guennadi
---
Guen
On 26 May 2011 10:51, Koen Kooi wrote:
>
> Op 26 mei 2011, om 09:24 heeft Javier Martin het volgende geschreven:
>
>> Hi Koen,
>>
>> On 25 May 2011 15:38, Koen Kooi wrote:
>>>
>>> Op 25 mei 2011, om 13:16 heeft Javier Martin het volgende geschreven:
>>>
It includes several fixes pointed out
On Thursday 26 May 2011, Laurent Pinchart wrote:
> On Thursday 26 May 2011 01:50:07 Mauro Carvalho Chehab wrote:
> > Em 25-05-2011 20:43, Laurent Pinchart escreveu:
> > > Issues arise when devices have floating point registers. And yes, that
> > > happens, I've learnt today about an I2C sensor with
In the original code, if the allocation failed we dereference "rr3"
when it was NULL.
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/rc/redrat3.c b/drivers/media/rc/redrat3.c
index 5147767..4582ef7 100644
--- a/drivers/media/rc/redrat3.c
+++ b/drivers/media/rc/redrat3.c
@@ -1186,7 +1186
On Thursday 26 May 2011 01:50:07 Mauro Carvalho Chehab wrote:
> Em 25-05-2011 20:43, Laurent Pinchart escreveu:
> > Issues arise when devices have floating point registers. And yes, that
> > happens, I've learnt today about an I2C sensor with floating point
> > registers (in this specific case it s
If change_protocol() fails and we goto out_raw, then it calls unlock
twice. I noticed that the other time we called change_protocol() we
held the &dev->lock, so I changed it to hold it here too.
Signed-off-by: Dan Carpenter
---
Compile tested only.
diff --git a/drivers/media/rc/rc-main.c b/driv
If the tvp->cmd == DTV_MAX_COMMAND then we read past the end of the
array.
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/dvb/dvb-core/dvb_frontend.c
b/drivers/media/dvb/dvb-core/dvb_frontend.c
index 9827804..607e293 100644
--- a/drivers/media/dvb/dvb-core/dvb_frontend.c
+++ b/drivers/
>From 70d02ce19f64fae4ceee563501e8462a76e17b91 Mon Sep 17 00:00:00 2001
From: Hans Petter Selasky
Date: Thu, 26 May 2011 10:06:09 +0200
Subject: [PATCH] Correct and add some parameter descriptions.
Signed-off-by: Hans Petter Selasky
---
drivers/media/video/tda7432.c |5 +++--
1 files change
>From 0dd2949dfeae431ed4ffbd00fd14a10dc3747ad0 Mon Sep 17 00:00:00 2001
From: Hans Petter Selasky
Date: Thu, 26 May 2011 09:56:55 +0200
Subject: [PATCH] Remove unused definitions which can cause conflict with
definitions in usb/ch9.h.
Signed-off-by: Hans Petter Selasky
---
drivers/media/dvb/dv
>From 9b38a5c9878b5e4be2899ae291c4524f5f5fc218 Mon Sep 17 00:00:00 2001
From: Hans Petter Selasky
Date: Thu, 26 May 2011 09:49:52 +0200
Subject: [PATCH] Correct error code from -ENOMEM to -EINVAL. Make sure the
return value is set in all cases.
Signed-off-by: Hans Petter Selasky
---
drivers/me
On Thu, 26 May 2011 08:49:12 +0200
Jean-Francois Moine wrote:
> On Wed, 25 May 2011 17:34:32 -0400
> Jarod Wilson wrote:
>
> > diff --git a/drivers/media/video/gspca/kinect.c
> > b/drivers/media/video/gspca/kinect.c
> > index 66671a4..26fc206 100644
> > --- a/drivers/media/video/gspca/kinect.c
At Wed, 25 May 2011 21:21:30 -0300,
Mauro Carvalho Chehab wrote:
>
> Em 23-05-2011 09:17, Ondrej Zary escreveu:
> > Convert radio-sf16fmr2 to use generic TEA575x implementation. Most of the
> > driver code goes away as SF16-FMR2 is basically just a TEA5757 tuner
> > connected to ISA bus.
> > The c
This patch is not ready to be submitted to mainline since it still
has some issues (code belonging to mt9p031 must be moved to a separate
file, etc...). However it is useful for you to test mt9p031 sensor
driver in kernel 2.6.39 (commit 61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf).
Signed-off-by: Jav
This patch applies on 2.6.39 (commit 61c4f2c81c61f73549928dfd9f3e8f26aa36a8cf).
It has some power management issue which causes horizontal random lines on
the image. If we do not disable 1v8 regulator, the problem disappears.
I would like to get some help on fixing whatever the problem with power
m
43 matches
Mail list logo