Siarhei Siamashka siarhei.siamas...@gmail.com writes:
write-through cache for it (with a simple kernel patch) improves scrolling
and moving windows performance by 4x-5x factor (unless shadow framebuffer is
used, which is also not good for performance).
What is the issue with the shadow
On Mon, 2009-10-26 at 17:52 +0100, Soeren Sandmann wrote:
write-through cache for it (with a simple kernel patch) improves scrolling
and moving windows performance by 4x-5x factor (unless shadow framebuffer is
used, which is also not good for performance).
What is the issue with the
On Friday 23 October 2009, Koen Kooi wrote:
I'm not sure about pixman_gc_t since most of the needed operations are just
simple copies. What about starting with just introducing a variant
of 'pixman_blt' which is overlapping aware?
I created a work-in-progress branch with 'pixman_blt'
Siarhei Siamashka siarhei.siamas...@gmail.com writes:
First introduce something like 'pixman_init' function. Right now CPU type
detection is done on the first call to the function. It introduces some
minor overhead by having an extra pointer check on each function call.
Another problem is
On Thursday 04 June 2009, Soeren Sandmann wrote:
Siarhei Siamashka siarhei.siamas...@gmail.com writes:
What kind of guarantees (or the lack of) pixman and XRender are supposed
to provide when dealing with overlapping parts of images?
(Adding xorg-devel). See this thread:
Cairo can do a transformation when copying (like a rotation or scale). I
think it is best to say that no guarantee is made when the source and
destination intersect. You could say it works if there is no
transformation other than integer translation but it seems a little
artificial to me. It
Siarhei Siamashka siarhei.siamas...@gmail.com writes:
What kind of guarantees (or the lack of) pixman and XRender are supposed to
provide when dealing with overlapping parts of images?
(Adding xorg-devel). See this thread:
