On Wed, 2010-07-14 at 00:38 +0200, ext 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).
That's right. You could write a new backend for mcompositor, using QGraphicsView or Mesa-like library for software rendering. > 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. ;) Hardware acceleration is needed for speed, of course. And we can also avoid making a copy of the application window contents for compositing with some server-side buffer magic. -Kimmo > 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. > > > > > 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
