Hi Muralidharan, 2010/6/25, Karicheri, Muralidharan <m-kariche...@ti.com>: > Raffaele, > > >>I guess you are developing V4L2 without changing the DM365 VPFE porting, >> for example I'm seeing the isif.c file equal to the one in Kevin tree. > > The vpfe driver is already upstream though it doesn’t have all the > functionality that we have in Arago tree. That is why you are seing it in > Kevin’s tree. > >>Also I don't see any info about VPFE in the readme. > > That is because this branch is for adding just vpbe v4l2 display support.
ok > >>Anyway I'm going on trying to understand how to implement: > > Are you willing to take up this activity to upstream VPBE fb display driver? > If so, let me know so that I can discuss this with the TI’s development team > and get back to you on this. I have some version of vpbe_fb.c and vpbe_fb.h > that partially builds with the vpbe display controller. But some > functionality to set mode is missing. It's ok, please send me your work. Let me have also your .config, so I can start from something clear. If you also some other guidelines to implement it let me know. Thanks, Raffaele. > > Murali Karicheri > Software Design Engineer > Texas Instruments Inc. > Germantown, MD 20874 > email: m-kariche...@ti.com > > ________________________________ > From: Raffaele Recalcati [mailto:lamiapost...@gmail.com] > Sent: Thursday, June 24, 2010 11:29 AM > To: Karicheri, Muralidharan > Cc: Kevin Hilman; davide.bonfa...@bticino.it; > davinci-linux-open-source@linux.davincidsp.com; Selvamani, Senthilnathan > Subject: Re: RE: [PATCH 14/14] davinci: video: davincifb Parallel RBG LCD > management > > Hi Muralidharan, > > 2010/6/17 Karicheri, Muralidharan > <m-kariche...@ti.com<mailto:m-kariche...@ti.com>> > Raffaele, > > You got the readme.txt right! > > Arago tree has the latest video drivers for DM365. But this is a temporary > staging tree that has all of the video > drivers up ported from the MV kernel. Some of these drivers (vpfe capture on > DM6446, DM355, DM365 > and vpif capture and display on DM646x) are already up ported to mainline > kernel and are available on > Kevin’s tree as well (got merged via mainline kernel). devel_2_6_35rc2 > branch is used for up porting > the display driver. > > I guess you are developing V4L2 without changing the DM365 VPFE porting, for > example I'm seeing the isif.c file equal to the one in Kevin tree. > Also I don't see any info about VPFE in the readme. > Anyway I'm going on trying to understand how to implement: > > Frame buffer display device driver > drivers/media/video/davinci/vpbe_fb.c > drivers/media/video/davinci/vpbe_fb.h > > First of all, I'm compiling with: > commit 01fcd84c3a781063038e6a27dd7e1cd8dc9695da > Author: Muralidharan Karicheri > <m-kariche...@ti.com<mailto:m-kariche...@ti.com>> > Date: Thu Jun 17 15:13:26 2010 -0400 > > and I have some compiling errors doing these commands: > > export ARCH=arm > export > CROSS_COMPILE=/home/sources/NEXTGEN/M/toolc/arm-2009q1/bin/arm-none-linux-gnueabi- > make mrproper > make davinci_all_defconfig > make uImage > > can you please give me a good .config so I can start in a clean way? > > thanks, > Raffaele > > -- www.opensurf.it _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
