Originally posted by valeriodean
View Post
Announcement
Collapse
No announcement yet.
We Have Mir & Wayland, But There Still Could Be X12
Collapse
X
-
Originally posted by ryao View PostThat is your assumption.
Originally posted by ryao View PostX11 fans such as myself do not care if Wayland could be made to work for our use cases. We do not see the need to replace X11 and we will continue using it for years to come. You are not going to replace the display server on our machines. To put it simply, read xkcd #927:
http://xkcd.com/927/
Comment
-
Originally posted by mrugiero View PostOn the other hand, rendering toolkits could use acceleration, too, either with an agnostic, specialized 2D driver (kind of DDX, but generic for any toolkit) or via OpenGL, so this possible hog of the CPU sounds like a temporary problem, if any.
Comment
-
Originally posted by mrugiero View PostIt shouldn't target Wayland, as Wayland doesn't render. It should target toolkits, which are the ones doing this work.
If Wayland applications will hog CPU and GPU, it will also increase power consumption and decrease battery life on mobile devices.Last edited by JS987; 07 October 2013, 02:05 PM.
Comment
-
Originally posted by JS987 View PostIntel / AMD / NVIDIA haven't announced they are working on or planning 2D driver for e.g. GTK and Qt on Wayland AFAIK. There are applications which use neither GTK nor Qt. 2D driver on X is toolkit independent and is running in different process than application.
If Wayland applications will hog CPU and GPU, it will also increase power consumption and decrease battery life on mobile devices.
Those applications which use no toolkit shouldn't exist on Wayland, since Wayland doesn't implement the rendering operations. If they exist, they will be manually doing any render, and this means they would be the ones who think how to accelerate it.
Also, I don't see how they would "hog CPU and GPU". If anything, they will hog only one of them, because either they will be unaccelerated (hogging CPU, but not touching GPU) or accelerated (opposite situation).
Comment
-
Originally posted by JS987 View PostIntel / AMD / NVIDIA haven't announced they are working on or planning 2D driver for e.g. GTK and Qt on Wayland AFAIK. There are applications which use neither GTK nor Qt. 2D driver on X is toolkit independent and is running in different process than application.
If Wayland applications will hog CPU and GPU, it will also increase power consumption and decrease battery life on mobile devices.
If it's below the toolkits, and implemented by all drivers, it will end up being some "Khronos group" API style, especially if not "NIH".
Comment
-
Originally posted by LinuxGamer View Postwow you don't get it at all do you? the only Way to Fix X11 is to fully gut it remove all the old code and write all new code it was faster just to write Wayland and by doing a rewrite to Xorg this way brings in way to many politics Look how pissy the Xorg developers are over DRI3 (it was like them gentoo guys over systemd or was that NIH syndrome) also the X.Org Foundation said wayland is a umbrella of them.
Comment
-
Originally posted by valeriodean View PostX11 fans?
ROFL.
I know there are fan clubs for every stupid thing out there, but why to be a fan of a display server full of flicker, flashes and tearing defects? It's a mistery.
You do not see the need to replace X11, isn't it?
LOL, you can see all the reasons just watching your monitor.
I have no interest in replacing X11. It has worked well for me for years, and it has become a standard across all the UNIXsphere.
Comment
-
Originally posted by mrugiero View PostAFAIK, 2D driver on X is not toolkit independent, as it only works for calls for the toolkit embedded on X (xrender, IIRC). Other toolkits can call them, but they can avoid them, too, and just use OpenGL or whatever means they prefer.
Those applications which use no toolkit shouldn't exist on Wayland, since Wayland doesn't implement the rendering operations. If they exist, they will be manually doing any render, and this means they would be the ones who think how to accelerate it.
Also, I don't see how they would "hog CPU and GPU". If anything, they will hog only one of them, because either they will be unaccelerated (hogging CPU, but not touching GPU) or accelerated (opposite situation).
OpenGL applications can hog CPU and GPU at same time.
Comment
Comment