Hi Guennadi, On Thursday 10 March 2011 16:36:36 Guennadi Liakhovetski wrote: > On Thu, 10 Mar 2011, javier Martin wrote: > > Hi, > > we are going to receive a Beagleaboard xM board in a couple of days. > > One of the things we would like to test is video capture. > > > > When it comes to the DM3730 SoC, it seems the support is given through > > these two files: > > http://lxr.linux.no/#linux+v2.6.37.3/drivers/media/video/davinci/vpfe_cap > > ture.c --> to capture from sensor > > http://lxr.linux.no/#linux+v2.6.37.3/drivers/media/video/davinci/dm644x_c > > cdc.c --> to convert from Bayer RGB to YUV > > > > On the other hand, the sensor we would like to test is mt9p031 which > > comes with LI-5M03, a module that can be attached to Beagleboard xM > > directly: > > https://www.leopardimaging.com/Beagle_Board_xM_Camera.html > > > > By a lot of googling I found this version of a driver for mt9p031 > > which is developed by Guennadi Liakhovetski. It is located in a 2.6.32 > > based branch: > That's a back-port of my patches by a "third party";) Probably, never > actually tested. > > > http://arago-project.org/git/projects/?p=linux-davinci.git;a=blob;f=drive > > rs/media/video/mt9p031.c;h=66b5e54d0368052bf76796aa846e9464e42204bb;hb=HE > > AD > > > > The question is, what does this driver lack for not entering into > > mainline? We would be very interested on helping it make it. > > I'm waiting for media-controller to be pulled by Mauro (I think, they > needed some updates by Laurent, not sure about the current state). As soon > as that's in the mainline, I'll try to find some time to update, clean up > and submit my beagle-board and mt9p031 patches. I'll submit Aptina sensor drivers as well. I'll review your patches. I'm curious about the Beagleboard code, as the camera module is an expansion board you obviously can't hardcode support for it in the board file. How do you plan to handle that ? -- Regards, Laurent Pinchart -- 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
