On Wed, Dec 13, 2017 at 04:19:03PM -0500, Bryan Steele wrote: > On Wed, Dec 13, 2017 at 09:56:32PM +0100, Matthieu Herrb wrote: > > On Mon, Nov 27, 2017 at 08:22:30PM +1100, Jonathan Gray wrote: > > > cd /usr/xenocara/lib > > > ftp https://mesa.freedesktop.org/archive/mesa-17.2.6.tar.gz > > > ftp http://jsg.id.au/mesa-update/mesa.diff.gz > > > tar zxf mesa-17.2.6.tar.gz > > > gunzip mesa.diff.gz > > > patch -p0 < mesa.diff > > > > > > sed -i 's/mesa$/mesa-17.2.6/' Makefile > > > > > > build xenocara as normal > > > > > > Builds on at least amd64, i386, sparc64, armv7 and arm64. > > > > > > I'm interested in reports from people who saw corruption on Intel > > > graphics during the brief period when Mesa 17.1.6 was in the tree. > > > > Hi, > > > > Works for me on my various intel and radeon based machines, including > > macppc (with r300). I wasn't seeing the corruption with 17.1.6 though. > > > > I've also checked the it builds and that glxgears works (slowly as > > expected) on loongson. > > -- > > Matthieu Herrb > > > > Hi, > > The last time the Mesa 17 update came up there was also an issue with > the newly introduced GLSL shader cache with pledge(2), which broke 3d > Accel/WebGL in chromium, at least on radeondrm(4). > > Is this still an issue?
In Mesa 17.1/17.2 the disk shader cache is not used on Intel graphics which is why I didn't notice the problem at the time. Mesa 17.2.8 is now in the tree and unconditionally disables the disk shader cache on OpenBSD with the same result as setting the disable environment variable.
