XMir runs on Mir. It is a major achievement to replace Xorg with XMir. If it were trivial, why didn't Fedora or others ship with X-Wayland as default years ago? It would have been the best way to kickstart porting to Wayland.
Posted Oct 2, 2013 17:04 UTC (Wed) by rsidd (subscriber, #2582)
[Link]
I assume you read it too, as well as the comments? There is a benefit to pushing (Mir/Wayland) out to users, even if they are using X(Mir/Wayland) to actually run their programs, and even if Xmir is not very different at this point from Xorg. Apart from wider testing of Mir itself, several other points are brought up in the comments.
No Mir by default in Ubuntu 13.10
Posted Oct 2, 2013 17:46 UTC (Wed) by tuna (guest, #44480)
[Link]
The only point I found in the comment was that it would be technically possible to have better VT switching, but that is not enabled in the current Mir/XMir setup.
Did you find something else?
No Mir by default in Ubuntu 13.10
Posted Oct 2, 2013 21:31 UTC (Wed) by drag (subscriber, #31333)
[Link]
> XMir runs on Mir. It is a major achievement to replace Xorg with XMir.
It's a bit old article, but I doubt a huge amount has changed.
No Mir by default in Ubuntu 13.10
Posted Oct 2, 2013 22:09 UTC (Wed) by mjg59 (subscriber, #23239)
[Link]
Not really. XMir is a Mir client, it depends on there being a Mir server process running. It just doesn't use that Mir server for performing drawing operations.
No Mir by default in Ubuntu 13.10
Posted Oct 6, 2013 12:01 UTC (Sun) by krake (subscriber, #55996)
[Link]
> XMir runs on Mir. It is a major achievement to replace Xorg with XMir.
It would be a major achievement if it had been achieved :)
You might have missed it but a short while back there was a huge flamefest because some XMir specific patches were removed from a Xorg driver.
Those patches wouldn't be necessary if XMIr ran on Mir due to Mir doing the actual input/output hardware/driver access.
