On Mon, May 2, 2011 at 8:40 PM, Marcin Slusarz marcin.slus...@gmail.com wrote:
On Mon, May 02, 2011 at 03:11:00PM +0200, Daniel Vetter wrote:
On Mon, May 2, 2011 at 2:56 PM, Benjamin Franzke
benjaminfran...@googlemail.com wrote:
I think in i915g the CURSOR flag should be used in
On Sun, May 1, 2011 at 11:59 PM, Marcin Slusarz
marcin.slus...@gmail.com wrote:
We need to distinguish surfaces for mouse cursors from scanouts, because nv50
hardware display engine ignores tiling flags.
i915 seems to have similar needs, so fix it too.
For the i915g part:
Acked-by: Daniel
I think in i915g the CURSOR flag should be used in i9x5_scanout_layout
for the special case for cursors as well, instead of only checking
only pt-width0 == 64 pt-height0 == 64.
2011/5/2 Daniel Vetter dan...@ffwll.ch:
On Sun, May 1, 2011 at 11:59 PM, Marcin Slusarz
marcin.slus...@gmail.com
On Mon, May 2, 2011 at 2:56 PM, Benjamin Franzke
benjaminfran...@googlemail.com wrote:
I think in i915g the CURSOR flag should be used in i9x5_scanout_layout
for the special case for cursors as well, instead of only checking
only pt-width0 == 64 pt-height0 == 64.
Oops, so much for actually
We need to distinguish surfaces for mouse cursors from scanouts, because nv50
hardware display engine ignores tiling flags.
i915 seems to have similar needs, so fix it too.
---
src/gallium/drivers/i915/i915_resource_texture.c |6 +-
src/gallium/drivers/nv50/nv50_miptree.c | 11
