Hi Phillip, On Mon, May 13, 2013 at 06:03:38PM +0000, Phillip Norisez wrote: > Hans, > > I fear that in my ignorance of V4L2, I have backed my client into a > corner, so to speak. I am developing embedded Linux firmware for boards > intended to driver video sensors within a medical device. As such, tried > and true versions of everything on board are preferred, even if they are > not cutting edge. Applying this philosophy has gotten me into the > situation where I am committed, for first human use, to a 2.6.37 kernel > which does not have media controller v4l2, only int device. Hence my > question about back-porting drivers, and the programming differences. I > hope that clears up my situation for you. If a patch exists to make the > v4l2 on a 2.6.37 kernel into a media controller version, I am unaware of > it, though I have not conducted a search for it (I will as soon as I > finish this e-mail). To amend what Hans already told you, V4L2 int device has nothing to do with Media controller. What comes closest is V4L2 subdev interface which is part of your kernel. If you wish to use V4L2 subdev in the user space (and Media controller), you'll need to backport patches from at least v2.6.39 which is the one where the two were merged. I'd really try to start with something closer to mainline if reliability is important: there may be issues in backporting patches, too. Just that the code hasn't been changed for a long time does not make it magically better. Often it's quite the contrary. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- 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
