From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers Date: Mon, 16 Feb 2015 08:46:31 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0882824283==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id C19366E229 for ; Mon, 16 Feb 2015 00:46:31 -0800 (PST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0882824283== Content-Type: multipart/alternative; boundary="1424076391.1fBae0.10151"; charset="UTF-8" --1424076391.1fBae0.10151 Date: Mon, 16 Feb 2015 08:46:31 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=89164 Bug ID: 89164 Summary: AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers Product: Mesa Version: 10.4 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: andreas.pokorny@gmail.com QA Contact: dri-devel@lists.freedesktop.org When creating a cursor with GBM_BO_USE_CURSOR{_64x64} and a dimension of 64 by 64 pixel the operation succeeds and the returned stride size is always 256. When drawing the cursor buffer and displaying on screen graphical artifacts appear. Instead of 128 bytes a stride size of 512 seems to be correct on Kaveri systems. For this particular scenario there is a workaround: query 'an arbitrary but valid cursor buffer size' with DRM_CAP_CURSOR_WIDTH DRM_CAP_CURSOR_HEIGHT. Still gbm_bo_get_stride should not return a wrong stride size. -- You are receiving this mail because: You are the assignee for the bug. --1424076391.1fBae0.10151 Date: Mon, 16 Feb 2015 08:46:31 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
Bug ID 89164
Summary AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers
Product Mesa
Version 10.4
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component Drivers/Gallium/radeonsi
Assignee dri-devel@lists.freedesktop.org
Reporter andreas.pokorny@gmail.com
QA Contact dri-devel@lists.freedesktop.org 

When creating a cursor with GBM_BO_USE_CURSOR{_64x64} and a dimension of 64 by
64 pixel the operation succeeds and the returned stride size is always 256.
When drawing the cursor buffer and displaying on screen graphical artifacts
appear. Instead of 128 bytes a stride size of 512 seems to be correct on Kaveri
systems. 

For this particular scenario there is a workaround: query 'an arbitrary but
valid cursor buffer size' with DRM_CAP_CURSOR_WIDTH DRM_CAP_CURSOR_HEIGHT.

Still gbm_bo_get_stride should not return a wrong stride size.

You are receiving this mail because:
  • You are the assignee for the bug.
--1424076391.1fBae0.10151-- --===============0882824283== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0882824283==--