While PSR has problems with GTT mmaps, we're studying the possibility
of implementing a workaround for FBC that affects CPU and WC mmaps. So
prefer the BLT method since it behaves the same with both features.
Signed-off-by: Paulo Zanoni <paulo.r.zan...@intel.com>
---
tests/kms_frontbuffer_tracking.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/kms_frontbuffer_tracking.c b/tests/kms_frontbuffer_tracking.c
index 0ea1dde..363fe23 100644
--- a/tests/kms_frontbuffer_tracking.c
+++ b/tests/kms_frontbuffer_tracking.c
@@ -1081,7 +1081,7 @@ static void fill_fb_region(struct fb_region *region, enum
color ecolor)
{
uint32_t color = pick_color(region->fb, ecolor);
- igt_draw_rect_fb(drm.fd, NULL, NULL, region->fb, IGT_DRAW_MMAP_CPU,
+ igt_draw_rect_fb(drm.fd, drm.bufmgr, NULL, region->fb, IGT_DRAW_BLT,
region->x, region->y, region->w, region->h,
color);
}
@@ -3498,7 +3498,7 @@ int main(int argc, char *argv[])
if (t.pipes != PIPE_SINGLE ||
t.screen != SCREEN_PRIM ||
t.plane != PLANE_PRI ||
- t.method != IGT_DRAW_MMAP_CPU)
+ t.method != IGT_DRAW_BLT)
continue;
igt_subtest_f("%s-%s-scaledprimary",
feature_str(t.feature),
@@ -3511,7 +3511,7 @@ int main(int argc, char *argv[])
t.screen != SCREEN_PRIM ||
t.plane != PLANE_PRI ||
t.fbs != FBS_INDIVIDUAL ||
- t.method != IGT_DRAW_MMAP_CPU)
+ t.method != IGT_DRAW_BLT)
continue;
igt_subtest_f("%s-modesetfrombusy", feature_str(t.feature))
--
2.7.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
