[EMAIL PROTECTED] wrote: > Sriram, > > How did you manage to get a hold of the 2.6.18 source? > Contacts inside TI and montavista have eluded to it but they said it's not > ready for distrubution and it doesn't show up on Montavista's list. > I'd like to see what they've done with the FBDev driver... someone from TES > electronic solutions said that the current FBDev driver has a lot of > performance issues and the new one from Montavista is supposed to fix all > of that.
The 2.6.10 davincifb is working fine. What kind of performance issues? :) > I had a chance to play around with the davncifb patch and I missed a few > more IOCTLs so I'll post when I can run dfbinfo without it complaining... > stay tuned. > > I also created a shell script that maps all of the arm_v5t_le-* tools to > the now supported standard of the platform triplet > armv5tl-montavista-linuxeabi so autogen and configure can actually find the > proper tools. I'll send that one also. > > If we're able to find the either the source or the binary for the driver, I > can incorporate that into the kernel module patch so that we can build from > within the kernel tree, that is if I knew where it was. > > It's probably easier for now to just include the binary image if we can > find or make it because it would require the TI c64x+ code generation tools > and I don't think that the kernel make will call them properly. Besides, it > would be easier to just throw the project in CodeComposer and generate a > binary. The firmware sources will most likely be released under GPL soon. I'm not sure if we are allowed to send binaries built from Code Composer. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
