Kenneth Graunke writes:
> If a region is larger than the estimated aperture size, we map/unmap it
> by copying with the BLT engine. Which means we can't use Y-tiling.
>
> Fixes Piglit max-texture-size and tex3d-maxsize, which regressed in my
> recent change to use Y-tiling by default on Gen6+.
On 04/10/2013 02:08 PM, Kenneth Graunke wrote:
If a region is larger than the estimated aperture size, we map/unmap it
by copying with the BLT engine. Which means we can't use Y-tiling.
Fixes Piglit max-texture-size and tex3d-maxsize, which regressed in my
recent change to use Y-tiling by defau
If a region is larger than the estimated aperture size, we map/unmap it
by copying with the BLT engine. Which means we can't use Y-tiling.
Fixes Piglit max-texture-size and tex3d-maxsize, which regressed in my
recent change to use Y-tiling by default on Gen6+. This was due to a
botched merge con
Kenneth Graunke writes:
> If a region is larger than the estimated aperture size, we map/unmap it
> by copying with the BLT engine. Which means we can't use Y-tiling.
>
> Fixes Piglit max-texture-size and tex3d-maxsize, which regressed in my
> recent change to use Y-tiling by default on Gen6+.
If a region is larger than the estimated aperture size, we map/unmap it
by copying with the BLT engine. Which means we can't use Y-tiling.
Fixes Piglit max-texture-size and tex3d-maxsize, which regressed in my
recent change to use Y-tiling by default on Gen6+. This was due to a
botched merge con
