The way to Wayland: Preparing for life After X
Posted Nov 20, 2010 20:45 UTC (Sat) by quotemstr
In reply to: The way to Wayland: Preparing for life After X
Parent article: The way to Wayland: Preparing for life After X
Tearing can be solve not too badly with compositor
So you concede that tearing can be fixed within the X protocol.
please feel free to show me how to do it
You can do it with a novel technique called double buffering
. I mean, it was only invented in the 1980s: you may not have heard of it yet.
app->toolkit->render window(gtk/qt/cairo ...)->upload to X as a pixmap (memcpy new buffer allocation + others overhead)->compositor use it has a texture->screen
Cairo and other toolkits can render directly using XRENDER or OpenGL. The XRENDER and OpenGL operations are sent symbolically to the X server, which then hands them off directly to the GPU. There's no client-side pixmap and memcpy involved. You're either disingenuous or ignorant.
X is painfull to accelerate and even more to get it righ
Boo hoo, programming is hard! Let's burn the place down instead.
wrote driver to truely use GPU with X
What specific operations that are not accelerated today would be accelerated under your proposed architecture?
i prefer writing a GL driver than an X driver
Your statement is nonsense. What's the difference? When writing an X driver, you don't have to care about it being for X per se. A graphics driver deals with the same primitives in any environment: mode setting and acceleration. That's why nVidia can use the same codebase for its drivers on all platforms.
if all X people says that they want wayland
If that's the case, then the X people have lost their minds.
to post comments)