On 12/10/2012 11:31 AM, Stephan Kanthak wrote: > Hi all, > > I promised to get back on this, once Prabindh and I find out more about > the real issues: > > 1. I got this working cleanly for Qt5 + LinuxFB/EGL + OMAP4 using (the > rather old) TI SGX driver release 4.04.00.03 by adding a > get_update_mode() callback to the appropriate panel driver in the kernel > (2.6.35.7). Thanks to Prabindh to point me in the right direction. > There's no fix needed for the OMAP4 SDP panel-taal.c driver in the > kernel, but all other panel drivers do need fixes! People working on a > similar track than me may have bumped into this same problem and should > inspect the appropriate panel driver code. Donald, if you tried the same > as me, it's definitely worth looking at the panel's driver, fix was > pretty simple. This also removed the need for any vsync user-level code > via ioctl, so not a single change needed for Qt5 (I still have to try > OMAP4 video acceleration in QtMultimedia). > > 2. Android driver SDKs seem to not test for the panel driver's update > mode. That's what confused me initially as on Android and the original > Kindle Fire everything is smooth. The logic there is hard-wired and in > my view the same behaviour could be applied to the non-Android SDK. This > is an alternative way of fixing the problem, but I personally prefer > fixing the kernel's panel drivers. In case TI does not want to publish a > new driver for OMAP4 to support LinuxFB/EGL, it seems the Linux > community can continue to maintain this separately as the SDK is > licensed under CC license. I'm strictly not volunteering here, but TI > may have reasons to not help us much on this. > > 3. for LinuxFB/EGL (and that also includes Qt5 to some extent) it's > impossible to move to a newer version of the DDK, as Ubuntu/Linaro only > releases the DRM part of the driver and I couldn't get Android drivers > working at all. I suspect it's mostly due to absolute paths being > compiled into all libs, so /system/..., but I failed at all attempts to > patch them. Finally there could also be linkage problems that I didn't > see yet. > > All in all my conclusions are that you can get this working, but only > with some considerable effort on a bit outdated software packages. I can > document what I did somewhere and I most likely will when I find time > for that. But there's still some bitter taste left as the main problem > seems to be due to not much maintained driver SDK / kernel code. I would > love to move on to the latest driver version, but LinuxFB/EGL is simply > not supported by the non-Android SDKs anymore. So, I may as well > continue to check the Android SDK path again.
Which Android SDK part would that be? You might be interested in http://qt-project.org/wiki/Korhal -- Samuel _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest