<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - scanout broken on radeon SI (OLAND)" href="https://bugs.freedesktop.org/show_bug.cgi?id=73946#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - scanout broken on radeon SI (OLAND)" href="https://bugs.freedesktop.org/show_bug.cgi?id=73946">bug 73946</a> from <a class="email" href="mailto:dh.herrmann@gmail.com" title="David Herrmann <dh.herrmann@gmail.com>"> David Herrmann</a> <pre>@Michel, any idea how to fix that? The scanout buffers are created via gbm and this falls back to mesa dri->image->createImage() with __DRI_IMAGE_SCANOUT set. So I guess the radeonsi driver uses wrong tiling for such buffers? The DRM device node is stored in dri->screen so the driver should be able to query all required context information, right? Could you tell me at which point exactly you added the PIPE_BIND_SCANOUT flag? I can try adding some ctx-queries there so we set it correctly if used for DRM scanout. In case this flag is needed during pipe-creation, not at buffer-alloc time, we should probably set this flag unconditionally for gbm created pipes. Just thinking out loud.. I have no idea how the radeon hw really works..</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>