> > But in user space there is nothing changed having access to > > device and control them. > > As you know, subdev and int-device is all about how to bind > > interface(or host?) and device and make them communicated each other. > > But using subdev device driver with int-device supporting interface > > (or host) device driver? it won't make any communication. > > So if you are running out of time with your project, you'd better use > > old driver of TVP. Like TVP driver in kernel 2.6.28 I suppose. But if > > you have enough time and wanna be challenging, try to convert > > in-device based omap3 camera interface driver to subdev supporting > > one. > > Someone's got to do this. v4l2_subdev is the future and it has many > advantages over the older interfaces. The ability to be able to use the > same i2c driver in anything from USB webcams to PCI capture cards to > omap/davinci embedded platforms is very powerful. Hi, We have already this framework migration planned, but we haven't been able to do it, because we are still solving stability issues on the driver. I beg for your patience, and i hope i can get my hands on this pretty soon. I'll be updating my tree when i have something. Regards, Sergio-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
