Porting xf86-video-v4l to use textured video

I'm currently working on make xawtv and xf86-video-v4l fully functional, in order to allow us to test the overlay part of the V4L2 API. I just sent a big patch replacing the old API to the new one, so the driver should be working now. However, only a very few set of drivers will benefit from

Re: [PATCH] Port xf86-video-v4l driver to V4L2

Hi Thierry, Em 08-02-2011 08:12, Thierry Vignaud escreveu: > On 8 February 2011 10:42, Mauro Carvalho Chehab wrote: >> @@ -57,16 +65,16 @@ static MODULESETUPPROTO(v4lSetup); >> >> static XF86ModuleVersionInfo v4lVersRec = >> { >> -&quo

Re: [PATCH] Port xf86-video-v4l driver to V4L2

Hi Thierry, Em 08-02-2011 08:12, Thierry Vignaud escreveu: > On 8 February 2011 10:42, Mauro Carvalho Chehab wrote: >> @@ -57,16 +65,16 @@ static MODULESETUPPROTO(v4lSetup); >> >> static XF86ModuleVersionInfo v4lVersRec = >> { >> -&quo

[PATCH] xserver: Don't crash if Xv is not initialized

initialized); return (char *) (*privates) + key->offset; } As nobody registered it, key->initialized is FALSE, and assert will complain, causing the crash. More information is available on this bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=675532 Signed-off-by: Mauro Carva

Porting xf86-video-v4l to use textured video

I'm currently working on make xawtv and xf86-video-v4l fully functional, in order to allow us to test the overlay part of the V4L2 API. I just sent a big patch replacing the old API to the new one, so the driver should be working now. However, only a very few set of drivers will benefit from

[PATCH 3/8] Use the fourcc header instead of redefining it inside the code

Signed-off-by: Mauro Carvalho Chehab diff --git a/src/v4l.c b/src/v4l.c index 605454b..a51f00f 100644 --- a/src/v4l.c +++ b/src/v4l.c @@ -32,6 +32,7 @@ #include "regionstr.h" #include "dgaproc.h" #include "xf86str.h" +#include "fourcc.h" #include

[PATCH 4/8] Fix Get/Set Port Attribute logic

