From 33fab30a1fafba82e18ff320471332e8a8a453f2 Mon Sep 17 00:00:00 2001 From: Alexander Boettcher Date: Wed, 2 Apr 2025 13:57:38 +0200 Subject: [PATCH] intel/display: use phys resolution for capture In the "" case, only a subset of the actual framebuffer was (intentionally) captured to reduce cpu and memory bandwith. The new blit tool however requires, by now, that the capture size must be identical to the framebuffer in use. Issue #5501 --- repos/pc/src/driver/framebuffer/intel/pc/main.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/repos/pc/src/driver/framebuffer/intel/pc/main.cc b/repos/pc/src/driver/framebuffer/intel/pc/main.cc index b1c9b5b772..f583840501 100644 --- a/repos/pc/src/driver/framebuffer/intel/pc/main.cc +++ b/repos/pc/src/driver/framebuffer/intel/pc/main.cc @@ -569,7 +569,7 @@ void lx_emul_i915_framebuffer_ready(unsigned const connector_id, drv.ids.apply(id, [&](Connector &conn) { - Capture::Area const area (xres, yres); + Capture::Area const area (phys_width, phys_height); Capture::Area const area_phys(phys_width, phys_height); bool const merge = Capture::Connection::Label(conn_name) == "mirror_capture";