Nemosoft Unv. wrote: >On Friday 15 March 2002 18:19, Greg KH wrote: > >>Also realize that the v4l interfaces are changing right now in 2.5, so >>you will end up with two different drivers over time. >> >You mean the introduction of V4L2? Well, if that happens I will *probably* >abandon the 2.4 driver; more or less what I did with the 2.2 series. But >the driver is complete enough. But that's my call :-) >
Just thought I'd jump in here :) This is a redesign of the V4L1 interface. See http://www.uwsg.iu.edu/hypermail/linux/kernel/0203.0/0335.html . The patches for the individual drivers are at: http://bytesex.org/patches/ . There's a videodev.c patch there for 2.4 as well, but I'm not confident that Marcelo will approve such a change. The bulk of the changes are to ioctl(). The copy_[to|from]_user is done in videodev.c now, by the video_generic_ioctl() helper function. I copied this function into my driver so that I could use the same ov511_ioctl() under 2.2/2.4/2.5 (with a minimum of #ifdefs). If you want to, you can see my code at http://alpha.dyndns.org/ov511/download/ov511.c As for abandoning 2.4 because of V4L2, you probably won't have to do that completely. The V4L2 "videodevX" driver works with 2.2 and 2.4, and supports both V4L1 and V4L2 drivers and apps. Your in-kernel 2.4 driver will have to be abandoned, of course, but 2.4 users will still be able to use the latest driver from your website. That said, the number of preprocessor statements in my code is getting pretty bad. I'll have to abandon 2.2 soon, and eventually 2.4, or I'll be spending more time on cross-kernel compatibility than writing real code. :-) -- Mark McClelland [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
