[linux-dvb] Re: problem with 1.1.1 and VDR grab

[Peter Siering <lists@siering.org>]

On Fri, 2004-03-12 at 10:48, Michael Hunold wrote:
> > 
> > plain Debian plus Gerd Knorrs V4L2 patches (as I wrote in my first post,
> > the same Kernel(+Patches) works as expected with DVB 1.1.0).
> 
> Sorry, I missed that piece of information.
> 
> Ok, but this explains your problems. Gerd Knorr regularly improves the 
> v4l2 helper modules (like video-buf, v4l2-common or v4l1-compat) or 
> incorporates my fixes.
> 
> He regularly creates patches against recent 2.4 kernels, but he 
> *doesn't* create patches against older versions, ie. the patches against 
> 2.4.24 and 2.4.25 contain differences.
> 
> When 2.4.25 came out, I took his latest improvements and incorporated it 
> into the DVB tree. The problem now is, that the in-kernel modules for 
> 2.4.24 are compiled against different header files than the DVB drivers 
> from the release. This is screaming for problems.
> 
> One solution is to upgrade to 2.4.25 and use the CVS version of the 
> "dvb-kernel" tree. (Not the release, because some bugfixes are missing)
>

So just the CVS dvb-kernel catches up with Gerds Knorrs patches for
2.4.25rc1 (the freshest on bytesex.org)? 

I gave those a try, but had not much success: things I had running fine
with 2.4.24 (and Gerds patches) stopped working (analogtv-plugin for
VDR, ivtv/PVR).

> Or you take 2.6.4 and apply the patches from the "patches-2.6" directory 
> from "dvb-kernel" CVS.
> 

2.6 is not an option for me. I am not (just) doing it for my personal
entertainment, but I am working on improvements on our VDR distribution
and I am stuck to keep some other devices running: dxr3 and PVR; that
looks more promising with 2.4 for now.

> >>I can confirm that 1.1.1 contains a bug that produces a kernel oops 
> >>through the v4l1 compatibility layer when using "kvdr". Taking a 
> >>snapshot via "space" then quitting the application will cause a kernel oops.
> >>
> >>I'm working on it, the fix for preventing the oops is easy. But it looks 
> >>like "kvdr" needs to be changed in order to work after that change.
> 
> > If you like to, I could give it try.
> 
> I apologize for the current problems. The problems are due to the fact 
> that most applications are still Video4Linux-1 specific, so all stuff 
> goes through the compatibility layer until it reaches the DVB 
> Video4Linux-2 driver. I recently added some resource management to get 
> the driver more robust and a lot of hidden bugs are now triggered.
> 
> I admit that it was unfortunate to do this before the releases, but now 
> we have to live with it. Be assured that I'm really interested to fix 
> all these problems.
> 

What about the fix you mentioned for kvdr - may be it could help me to
fix the problem with VDR too?

Thanks,
Peter




-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.