There are three drivers that use video_ioctl2() as an unlocked_ioctl,
let them use the new video_ioctl2_unlocked.
Signed-off-by: Frederic Weisbecker
---
drivers/media/video/davinci/vpfe_capture.c |2 +-
drivers/media/video/gspca/gspca.c |2 +-
drivers/media/video/hdpvr/hdpvr-vid
These are the last remaining v4l drivers that implement the ioctl
callback.
Signed-off-by: Frederic Weisbecker
---
drivers/media/video/bw-qcam.c| 11 -
drivers/media/video/c-qcam.c | 11 -
drivers/media/video/cpia.c | 11 +++
Now that video_ioctl2() got the bkl pushed down, update its users
to use .unlocked_ioctl instead of ioctl.
Signed-off-by: Frederic Weisbecker
---
drivers/media/common/saa7146_fops.c |2 +-
drivers/media/radio/dsbr100.c|2 +-
drivers/media/radio/radio-aims
video_ioctl2 is a generic ioctl helper used by a lot of drivers.
Most of them put it as their bkl'ed .ioctl callback, then let's
pushdown the bkl inside but also provide an unlocked version for
those that use it as an unlocked ioctl.
Signed-off-by: Frederic Weisbecker
---
drivers/media/video/v4l
Hi,
Linus suggested to rename struct v4l2_file_operations::ioctl
into bkl_ioctl to eventually get something greppable and make
its background explicit.
While at it I thought it could be a good idea to just pushdown
the bkl to every v4l drivers that have an .ioctl, so that we
actually remove struc
On Thu, Apr 29, 2010 at 12:52:57AM +0200, Laurent Pinchart wrote:
> Hi everybody,
>
> Here's a new version of the UVC gadget driver I posted on the list some time
> ago, rebased on 2.6.34-rc5.
>
> The private events API has been replaced by the new V4L2 events API that will
> be available in 2.6.
This webcam gadget instantiates a UVC camera (360p and 720p resolutions
in YUYV and MJPEG).
Signed-off-by: Laurent Pinchart
---
drivers/usb/gadget/Kconfig |9 +-
drivers/usb/gadget/Makefile |2 +
drivers/usb/gadget/webcam.c | 399 +++
3 files cha
Hi everybody,
Here's a new version of the UVC gadget driver I posted on the list some time
ago, rebased on 2.6.34-rc5.
The private events API has been replaced by the new V4L2 events API that will
be available in 2.6.34 (the code is already available in the v4l-dvb tree on
linuxtv.org, and should
On Wed, Apr 28, 2010 at 01:41:12PM -0700, Dmitry Torokhov wrote:
> On Wed, Apr 28, 2010 at 01:37:00PM -0400, Jarod Wilson wrote:
> > Set the EV_REP bit, so reported key repeats actually make their
> > way out to userspace, and fix up the handling of repeats a bit,
> > routines for which are shamele
--
Stefan Ringel
commit 32b6f5e24c4de1143c784fd82201ac32c191c3b0
Author: Stefan Ringel
Date: Wed Apr 28 22:31:19 2010 +0200
tm6000: bugfix analog init for tm6010
- change value in function tm6000_set_fourcc_format
- disable digital source
- add vbi and audio init
On Wed, Apr 28, 2010 at 01:37:00PM -0400, Jarod Wilson wrote:
> Set the EV_REP bit, so reported key repeats actually make their
> way out to userspace, and fix up the handling of repeats a bit,
> routines for which are shamelessly heisted from ati_remote2.c.
>
Is it really needed? I'd expect input
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:Wed Apr 28 19:00:24 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 14605:5910305f6d48
git master:
First some additional info.
my current dmesg is full with messages like:
[93953.934121] ds3000_readreg: read reg 0xfe, value 0x92
[93953.934128] ds3000_writereg: write reg 0xfe, value 0x9b
[93953.953980] ds3000_writereg: write reg 0x29, value 0x80
[93953.974481] ds3000_writereg: write reg 0x25, v
On Sun, Mar 14, 2010 at 06:13:16PM +0200, Olimpiu Pascariu wrote:
> >From 9473816c446a6ca91905fc49a73732f70b5223b4 Mon Sep 17 00:00:00 2001
> From: Olimpiu Pascariu
> Date: Sun, 14 Mar 2010 17:44:37 +0200
> Subject: [PATCH 844/844] Staging: cx25821: fix coding style issues in
> cx25821-alsa.c
>
This is a follow-up to my prior patch implementing ir-core's
change_protocol functionality in the imon driver, which eliminates
a false warning when change_protocol is called without a specific
protocol selected yet (i.e., still IR_TYPE_UNKNOWN). It also removes
some extraneous blank lines getting
Set the EV_REP bit, so reported key repeats actually make their
way out to userspace, and fix up the handling of repeats a bit,
routines for which are shamelessly heisted from ati_remote2.c.
Signed-off-by: Jarod Wilson
---
drivers/media/IR/imon.c | 38 +++---
1
Hello all,
I have bought a new tevii s660 device in december 3 months later
(backorder) when i received my device i was having issues when loading the
driver from the tevii website.
First loading went ok but then i got hundreds of debug messages in dmesg.
Later this device really died so i sent it
Laurent Pinchart wrote:
> Hi Hans,
>
> On Wednesday 28 April 2010 14:37:10 Hans Verkuil wrote:
>>> Arnd Bergmann wrote:
>
> [snip]
>
Mauro, does this patch make sense to you? It would be good to have your
Ack so we can queue this in the series leading to the removal of the
->ioctl
Sergio Aguirre wrote:
> After commit ID:
>
> commit de380b55f92986c1a84198149cb71b7228d15fbd
> Author: Tejun Heo
> Date: Wed Mar 24 17:06:43 2010 +0900
>
> percpu: don't implicitly include slab.h from percpu.h
>
> slab.h include was not longer implicitly included with sched.h.
>
Hi Andre,
On Wed, 28 Apr 2010 14:29:10 +0200
André Weidemann wrote:
>
> How come there is such a high current drain to drive the switch plus
> the LNBs? From what I understand, the switch should only power one
> LNB at a time. Usually the switch plus the LNB should not drain more
> than 300-40
On Wed, Apr 28, 2010 at 12:33 PM, Guy Martin wrote:
> On Wed, 28 Apr 2010 09:45:39 +0200
> André Weidemann wrote:
>
>> I advise not to pull this change into the kernel sources.
>> The card has only been testet with the a maximum current of 515mA.
>> Anything above is outside the specification for
Hi Hans,
On Wednesday 28 April 2010 14:37:10 Hans Verkuil wrote:
> > Arnd Bergmann wrote:
[snip]
> >> Mauro, does this patch make sense to you? It would be good to have your
> >> Ack so we can queue this in the series leading to the removal of the
> >> ->ioctl file operation. We can also do the
> Hi Arnd,
>
> Arnd Bergmann wrote:
>> On Tuesday 27 April 2010, John Kacur wrote:
>>> Well it is certainly possible that my fixup is not correct too - your
>>> patch cannot be correct, because it doesn't compile! Here is what I get
>>> when I apply your patch to a recent linus/master
>>
>> Ah, I
Hello Guy,
On 28.04.2010 10:33, Guy Martin wrote:
On Wed, 28 Apr 2010 09:45:39 +0200
André Weidemann wrote:
I advise not to pull this change into the kernel sources.
The card has only been testet with the a maximum current of 515mA.
Anything above is outside the specification for this card.
Hi Arnd,
Arnd Bergmann wrote:
> On Tuesday 27 April 2010, John Kacur wrote:
>> Well it is certainly possible that my fixup is not correct too - your
>> patch cannot be correct, because it doesn't compile! Here is what I get
>> when I apply your patch to a recent linus/master
>
> Ah, I see.
>
>
Dmitri Belimov wrote:
> Hi
>
> Anyone can watch TV with tm6000 module??
>
> I try mplayer. My PC crashed inside copy_streams function after some time.
>
> With my best regards, Dmitry.
It is still causing panic on my tests. Probably, the routine is still writing
something out of the buffer area
> -Original Message-
> From: Hiremath, Vaibhav
> Sent: Wednesday, April 28, 2010 1:17 AM
> To: Aguirre, Sergio; linux-media@vger.kernel.org
> Cc: mche...@redhat.com; Karicheri, Muralidharan; hverk...@xs4all.nl
> Subject: RE: [PATCH-V7] OMAP2/3 V4L2: Add support for OMAP2/3 V4L2 driver
> o
Hello Mauro,
could you please pull the following patches?
https://patchwork.kernel.org/patch/95627/
https://patchwork.kernel.org/patch/95628/
https://patchwork.kernel.org/patch/95629/
Best regards
--
Pawel Osciak
Linux Platform Group
Samsung Poland R&D Center
--
To unsubscribe from this lis
patch seem work with no adverse effect or benefit? although the green
screen is still an issue if the buffer is cleared.
maybe its just perception Will this patch give a better quality video?
On Mon, Apr 26, 2010 at 10:24 PM, Mauro Carvalho Chehab
wrote:
> Although the code is getting the better
On Wed, 28 Apr 2010 09:45:39 +0200
André Weidemann wrote:
> I advise not to pull this change into the kernel sources.
> The card has only been testet with the a maximum current of 515mA.
> Anything above is outside the specification for this card.
I'm currently running two of these cards in the
Hello Guy,
On 11.04.2010 23:18, Guy Martin wrote:
Hi linux-media,
The following patch increases the current limit for the isl6423 chip
on the TT S2-1600 card. This allows DiSEqC to work with more complex
and current demanding configurations.
Signed-off-by: Guy Martin
I am sorry for the l
its working fine on my tm5600. Run fine for more than 5mins without crashing.
But it does crashed everytime when its playing on the first channel
and I switch channel in mythtv. I am waiting for usb/serial cable to
arrive from ebay to find out why.
I hope to work on the audio part though.
On Wed
Hello,
I have a WinTV-Nova-HD-S2 (known as HVR4000Lite) card for HD receiving.
After a while of browsing trough channels, I'm getting the message:
cx24116_cmd_execute() Firmware not responding
and the card fails to tune anymore.
The only fix from this situation is to reload the drivers and the
From: Hans Verkuil
For recoverable stream errors dqbuf() now returns 0 and the error flag
is set instead of returning EIO.
Signed-off-by: Hans Verkuil
---
drivers/media/video/videobuf-core.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/media/v
Add documentation for V4L2_BUF_FLAG_ERROR.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
Documentation/DocBook/v4l/io.xml | 10 ++
Documentation/DocBook/v4l/vidioc-qbuf.xml | 14 --
2 files changed, 22 insertions(+), 2 deletions(-)
diff --git a/D
This flag is intended to indicate streaming errors, which might have
resulted in corrupted video data in the buffer, but the buffer can still
be reused and streaming may continue.
Setting this flag and returning 0 is different from returning EIO. The
latter should now indicate more serious (unreco
Hello,
this is the fourth version of a series that introduces a V4L2_BUF_FLAG_ERROR
flag for recoverable stream errors. It allows applications to gracefully recover
in case of such errors instead of losing the buffer or having to guess
its index.
Changes since v3:
- fixed a typo in docs
- removed
37 matches
Mail list logo