Em 10-09-2010 00:20, Pawel Osciak escreveu:
> Hello Mauro,
>
> On 09/10/2010 02:53 AM, Mauro Carvalho Chehab wrote:
>> Em 09-09-2010 06:19, Pawel Osciak escreveu:
>> > Hello,
>> >
>> > These patches add a new driver framework for Video for Linux 2 driver
>> > - Videobuf2.
>>
>> I didn't test the p
Hello Mauro,
On 09/10/2010 02:53 AM, Mauro Carvalho Chehab wrote:
Em 09-09-2010 06:19, Pawel Osciak escreveu:
> Hello,
>
> These patches add a new driver framework for Video for Linux 2 driver
> - Videobuf2.
I didn't test the patches, but, from a source code review, they seem
on a good shape. I
On Thu, Sep 09, 2010 at 12:34:27AM -0400, Jarod Wilson wrote:
...
> >> For now, I've applied patches 3, 4 and 5, as it is nice to have Jarod's
> >> review also.
> >
> > I've finally got them all applied atop current media_tree staging/v2.6.37,
> > though none of the streamzap bits in patch 7 are a
On Thu, Sep 9, 2010 at 8:40 PM, Maxim Levitsky wrote:
> On Wed, 2010-09-08 at 10:47 -0400, Jarod Wilson wrote:
>> On Mon, Sep 6, 2010 at 5:26 PM, Maxim Levitsky
>> wrote:
>> > These keys are found on remote bundled with
>> > Toshiba Qosmio F50-10q.
>> >
>> > Found and tested by, Sami R
>> >
>>
Hi
On Friday 10 September 2010, Antti Palosaari wrote:
> Moikka Mauro!
> This patch series adds support for TerraTec Cinergy T Stick Dual RC and
> TerraTec Cinergy T Stick RC. Also MxL5007T devices with ref. design IDs
> should be working. Cinergy T Stick remote is most likely not working
> sin
On Thu, 2010-09-09 at 16:17 +0200, Hans Verkuil wrote:
> > Hans,
> > I'll have more later, but I can say, if LED API is what we agree to, we
> > should have infrastructure in v4l2 at a level higher than gspca for
> > helping drivers use the LED interface and triggers.
> >
> >
> > Specifically this
On Wed, 2010-09-08 at 10:47 -0400, Jarod Wilson wrote:
> On Mon, Sep 6, 2010 at 5:26 PM, Maxim Levitsky
> wrote:
> > These keys are found on remote bundled with
> > Toshiba Qosmio F50-10q.
> >
> > Found and tested by, Sami R
> >
> > Signed-off-by: Maxim Levitsky
> > ---
> > drivers/media/IR/k
Hi
On Friday 10 September 2010, Antti Palosaari wrote:
> Moikka Mauro!
> This patch series adds support for TerraTec Cinergy T Stick Dual RC and
> TerraTec Cinergy T Stick RC. Also MxL5007T devices with ref. design IDs
> should be working. Cinergy T Stick remote is most likely not working
> sin
Hi,
cards like the Digital Devices DuoFlex S2, cineS2 and upcoming
hardware (octuple, network, etc.) have independent CA devices.
This means that instead of having the stream routed from the frontend
through the CI and only then into memory a stream can be sent from
memory through the CI and bac
On Thu, 2010-09-09 at 15:17 +0200, Hans de Goede wrote:
> Hi,
>
> On 09/09/2010 04:41 PM, Andy Walls wrote:
> > Hans de Goede,
> >
> > The uvc API that creates v4l2 ctrls on behalf of userspace could intercept
> > those calls and create an LED interface instead of, or in addition to, the
> > v4l
Moikka Mauro!
This patch series adds support for TerraTec Cinergy T Stick Dual RC and
TerraTec Cinergy T Stick RC. Also MxL5007T devices with ref. design IDs
should be working. Cinergy T Stick remote is most likely not working
since it seems to use different remote as Cinergy T Dual... Stefan c
> "Hans" == Hans Verkuil writes:
Hi,
Hans> But I feel I am missing something: who is supposed to use these LEDs?
Hans> Turning LEDs in e.g. webcams on or off is a job for the driver, never for
Hans> a userspace application.
Agreed - By default, the driver should just turn on the LED when
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 Sep 9 19:00:05 CEST 2010
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 15139:6e0befab696a
git master:
Hi,
I was wondering if there exists a current standard way to query a
Imaging sensor driver for knowing things like the signal vert/horz blanking
time.
In an old TI custom driver, we used to have a private IOCTL in the sensor
Driver we interfaced with the omap3 ISP, which was basically reporting
Em 09-09-2010 06:19, Pawel Osciak escreveu:
> Hello,
>
> These patches add a new driver framework for Video for Linux 2 driver
> - Videobuf2.
I didn't test the patches, but, from a source code review, they seem
on a good shape. I did a few comments on some patches. There are a few
missing feature
From: Stefan Ringel
Signed-off-by: Stefan Ringel
---
drivers/staging/tm6000/tm6000-input.c | 61 +
1 files changed, 39 insertions(+), 22 deletions(-)
diff --git a/drivers/staging/tm6000/tm6000-input.c
b/drivers/staging/tm6000/tm6000-input.c
index 7b07096..dac
Em 09-09-2010 06:19, Pawel Osciak escreveu:
> Add generic memory handling routines for userspace pointer handling,
> contiguous memory verification and mapping.
>
> Signed-off-by: Pawel Osciak
> Signed-off-by: Kyungmin Park
> ---
> drivers/media/video/Kconfig|3 +
> drivers/medi
Hi,
On 09/09/2010 04:41 PM, Andy Walls wrote:
Hans de Goede,
The uvc API that creates v4l2 ctrls on behalf of userspace could intercept
those calls and create an LED interface instead of, or in addition to, the v4l2
ctrl.
That would mean special casing certain extension controls which I don
Hi,
On 09/09/2010 04:14 PM, Andy Walls wrote:
I'm of the mind that independent boolean illuminator controls are Ok. I think
that scales better. Not that I could imagine many in use for 1 camera anyway,
but some may be colors other than white.
Illuminator0 should always correspond to the mos
Hans de Goede,
The uvc API that creates v4l2 ctrls on behalf of userspace could intercept
those calls and create an LED interface instead of, or in addition to, the v4l2
ctrl.
Until udev, hal, pam, and polkit userspace configurations catch up, one still
has the problem of the sysfs LED files n
> Hans,
> I'll have more later, but I can say, if LED API is what we agree to, we
> should have infrastructure in v4l2 at a level higher than gspca for
> helping drivers use the LED interface and triggers.
>
>
> Specifically this is needed to make discovery and association of v4l2
> devices, expos
I'm of the mind that independent boolean illuminator controls are Ok. I think
that scales better. Not that I could imagine many in use for 1 camera anyway,
but some may be colors other than white.
Illuminator0 should always correspond to the most common default application of
the device.
I r
Hi all, first post.
I have a newly purchased Leadtek DTV2000DS dual tuner card in my
machine, configured and running in Mythbuntu 10.04 (after installing
latest v4l-dvb from source). I am having a bit of trouble getting the
supplied remote control working. Is anyone here able to assist? I
asked on
Hans,
I'll have more later, but I can say, if LED API is what we agree to, we should
have infrastructure in v4l2 at a level higher than gspca for helping drivers
use the LED interface and triggers.
Specifically this is needed to make discovery and association of v4l2 devices,
exposed v4l2 LEDs
Hi,
On 09/09/2010 03:29 PM, Hans Verkuil wrote:
Hi,
On 09/09/2010 08:55 AM, Peter Korsgaard wrote:
"Hans" == Hans Verkuil writes:
Hi,
>> - the status LED should be controlled by the LED interface.
Hans> I originally was in favor of controlling these through v4l as
Hans>
> Hi,
>
> On 09/09/2010 08:55 AM, Hans Verkuil wrote:
>> On Tuesday, September 07, 2010 23:14:10 Hans de Goede wrote:
>
>
>
>>> How about a compromise, we add a set of standard defines for menu
>>> index meanings, with a note that these are present as a way to
>>> standardize
>>> things between d
> Hi,
>
> On 09/09/2010 08:55 AM, Peter Korsgaard wrote:
>>> "Hans" == Hans Verkuil writes:
>>
>> Hi,
>>
>> >> - the status LED should be controlled by the LED interface.
>>
>> Hans> I originally was in favor of controlling these through v4l as
>> Hans> well, but people made some goo
Hi,
On 09/09/2010 08:55 AM, Peter Korsgaard wrote:
"Hans" == Hans Verkuil writes:
Hi,
>> - the status LED should be controlled by the LED interface.
Hans> I originally was in favor of controlling these through v4l as
Hans> well, but people made some good arguments against that. The
Hi,
On 09/09/2010 08:55 AM, Hans Verkuil wrote:
On Tuesday, September 07, 2010 23:14:10 Hans de Goede wrote:
How about a compromise, we add a set of standard defines for menu
index meanings, with a note that these are present as a way to standardize
things between drivers, but that some dri
On Wed, Sep 08, 2010 at 12:42:05AM -0700, Dmitry Torokhov wrote:
> Switch the code to use new style of getkeycode and setkeycode
> methods to allow retrieving and setting keycodes not only by
> their scancodes but also by index.
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> drivers/input/misc/at
On 09/09/2010 06:19 PM, Pawel Osciak wrote:
Hello,
These patches add a new driver framework for Video for Linux 2 driver
- Videobuf2.
Sorry, I failed to mention that these patches depend on the multi-planar
API extensions, but do not require multi-planar support in drivers and
in vivi.
Vide
Make vivi use videobuf2 in place of videobuf.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
drivers/media/video/Kconfig |2 +-
drivers/media/video/vivi.c | 248 +--
2 files changed, 124 insertions(+), 126 deletions(-)
diff --git a/dr
Videobuf2 is a Video for Linux 2 API-compatible driver framework for
multimedia devices. It acts as an intermediate layer between userspace
applications and device drivers. It also provides low-level, modular
memory management functions for drivers.
Videobuf2 eases driver development, reduces driv
Add generic memory handling routines for userspace pointer handling,
contiguous memory verification and mapping.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
drivers/media/video/Kconfig|3 +
drivers/media/video/Makefile |2 +
drivers/media/video/vid
Add support for the CMA contiguous memory allocator to videobuf2.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
drivers/media/video/Kconfig |5 +
drivers/media/video/Makefile|2 +
drivers/media/video/videobuf2-cma.c | 250 +
Hello,
These patches add a new driver framework for Video for Linux 2 driver
- Videobuf2.
Videobuf2 is intended as a replacement for videobuf, the current driver
framework, which will be referred to as "videobuf1" for the remainder
of this document.
What is video
Add an implementation of contiguous virtual memory allocator and handling
routines for videobuf2, implemented on top of vmalloc()/vfree() calls.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
drivers/media/video/Kconfig |5 +
drivers/media/video/Makefile
Add an implementation of DMA coherent memory allocator and handling
routines for videobuf2, implemented on top of dma_alloc_coherent() call.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
drivers/media/video/Kconfig |5 +
drivers/media/video/Makefile
Port memory-to-memory framework to videobuf2 framework.
Signed-off-by: Pawel Osciak
Signed-off-by: Kyungmin Park
---
drivers/media/video/Kconfig|3 +-
drivers/media/video/v4l2-mem2mem.c | 185 ++--
include/media/v4l2-mem2mem.h | 49 ++
On Wed, 2010-09-08 at 23:12 +0200, David Härdeman wrote:
> On Wed, Sep 08, 2010 at 11:10:40AM -0400, Andy Walls wrote:
> > Tag files and a decent editor are all one needs for full code
> > navigation. The kernel makefile already has a tags target to make the
> > tags file.
>
> If you like to
Hello.
And thanks for the comments.
On Wed, 2010-09-08 at 20:35 +0200, ext Mauro Carvalho
> > }
> > @@ -386,6 +394,8 @@ const char *v4l2_ctrl_get_name(u32 id)
> > case V4L2_CID_TUNE_PREEMPHASIS: return "Pre-emphasis settings";
> > case V4L2_CID_TUNE_POWER_LEVEL: retur
On Thursday 09 September 2010 01:16:09 Mauro Carvalho Chehab wrote:
> Em 07-09-2010 12:58, Patrick Boettcher escreveu:
> > Hi Mauro,
> >
> > On Tuesday 07 September 2010 17:50:45 pboettc...@kernellabs.com wrote:
> >> From: Olivier Grenie
> >>
> >> To improve performance on DiB7770-devices enabli
42 matches
Mail list logo
