Signed-off-by: Bee Hock Goh beeh...@gmail.com
diff --git a/drivers/staging/tm6000/tm6000-cards.c
b/drivers/staging/tm6000/tm6000-cards.c
index f795a3e..ced8fce 100644
--- a/drivers/staging/tm6000/tm6000-cards.c
+++ b/drivers/staging/tm6000/tm6000-cards.c
@@ -349,6 +349,22 @@ int
Avoid(until there is a better fix) cleaning up of buffer as it will
cause partital green screen when there are frame dropped.
Fix video line couting corruption when cmd is not a video packet.
Signed-off-by: Bee Hock Goh beeh...@gmail.com
diff --git a/drivers/staging/tm6000/tm6000-video.c
Sakari Ailus wrote:
Hi Mauro,
Hans Verkuil has provided the patches to support the V4L2 events on ivtv
(thanks, Hans!). Those patches are part of this pull request. The
documentation has been improved --- v4l2_fh is now clearly marked as
optional interface. Rebased, too.
Please pull.
Samuel Ortiz wrote:
Hi Richard,
On Fri, Apr 16, 2010 at 06:27:54PM +0200, Richard Röjfors wrote:
To follow are two patches.
The first one adds the timberdale video-in driver to the media tree.
The second one adds it to the timberdale MFD driver.
The Kconfig of the media patch selects
On Sunday 25 April 2010 15:42:54 Mauro Carvalho Chehab wrote:
Oliver Endriss wrote:
On Sunday 21 March 2010 21:15:01 Oliver Endriss wrote:
Mauro,
Please pull from http://linuxtv.org/hg/~endriss/ngene
for the following changeset:
01/01: ngene: Workaround for stuck DiSEqC pin
Richard Röjfors wrote:
On 04/25/2010 05:24 PM, Mauro Carvalho Chehab wrote:
Richard Röjfors wrote:
This patch adds the timberdale video-in driver.
The video IP of timberdale delivers the video data via DMA.
The driver uses the DMA api to handle DMA transfers, and make use
of the V4L2
On 04/25/2010 05:24 PM, Mauro Carvalho Chehab wrote:
Richard Röjfors wrote:
This patch adds the timberdale video-in driver.
The video IP of timberdale delivers the video data via DMA.
The driver uses the DMA api to handle DMA transfers, and make use
of the V4L2 videobuffers to handle buffers
On Wed, Apr 21, 2010 at 2:44 AM, Oliver Endriss o.endr...@gmx.de wrote:
It's merged in Mauro's fixes tree, but I don't think those pending patches
have been pushed upstream yet. Mauro, can you verify this? They should be
pushed to 2.6.34!
What about the HG driver?
The v4l-dvb HG repository
Hi!
I'd have an Exibel snakescope TF2808 which dont make any picure on
Linux. It worked ok on windows, but I do not have windows installed
any longer. I do not think there have happened something to the camera
meanwhile, I'd think the camera is OK. The driver seems to be ok too:
(part of
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:Sun Apr 25 19:00:28 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14592:b438301e588f
git master:
Hi
It's my error. This code good only for tm6010. Now I rework my patch.
With my best regards, Dmitry.
I am still able to watch tv after applying the patch but the return
code is bad and is causing unnecessary reloading of the same
firmwares.
[ 2482.599040] usb 1-1: firmware: requesting
Hi
It's my error. This code good only for tm6010. Now I rework my patch.
With my best regards, Dmitry.
Am 23.04.2010 02:48, schrieb Dmitri Belimov:
Hi
Rework I2C for read word from connected devices, now it works well.
Add new functions for read/write blocks.
diff -r 7c0b887911cf
Hi
Rework last I2C patch.
Set correct limit for I2C packet.
Use different method for the tm5600/tm6000 and tm6010 to read word.
Try this patch.
diff -r 7c0b887911cf linux/drivers/staging/tm6000/tm6000-i2c.c
--- a/linux/drivers/staging/tm6000/tm6000-i2c.c Mon Apr 05 22:56:43 2010 -0400
+++
Hi
Sometimes tuner XC5000 crashed on boot. This PC is dual-core.
It can be race condition or multi-core depend problem.
Add mutex for solve this problem is correct?
Crash boot dmesg
[ 11.430108] Linux video capture interface: v2.00
[ 11.503411] saa7130/34: v4l2 driver version 0.2.15 loaded
On Mon, 2010-04-26 at 10:44 +1000, Dmitri Belimov wrote:
Hi
Sometimes tuner XC5000 crashed on boot. This PC is dual-core.
It can be race condition or multi-core depend problem.
Add mutex for solve this problem is correct?
Dmitri,
This problem may be related to the firmware loading race
15 matches
Mail list logo