Error: couldn't find RGB GLX visual or fbconfig
and glxgear gives
Error: couldn't get an RGB, Double-buffered visual
libglx.so seems to be properly loaded from X.org.log
Will try to file a bug report tomorrow if nothing comes out.
The problem with these new display servers is not the complexity in writing them. They are designed with the intention of not doing much at all, that is the whole point behind Wayland.
The difficulty is in coming up with a good protocol that is future-proof and widely agreed upon by the community so it can last a long while. That's one of the reasons why Wayland is taking so long, in addition to the fact that X is good enough (tm) for most people and most applications right now, so there is not much money being pumped into Wayland.
What Ubuntu did is take Wayland concepts shortly before the Wayland protocol was finalised, add their own changes without consulting anyone, then writing the server in-house (arguably the easiest part of the whole process). The result is a server nobody in the community wants to support, which is exclusive to Ubuntu, and Canonical will have to maintain compatibility patches for all relevant toolkits and libraries.
I cannot imagine Mir having any impact on the Linux ecosystem at all. Wayland, perhaps.
Not a bad hit for alpha/early software. Color my surprised.
Michael, there's a mistake on the 5th page:
It's not 1920x1080, it's 1600x900.Quote:
OpenArena 0.8.5, which is a rather CPU-limited game and doesn't even make use of GLSL, saw no performance difference at 800 x 600 but at 1920 x 1080, the old game saw its frame-rate drop by about 25% with going through XMir.
I'm personally not surprised by these results at all - Canonical got a head start since they decided to base this off of Android's code, to some degree anyway. As said before, a compatibility layer will always result in poorer performance, HOWEVER, that means worse performance compared to native. So for example, a game compiled to work for Wayland will perform better than the X version in Xwayland. But, Xwayland could still potentially perform better than X11. But considering how young Mir is, I'm not surprised it performed worse, and its performance loss is far from "what a shame, just kill it".
At this point I'm finding it a bit tough to figure out which display server will end up being the best replacement to X:
Pros of Mir over Wayland:
* MUCH faster development
* Supposed to get Android driver support
* A seemingly more devoted team
Pros way Wayland over Mir:
* Targets all DEs in mind
* Seems to be more thought-out in a technical standpoint
* Better multi-seat support
* A fully open source license
* Probably will be more light-weight in the end
already posted on Phoronix that Canonical plans to ship with Mir/XMir by default on Ubuntu 13.10.
So is Wayland:Quote:
Originally Posted by schmidtbag
Wayland utilizing Android GPU drivers on glibc based systems, Part 1
Wayland utilizing Android GPU drivers on glibc based systems, Part 2