Hey Robin,
Thanks for the reply, questions below:
Robin Burchell wrote:
Hi Eugene,
Excerpts from Eugene Seah's message of Tue Jul 13 23:33:25 +0100 2010:
Hi there,
I'm trying to get the UX working on another ARM device that does not
have the same SGX graphics chip that the N900/Beagleboard have. What's
limiting the UX/mcompositor from working with non-hw accelerated X11?
MCompositor requires a GLX/EGL backend to do rendering. I briefly (<5 mins)
looked into whether a software backend would be possible, as GLX/EGL
backends are thankfully fairly seperated from everything else, but I didn't
really reach a conclusion. It may be possible (if slow).
MCompositor works this way as it composites thumbnails of running applications
or something along these lines. I haven't worked out precisely what it does as I
haven't had the time to sit down and actually get it running. ;)
The rest of the UX is usable without GL, as libmeegotouch does not require it -
with newest libmeegotouch from master (I'm not sure if it's updated in MeeGo
yet), you have a patch by me which looks for the environment variable
M_USE_SOFTWARE_RENDERING to use software rendering, or alternatively, you can
run applications and pass -software as a parameter.
I guess I don't understand the UX framework well enough to get that. How
do I use "the rest of the UX" without running mcompositor? My impression
was that MCompositor was the window manager that and was critical for
anything else running on the UX? Any diagrams/docs you could point me to
would be helpful.
Thanks.
Thanks.
Hope this helps,
--
Robin Burchell
http://rburchell.com
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
