> > I suggest to increase the ivtv driver version number when implementing > > the changes. The application (which must be backward compatible) should > > be able to determine which ioctl it has to use. > > These days the version number of all drivers is the same as the kernel > version number, so it is easy to check when new ioctls became available. Does this mean that the ivtv driver version is also 3.3 when somebody uses an older kernel with updated drivers from media_build? I am worried that this might be the case if somebody checks out from the staging/for_v3.3 Branch **before** the patch is merged. > > > > It would be much better if the ivtv driver would continue to support the > > old ioctl for the few years we still have any PVR350 user. > > Don't worry, I won't be removing anything. good :-) > > I checked the plugin code and you aren't using VIDEO_GET_EVENT. The > VIDEO_GET_EVENT ioctl is the only one I'd really like to get rid of in > ivtv in favor of the V4L2 event API. It's only used as far as I can tell > in ivtv-ctl and ivtvplay, both ivtv utilities that can easily be changed. > > Are you perhaps aware of any other userspace applications that use that > ioctl? no. I think mythtv used it, but I doubt that the dropped support for the decoder will come back anytime. -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
