[Koying]

My question was simply about the use of direct texture and the associated performance improvement.
But OK I have just been able to try your version and obviously your cpu load issue is gone (it seems to be very similar to the V4L version)
Have you also been able to give it a try for android ?

Oh right
No, I haven't started Android work, yet. There will be specific work to be done for this, e.g. decouple CEGLNativeTypeIMX from CDVDVideoCodecIMX (android has its own CEGLNativeType, CEGLNativeTypeAndroid).

Apart from the deinterlacing issue you mentioned, I can't have a good VSYNC in spite of defining the environment variable
export FB_MULTI_BUFFER=2
before launching xbmc. Have you configured something else ?

Did you enable vsync in System-Video? I suggest to try with "when playing video" only, as I noticed some deadlocks when doing the eglSwapBuffers.

Also, as you are a xbmc team member, maybe you can help with upstream this imx6 port ?

Sure.
The work won't be merged for Gotham, as we are in feature-freeze, but that does not prevent to create a "WIP" PR to make it semi-official.

I suggest to create a topical organization in github, create an xbmc fork under this umbrella and apply the imx patches. This way, you can have multiple devs working on imx while leaving your personal branches alone.
That would be the base for the PR.

Now you have to decide whether you want the V4L or EGL version to be merged...

At last for the DMA issue, I have lots of reports but on my side, I have really very rare issue with my main configuration (utilite pro).

Actually, running xbmc doesn't cause problems. The DMA is not fragmented neither at runtime nor at exit.
As I said, in my case, it is actually compiling on the device that fragments it