On Wed, 18 Feb 2009 00:06:38 +0100 Hans Verkuil <hverkuil@xxxxxxxxx> wrote: > Especially companies like Texas Instruments that > are working on new v4l2 drivers for the embedded space (omap, davinci) are > quite annoyed and confused by all the backwards compatibility stuff that > we're dragging along. I find it much more important to cater to their needs > than to support a driver on an ancient kernel for some anonymous company. The i2c code or any other backported code shouldn't affect any new driver. For new drivers, they can just use 2.6.29-rc as reference and mark that the minimum required version for it is 2.6.30, at v4l/versions.txt. If the driver is for x86/x86_64, it generally makes sense to preserve the backward compat bits, to help users. However, in the specific case of TI development, for OMAP and similar drivers that are specific to some embedded architecture, and where a normal user will never need to test it for us, since the vendor is responsible for the driver, it is perfectly fine to update v4l/versions.txt for each new version that needs something for a newer API. Cheers, Mauro -- 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
