[Libva] [PATCH] Fix the issue in i965_UnlockSurface to lock it next time

yakui.zhao at intel.com yakui.zhao at intel.com
Tue Oct 9 06:19:54 PDT 2012

From: Zhao Yakui <yakui.zhao at intel.com>

It uses the variable of locked_image_id to check whether one surface is locked
or not. But as the locked_image_id is not assigned correctly, it causes that
it can't lock one surface next time although it calls the vaUnlockSurfaces.

Signed-off-by: Zhao Yakui <yakui.zhao at intel.com>
 src/i965_drv_video.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/i965_drv_video.c b/src/i965_drv_video.c
index 8a99e43..6c3aac4 100755
--- a/src/i965_drv_video.c
+++ b/src/i965_drv_video.c
@@ -3644,6 +3644,7 @@ i965_UnlockSurface(
     locked_img->image.image_id = VA_INVALID_ID;
+    obj_surface->locked_image_id = VA_INVALID_ID;
     return vaStatus;

More information about the Libva mailing list