Thanks for all the comments!
@Mike Blumenkrantz, when I built mesa with
-Dgallium-drivers=radeonsi,virgl,zink,
How should I instruct the mesa to use GBM/ZINK during run time?
When I use "MESA_LOADER_DRIVER_OVERRIDE=zink", the test fails by "MESA:
error: ZINK: failed to choose pdev".
On Mon, 22
virtio likely doesn't work with zink for the same reason that
xf86-video-amdgpu doesn't work with zink: the DDX doesn't support
modifiers.
Marek
On Mon, Jul 22, 2024 at 11:00 AM Mike Blumenkrantz
wrote:
>
> Hi,
>
> If you aren't hitting the kopper init paths (e.g., kopper_init_screen),
> you're
Hi,
If you aren't hitting the kopper init paths (e.g., kopper_init_screen),
you're doing something wrong.
I'm not sure exactly what's going on there with gfxstream, but for gbm+zink
you should be getting a backtrace like this on init:
#0 kopper_init_screen (screen=0x25e010, driver_name_is_inferr
Dear mesa/experts,
Need your support to help us better understand how we can go about this
behavior.
Here is what we have:
1.We are running QEMU based Debian guest with -device
virtio-gpu-rutabaga,gfxstream-vulkan=on,cross-domain=on. Expect to run
vulkan application eg.vkcube-wayland f
