[wolfgar]

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.

Yes I have : I can't manage to get rid of a little flickering from time to time. Which GPU libs do you use ? Maybe they are the key ...

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...

OK, this week, I will create this organization, will fork xbmc and push imx patches.
When it is ready how can I communicate broader without opening a PR ?
For the version It should be EGL I guess : I will not stupidly advertize V4L against the global xbmc approach for rendering...
For now I have 2 concerns :
- vsync still not perfect for me but if you say it is ok for you then I have to find what's wrong with my env
- deinterlacing : We have to renounce to using IPU deinterlacing engine otherwise we are back to a imx specific mechanism I fear...
(There are also the freezes you mentioned)

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

Did you use a usb drive to compile ?

Regards
Stephan