[Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers

[Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers

[bugzilla-daemon]

[-- 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

[Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 684 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=89164

Michel Dänzer <michel@daenzer.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
You need to pass the dimensions queried from DRM_CAP_CURSOR_WIDTH and
DRM_CAP_CURSOR_HEIGHT instead of hardcoding 64. As of CIK, Radeon hardware only
supports 256x256 hardware cursors.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2256 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

[Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 561 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=89164

--- Comment #2 from Andreas Pokorny <andreas.pokorny@gmail.com> ---
(In reply to Michel Dänzer from comment #1)
> You need to pass the dimensions queried from DRM_CAP_CURSOR_WIDTH and
> DRM_CAP_CURSOR_HEIGHT instead of hardcoding 64. As of CIK, Radeon hardware
> only supports 256x256 hardware cursors.

Yes, but since buffer creation with a smaller size does not fail,
gbm_bo_get_stride should return the right size.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1527 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

[Bug 89164] AMD Kaveri: gbm_bo_get_stride returns wrong values for cursor buffers

[bugzilla-daemon]

[-- Attachment #1.1: Type: text/plain, Size: 557 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=89164

--- Comment #3 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Andreas Pokorny from comment #2)
> Yes, but since buffer creation with a smaller size does not fail,
> gbm_bo_get_stride should return the right size.

It returns the stride of the allocated buffer. The problem is that the buffer
size doesn't match the hardware cursor size in the first place. Returning a
different stride can't change that.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1512 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