What to do now after Xgl and Xegl are gone....

[Adam Jackson]

On Fri, 2009-06-12 at 12:33 +0200, David Jander wrote:
> Hello,
> 
> We are developing an embedded-linux system that has a TFT LCD display and 
> should be able to run different desktop-linux applications using mostly the 
> GTK+ toolkit on top of the X.org Xserver.
> Right now we are using kdrive (xserver from latest git) with its fbdev driver, 
> but as it seems we will need Xcomposite (with hardware-acceleration). I have 
> been searching for quite a while now, but can't seem to find a clear hint as 
> to how to accomplish this with current X.org technology.
> Our hardware platform (Freescale MPC5121e processor) has a PowerVR MBX 
> graphics core that comes with OpenGL-ES library and EGL support. That way I 
> came to the conclusion that Xegl might be an option.... but Xegl is dead.
> What now? 
> I don't fear hacking Xserver or driver source-code to get something working on 
> a strange platform, but where should I begin? I don't have DRI2 drivers, nor 
> GLX libraries.... just (closed-source) Khronos OpenGL-ES-1.1 and EGL... and a 
> linux-framebuffer device, and I want an X-server with Xcomposite support.

Composite isn't a rendering API.  In itself, it is not something you can
hardware-accelerate.  Your compositing manager will use some rendering
API or other, and _that_ could be accelerated or not.

You probably want to start with something like the Xorg fbdev driver and
then start bolting on acceleration paths that call down into the EGL
driver.  Getting that to interact well with GLX clients should be
entertaining.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.x.org/archives/xorg-devel/attachments/20090615/5dd06388/attachment.pgp