I have a more radical sugestion for legacy X support, more due to the experience from the X11 server built from scratch for Android tablets, which was written in Dalvik Java and SurfaceFliger API, and it's driveless, that's mean it don't need any Xorg drivers to work. The main backwards is the reduced compatibility with window toolkits, and some advanced X engines like Compiz would not be compatible at all. In real word use, the X emulator for Android was used to the unofficial port of OpenOffice for Android.
Instead to load a full X server in top of other graphic server, with all legacy stuff loaded, why not use the new Mir API directly and write a X11 driveless pseudo-server from stratch to start the X programs ? That's my fair opinion, and I think is the most stable option to legacy programs. For more information, I share the project homepage: http://code.google.com/p/android-xserver/
Power management, mobile and firmware developer on Linux. Security developer at nvidia. Ex-biologist. Content here should not be interpreted as the opinion of my employer. Also on Mastodon and Bluesky.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
A radical sugestion: create a xlib driveless compatibility layer from scratch
Date: 2013-10-17 11:33 am (UTC)The main backwards is the reduced compatibility with window toolkits, and some advanced X engines like Compiz would not be compatible at all.
In real word use, the X emulator for Android was used to the unofficial port of OpenOffice for Android.
Instead to load a full X server in top of other graphic server, with all legacy stuff loaded, why not use the new Mir API directly and write a X11 driveless pseudo-server from stratch to start the X programs ?
That's my fair opinion, and I think is the most stable option to legacy programs.
For more information, I share the project homepage:
http://code.google.com/p/android-xserver/