bugs and clean the code. Signed-off-by: Mauro Carvalho Chehab diff --git a/src/v4l.c b/src/v4l.c index a51f00f..8b3d87e 100644 --- a/src/v4l.c +++ b/src/v4l.c @@ -125,7 +125,6 @@ v4lSetup(pointer module, pointer opts, int *errmaj, int *errmin) typedef struct _XvV4LCtrlRec { struct

[PATCH 5/8] Return BadMatch if a Port Attribute is not found

Fix a small non-compliance issue: if a port attribute is not known, according with Xv specs, it should return BadMatch, and not BadValue. Signed-off-by: Mauro Carvalho Chehab diff --git a/src/v4l.c b/src/v4l.c index 8b3d87e..fbb8bd7 100644 --- a/src/v4l.c +++ b/src/v4l.c @@ -790,6 +790,8

[PATCH 6/8] Provide a more consistent message if FBUF fails

same video format. Signed-off-by: Mauro Carvalho Chehab diff --git a/src/v4l.c b/src/v4l.c index fbb8bd7..877977c 100644 --- a/src/v4l.c +++ b/src/v4l.c @@ -212,6 +212,7 @@ static struct V4L_DEVICE { static int SetV4LFmt(int fd, CARD32 pixelformat) { struct v4l2_framebuffer fbuf; +ch

[PATCH 7/8] Fix arguments for v4l_check_yuv

The device name and the file descriptors are wrong at the cal for v4l_check_yuv(). Due to that, the driver were falling back to work with RGB formats. While here, add a code to prevent V4L driver to work if no video adapter provide Xv overlay method. Signed-off-by: Mauro Carvalho Chehab diff

[PATCH 8/8] Fix standard video size detection

ers. We'll probably need to check for driver versions after reenabling the correct (not working) code, or to use the new VIDIOC ioctl's to enumberate the supported formats. Signed-off-by: Mauro Carvalho Chehab diff --git a/src/v4l.c b/src/v4l.c index 7b3d538..10e782b 100644 --- a/src/v

[PATCH 0/8] Port xf86-video-v4l driver to V4L2 version 2

atches there. Mauro Carvalho Chehab (8): Port xf86-video-v4l driver to V4L2 Coding style Cleanup Use the fourcc header instead of redefining it inside the code Fix Get/Set Port Attribute logic Return BadMatch if a Port Attribute is not found Provide a more consistent message if FBUF fails

Re: [PATCH 0/8] Port xf86-video-v4l driver to V4L2 version 2

Hi Alex, Em 11-02-2011 15:37, Alex Deucher escreveu: > On Fri, Feb 11, 2011 at 10:54 AM, Mauro Carvalho Chehab > wrote: >> This is the second version of my backport patches. To avoid spending >> people's time on looking at lines that have only whitespace changes, >>

[PATCH] xserver: Don't crash if Xv is not initialized

ie Signed-off-by: Mauro Carvalho Chehab diff --git a/hw/xfree86/common/xf86xv.c b/hw/xfree86/common/xf86xv.c index 016db1f..858d3bc 100644 --- a/hw/xfree86/common/xf86xv.c +++ b/hw/xfree86/common/xf86xv.c @@ -218,7 +218,14 @@ xf86XVQueryOffscreenImages( ScreenPtr pScreen, int *num ){ -

[PATCHv2] Don't crash if Xv is not initialized

initialized); return (char *) (*privates) + key->offset; } As nobody registered it, key->initialized is FALSE, and assert will complain, causing the crash. Signed-off-by: Mauro Carvalho Chehab diff --git a/hw/xfree86/common/xf86xv.c b/hw/xfree86/common/xf86xv.c index 016db1f..70b220

Re: IR remote control autorepeat / evdev

Hi Anssi/Peter, Em 10-05-2011 15:43, Anssi Hannula escreveu: > On 10.05.2011 08:30, Peter Hutterer wrote: >> On Tue, May 10, 2011 at 08:14:30AM +0300, Anssi Hannula wrote: >>> On 10.05.2011 07:11, Peter Hutterer wrote: On Sun, May 08, 2011 at 07:38:00AM +0300, Anssi Hannula wrote: > Hi al

Re: IR remote control autorepeat / evdev

Em 11-05-2011 18:33, Anssi Hannula escreveu: > On 11.05.2011 07:46, Mauro Carvalho Chehab wrote: >> Hi Anssi/Peter, > > Hi! > >> Em 10-05-2011 15:43, Anssi Hannula escreveu: >>> On 10.05.2011 08:30, Peter Hutterer wrote: >>>> On Tue, May 10,

Re: IR remote control autorepeat / evdev

Em 11-05-2011 19:59, Anssi Hannula escreveu: >> No. It actually depends on what driver you're using. For example, for most >> dvb-usb >> devices, this is given by the logic bellow: >> >> if (d->props.rc.legacy.rc_interval < 40) >> d->props.rc.legacy.rc_interval = 100; /* default

Re: IR remote control autorepeat / evdev

Em 12-05-2011 02:17, Anssi Hannula escreveu: > On 11.05.2011 23:53, Dmitry Torokhov wrote: >> On Wed, May 11, 2011 at 08:59:16PM +0300, Anssi Hannula wrote: >>> >>> I meant replacing the softrepeat with native repeat for such devices >>> that have native repeats but no native release events: >>> >>

Re: IR remote control autorepeat / evdev

Em 12-05-2011 02:37, Anssi Hannula escreveu: > On 12.05.2011 02:52, Mauro Carvalho Chehab wrote: >> Em 11-05-2011 19:59, Anssi Hannula escreveu: >>>> No. It actually depends on what driver you're using. For example, for most >>>> dvb-usb >>&

Re: IR remote control autorepeat / evdev

Em 12-05-2011 03:10, Mauro Carvalho Chehab escreveu: > Em 12-05-2011 02:37, Anssi Hannula escreveu: >> I don't see any other places: >> $ git grep 'REP_PERIOD' . >> dvb/dvb-usb/dvb-usb-remote.c: input_dev->rep[REP_PERIOD] = >> d->props.rc.legacy

Re: IR remote control autorepeat / evdev

Em 12-05-2011 08:05, Peter Hutterer escreveu: > On Thu, May 12, 2011 at 03:36:47AM +0200, Mauro Carvalho Chehab wrote: >> Em 12-05-2011 03:10, Mauro Carvalho Chehab escreveu: >>> Em 12-05-2011 02:37, Anssi Hannula escreveu: >> >>>> I don't see any

Re: IR remote control autorepeat / evdev

Em 13-05-2011 01:48, Anssi Hannula escreveu: > On 12.05.2011 04:36, Mauro Carvalho Chehab wrote: >> Em 12-05-2011 03:10, Mauro Carvalho Chehab escreveu: >>> Em 12-05-2011 02:37, Anssi Hannula escreveu: >> >>>> I don't see any other places: >>>&g

Re: IR remote control autorepeat / evdev

Em 14-05-2011 01:07, Anssi Hannula escreveu: > On 14.05.2011 01:39, Mauro Carvalho Chehab wrote: >> Em 13-05-2011 01:48, Anssi Hannula escreveu: >>> On 12.05.2011 04:36, Mauro Carvalho Chehab wrote: >>>> Em 12-05-2011 03:10, Mauro Carvalho Chehab escreveu: >>&g

Re: [PATCH:xf86-video-v4l] Bump version for development.

Em 28-06-2011 11:11, Cyril Brulebois escreveu: > Signed-off-by: Cyril Brulebois > --- > configure.ac |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > The version number wasn't bumped after 0.2.0; given the big changes from > Mauro Carvalho Chehab to