Hans, Thanks, Vaibhav Hiremath > -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Trilok Soni > Sent: Monday, November 24, 2008 2:13 PM > To: Hans Verkuil > Cc: video4linux-list@xxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx; > davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH 2/2] TVP514x V4L int device driver support > > Hi Hans, > > > > > The v4l2-int-device.h stuff should never have been added. Ditto > for > > parts of the soc-camera framework that duplicates v4l2-int- > device.h. My > > new v4l2_subdev support will replace the three methods of using > i2c > > devices (or similar) that are currently in use. It's exactly to > reduce > > the confusion that I'm working on this. > > > > It's been discussed before on the v4l mailinglist and the relevant > > developers are aware of this. It's almost finished, just need to > track > > down a single remaining oops. > > Right, I will wait for your updates. > > I am planning to send omap24xxcam and ov9640 drivers (now deleted) > available from linux-omap tree after syncing them with latest > linux-2.6.x tree, and the whole driver and the sensor is written > using > v4l2-int-device framework. I am going to send it anyway, so that it > can have some review comments. > [Hiremath, Vaibhav] Is your current development accessible through linuxtv.org? Can you share it with us, so that we can have a look into it? Which driver you are migrating to new interface (which I can refer to as a sample)? Again I would like to know, how are we handling current drivers (soc-camera and v4l2-int)? > -- > ---Trilok Soni > http://triloksoni.wordpress.com > http://www.linkedin.com/in/triloksoni > -- > 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 -- 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