From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-89164-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1192 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 2493 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-02-16 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 8:46 bugzilla-daemon [this message]
2015-02-16 9:24 ` [Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers bugzilla-daemon
2015-02-19 9:02 ` bugzilla-daemon
2015-02-19 9:33 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-89164-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.