<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported" href="https://bugs.freedesktop.org/show_bug.cgi?id=104926#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported" href="https://bugs.freedesktop.org/show_bug.cgi?id=104926">bug 104926</a> from <a class="email" href="mailto:michalsrb@gmail.com" title="Michal Srb <michalsrb@gmail.com>"> Michal Srb</a> <pre>I was able to reproduce the `gbm_device_is_format_supported` failure. The call sequence is following: * gbm_device_is_format_supported * gbm_dri_is_format_supported (gbm->is_format_supported) - `dri->image->base.version` is now 17 (this changed in the bisected commit e14fe41e0!) and `dri->image->queryDmaBufModifiers` is set, so it will be called. * dri2_query_dma_buf_modifiers (dri->image->queryDmaBufModifiers) - oh no, `pscreen->query_dmabuf_modifiers` is 0, so return false... The situation depends on whether the screen was initialized with `dri2_init_screen` or with `dri_kms_init_screen`. In case of `dri2_init_screen` the `dri->image->queryDmaBufModifiers` is not set if `pscreen->query_dmabuf_modifiers` is null. In case of `dri_kms_init_screen` it is set unconditionally. The condition was added to `dri2_init_screen` in commit a65db0ad1c3. I think that equivalent condition is needed in `dri_kms_init_screen`. Will send patch...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>