https://bugs.freedesktop.org/show_bug.cgi?id=104926
--- Comment #3 from Michal Srb <[email protected]> ---
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...
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug._______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
