From b99e8b022c4aaf586ae49e0eb597f0c34bc0e165 Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Thu, 18 Feb 2016 13:53:07 +0000 Subject: sna: Use dirtyfb for fallback direct rendering The preferred solution when direct rendering is too costly is to render into the backbuffer and flip. However, if the user insists, we need to tell the kernel when to flush the scanout due to direct rendering. Signed-off-by: Chris Wilson --- src/sna/kgem.h | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/sna/kgem.h') diff --git a/src/sna/kgem.h b/src/sna/kgem.h index 6cf877cf..8bea755a 100644 --- a/src/sna/kgem.h +++ b/src/sna/kgem.h @@ -189,6 +189,7 @@ struct kgem { uint32_t has_no_reloc :1; uint32_t has_handle_lut :1; uint32_t has_wc_mmap :1; + uint32_t has_dirtyfb :1; uint32_t can_fence :1; uint32_t can_blt_cpu :1; @@ -196,6 +197,8 @@ struct kgem { uint32_t can_render_y :1; uint32_t can_scanout_y :1; + uint32_t needs_dirtyfb :1; + uint16_t fence_max; uint16_t half_cpu_cache_pages; uint32_t aperture_total, aperture_high, aperture_low, aperture_mappable, aperture_fenceable; -- cgit v1.2.3