<div dir="ltr"><div>I think the only qemus where we do anything mesa-related are kvm-enabled x86 ones. So in that sense it doesn't matter which drivers are shipped for other qemu targets.</div><div><br></div><div>Alex<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 14 Jun 2019 at 15:16, Burton, Ross <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 14 Jun 2019 at 13:46, Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br>
> I would rather replace swrast with virgl in the qemu machine configs. Currently it's pulled in implicitly via the megadriver package which has virgl included because it is enabled by default in the mesa recipe. From what I can see beaglebone etc. are not affected by this.<br>
<br>
So the failure is that swrast is no longer shipped by mesa but the<br>
qemu BSP does this:<br>
<br>
XSERVER ?= "xserver-xorg \<br>
${@bb.utils.contains('DISTRO_FEATURES', 'opengl',<br>
'mesa-driver-swrast xserver-xorg-extension-glx', '', d)} \<br>
xf86-video-fbdev \<br>
"<br>
<br>
However as Alex says, we have virgl now. Does this work on all qemus?<br>
Should we just change the XSERVER assignment to explicitly pull in<br>
the megadriver instead?<br>
<br>
The 'proper' swrast driver *is* terrible, lets not enabe it by default<br>
now we have virgl for qemu. If a BSP wants to use it then they can,<br>
but it's not something we should enable out of the box.<br>
<br>
Ross<br>
</blockquote></div>