On Tue, Jul 7, 2015 at 12:11 PM, Anuj Phogat wrote:
> On Tue, Jul 7, 2015 at 2:35 AM, Kenneth Graunke wrote:
>> On Tuesday, June 23, 2015 01:23:05 PM Anuj Phogat wrote:
>>> In case of I915_TILING_{X,Y} we need to pass tiling format to libdrm
>>> using drm_intel_bo_alloc_tiled(). But, In case of Y
On Tue, Jul 7, 2015 at 2:35 AM, Kenneth Graunke wrote:
> On Tuesday, June 23, 2015 01:23:05 PM Anuj Phogat wrote:
>> In case of I915_TILING_{X,Y} we need to pass tiling format to libdrm
>> using drm_intel_bo_alloc_tiled(). But, In case of YF/YS tiled buffers
>> libdrm need not know about the tilin
On Tuesday, June 23, 2015 01:23:05 PM Anuj Phogat wrote:
> In case of I915_TILING_{X,Y} we need to pass tiling format to libdrm
> using drm_intel_bo_alloc_tiled(). But, In case of YF/YS tiled buffers
> libdrm need not know about the tiling format because these buffers
> don't have hardware support
On Tue, Jun 23, 2015 at 01:23:05PM -0700, Anuj Phogat wrote:
> In case of I915_TILING_{X,Y} we need to pass tiling format to libdrm
> using drm_intel_bo_alloc_tiled(). But, In case of YF/YS tiled buffers
> libdrm need not know about the tiling format because these buffers
> don't have hardware supp
In case of I915_TILING_{X,Y} we need to pass tiling format to libdrm
using drm_intel_bo_alloc_tiled(). But, In case of YF/YS tiled buffers
libdrm need not know about the tiling format because these buffers
don't have hardware support to be tiled or detiled through a fenced
region. libdrm still need
