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.
Alex On Fri, 14 Jun 2019 at 15:16, Burton, Ross <[email protected]> wrote: > On Fri, 14 Jun 2019 at 13:46, Alexander Kanavin <[email protected]> > wrote: > > 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. > > So the failure is that swrast is no longer shipped by mesa but the > qemu BSP does this: > > XSERVER ?= "xserver-xorg \ > ${@bb.utils.contains('DISTRO_FEATURES', 'opengl', > 'mesa-driver-swrast xserver-xorg-extension-glx', '', d)} \ > xf86-video-fbdev \ > " > > However as Alex says, we have virgl now. Does this work on all qemus? > Should we just change the XSERVER assignment to explicitly pull in > the megadriver instead? > > The 'proper' swrast driver *is* terrible, lets not enabe it by default > now we have virgl for qemu. If a BSP wants to use it then they can, > but it's not something we should enable out of the box. > > Ross >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
