lineage-rockchip/android_external_minigbm
1
0
Fork 0
Code Activity Actions

minigbm: virtio-gpu: Remove offset log message

Browse source 
When running the Zoom Android client, "Non-zero transfer offset" was
printed in the logs. We now know for sure that we encounter this case in
the wild, thus removing the log message.

BUG=none
TEST=build minigbm manually

Change-Id: I1a536df50996e5218548fb097543566affa9af3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/minigbm/+/2255931
Tested-by: Matthias Springer <springerm@chromium.org>
Auto-Submit: Matthias Springer <springerm@chromium.org>
Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>
Commit-Queue: Matthias Springer <springerm@chromium.org>
This commit is contained in:
Matthias Springer 2020-06-22 10:05:22 +09:00 • committed by Commit Bot
parent fd8b8abd7f
commit 5a496e3df3
1 changed files with 0 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
virtio_gpu.c
View file

@ -423,8 +423,6 @@ static int virtio_gpu_bo_invalidate(struct bo *bo, struct mapping *mapping)
xfer.box.d = 1;
if (mapping->rect.x || mapping->rect.y) {
drv_log("Non-zero transfer offset\n");
/*
* virglrenderer uses the box parameters and assumes that offset == 0 for planar
* images
@ -488,7 +486,6 @@ static int virtio_gpu_bo_flush(struct bo *bo, struct mapping *mapping)
xfer.box.d = 1;
if (mapping->rect.x || mapping->rect.y) {
drv_log("Non-zero transfer offset\n");
/*
* virglrenderer uses the box parameters and assumes that offset == 0 for planar
* images