| Age | Commit message (Collapse) | Author |
|---|
|
With glyphs sitting in per-glyph pixmaps, there's no reason to use the CPU
to move them to the cache pixmap, and lots of reasons to use the accelerator.
Signed-off-by: Keith Packard <keithp@keithp.com>
(cherry picked from commit fe08b81d0f5d6f96e0124e6286bd24aba6e140ad)
(also includes revert from fe08b81d0f5d6f96e0124e6286bd24aba6e140ad)
(and revert from from 78a60e1b66fe2e8449702dd43d9b062d279af8f1)
The reverts simply eliminate some unrelated changes accidentally included
with the first commit.
|
|
|
|
Without this, rendering component-alpha glyphs may break without a mask.
Bug #19534. Ported from fix by Michel Dänzer <daenzer@vmware.com> in
xserver commit 639f289dcdbe00a516820f573c01a8339e120ed4
|
|
We can get a case with gnome-terminal + links, where we get two arrays
of glyphs all with 0 width and 0 heights in them. If this happens
we manage to get to this case without any buffer setup and segfault.
(cherry picked from commit 717c7492a0f6ba3fb3eabda33515881eef314155)
|
|
GCC isn't smart enough to analyze the control flow and figure out that
these are false positives, but initializing them shouldn't hurt, so work
around it.
|
|
|
|
This eliminates the cost of EXA migration management while providing full
pixmap allocation control to the driver. The goal is to make something
useful for UMA drivers.
|
