[Wayland-bugs] [Bug 93094] Protocol: colored buffer
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Nov 29 05:34:22 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=93094
--- Comment #8 from phizh <phizhed at gmail.com> ---
(In reply to Pekka Paalanen from comment #7)
> With wl_viewport, the compositor does *not* create any kind of buffer of
> size NxM. During compositor repaint, it will just fill the given size with
> the given color in the final framebuffer, which is the cheapest possible
> operation. There is no memory reserved for the NxM image at all.
>
> Why is that not what you want?
>
> Do you want to do something with the buffer in the client *after* it has
> been filled with the given color? If so, what do you want to do?
>> in the final framebuffer, which is the cheapest possible operation
My goal is to slow resize the window, filled in one color, and have a 0% CPU
load. Not understanding the way it works from the inside, I was trying to think
optimization based on API abstractions like wl_buffer and wl_shm_pool. Now we
have to wait wl_viewport support from toolkits..
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20151129/9f2f691a/attachment.html>
More information about the wayland-bugs
mailing list