[Interest] Qt5/OMAP4/EGLFS: Strange animation behaviour
thomas.senyk at pelagicore.com
Wed Nov 21 15:39:49 CET 2012
On Wed, November 21, 2012 09:17:14 AM Stephan Kanthak wrote:
> Hi Samuel,
> On 11/21/2012 08:43 AM, Samuel Rødal wrote:
> > On 11/20/2012 09:12 PM, Stephan Kanthak wrote:
> >> Hi,
> >> one final word to this list on my fix. I think that the fix I did to Qt5
> >> is not in good shape to be integrated. My fix interfaces directly with
> >> OMAP-specific ioctl's to a linux framebuffer device in code that is
> >> generic to all egl platforms. I'll continue to discuss this first with
> >> Prabindh from TI to find out more about where to best fix this. Maybe
> >> I'm also not using the TI driver to its best, but I already tried hard
> >> to understand the problem in more general.
> > For eglfs we have a solution for device / device-family specific
> > work-arounds, they're the QEglFSHooks, in
> > src/plugins/platforms/eglfs/qeglfshooks.h
> > beforeSwapBuffers() and/or afterSwapBuffers() could be added to the
> > hooks for instance, so that you could put your work-around in a file
> > specified by a custom mkspec.
> > As an example, ee mkspecs/devices/linux-rasp-pi-g++ for the hooks used
> > on the raspberry pi, qeglfshooks_pi.cpp, enabled by setting the
> > EGLFS_PLATFORM_HOOKS_SOURCES variable in the qmake.conf in the same
> > directory.
> That's indeed a good suggestion. I already noticed those hooks when I
> inspected the mkspecs files in linux-rasp-pi-g++, but yet didn't take
> the time to fully understand the concept. But it does make sense to me now.
> In order to make that lean & clean, I assume it's best to also create a
> separate directory for my config in mkspecs/devices, right? So far, I
> was using the default linux-arm-gnueabi-g++.
yep, as Samuel said.
If you need help with this, let me know.
I got a pandaboard and I've written device-mkspecs and qeglfshooks.
> Interest mailing list
> Interest at qt-project.org
More information about the Interest