[pvrusb2] break with the past...

Mike Isely isely at isely.net
Wed Feb 22 09:48:49 CST 2012


Everyone:

To date I have worked to ensure that the standalone pvrusb2 driver stays 
at least compilable with old kernels dating all the way back to 2.6.12.x 
- that's 7 years ago!  Even the snapshot released a few days ago I 
successfully verified compilation against a kernel that old.

By "standalone" pvrusb2 driver, what I mean is the driver tarball that 
you can download from the pvrusb2 web site - as opposed to the pvrusb2 
driver version that has also been included with the kernel tree since 
about 2.6.18.

I've been able to do this with the standalone driver because, well, I've 
been very careful with #ifdef'ing implementations in the code and 
minding how the environment has changed as the kernel & V4L have changed 
over time.

At some point however there will need to be a break with the past.  I 
suspect that the standalone driver would shrink considerably if I were 
to cut compatibility off at, for example, 2.6.32.x.

So a question I have for people here is this: What is the *OLDEST* 
kernel for which you are using the standalone pvrusb2 driver?  Don't 
count any uses of the in-kernel pvrusb2 driver - that's bound into the 
specific kernel version so obviously nothing there would ever change.  
What I'm looking for is an idea for just how far back it makes sense to 
continue with backwards compatibility for the standalone driver.

What is the *OLDEST* kernel version for which you are using the 
standalone pvrusb2 driver?

  -Mike

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8


More information about the pvrusb2 mailing list