https://bugs.freedesktop.org/show_bug.cgi?id=93094
--- Comment #3 from Pekka Paalanen <[email protected]> --- I don't understand why moving the cursor would cause CPU load. We need a lot more information about the implementations involved to reply to that. It sounds like something (the application?) is redrawing or posting damage when there is none. But you talk about an X application. Is this CPU usage issue specific to Xwayland? Now, assuming you use case is valid... For a solid color buffer, we could add what you propose, but there is already protocol to do the equivalent and consuming just one pixel of storage: allocate a 1x1 wl_buffer, e.g. from wl_shm, and paint the one pixel with the color you want. When attaching it to a wl_surface, use wl_viewport to scale that one pixel up to any size you want. The extension for wl_viewport is not stable yet, but should be quite soon. You can follow it in bug #83918. If this is really about Xwayland, it seems you have three separate issues filed here: - the CPU consumption with Xwayland - Wayland protocol for solid color buffers - making Xwayland use the solid color buffers (if even possible) Is this correct? Btw. it is allowed to attach the same wl_buffer to several wl_surfaces at the same time, but there is a caveat: bug #75303 -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
