I have just had a look, and it seems that v4l2-cc should work with videodevX. I didn't immediatley notice any discrepancies, but there may be some. It should be fine to use v4l2-cc with videodevX. The package is still available from http://bttv-v4l2.sourceforge.net/bttv-v4l2/ . I didn't actually realise that v4l2-cc was being used in another project. Maybe it would be a good idea to split v4l2-cc off into it's own project? Any volunteers to maintain this? -justin Chris Worley wrote: > > Problem is, I've got drivers that need to be ported (about 4). Should > I try porting v4l2-cc.[ch] to work with videodevX? > > Are there some instructions for weaning these drivers away from > v4l2-cc.[ch]? > > Thanks, > > Chris > > Justin Schoeman wrote: > > > > Chris Worley wrote: > > > > > > I'm trying to upgrade some old V4L2 device drivers to 2.4 (looking at > > > http://bttv-v4l2.sourceforge.net/download/videodevX-061000.tgz ). > > > > > > I'm noticing that the v4l2-cc.[ch] files are not used anymore. > > > > > > What happened? Is there any documentation that describes the changes > > > that need to be made to rid yourself of dependence on these files? > > > > > > Thanks, > > > > > > Chris > > > > When you upgrade to bttv2 + videodevX the dependancies to v4l2-cc go > > away (you may have to remove the old v4l2-cc and videodev files). The > > v4l2-cc system was a much more elegant way of handling the bttv > > subsystems, but due to the masses of cards out there it became > > hopelessly impractical to maintain the two separate access methods. > > > > (If anybody wants to reintegrate and maintain the v4l2-cc subsystem, > > feel free!) > > > > -justin
