Created attachment 430702 [details] mesa-9999 ebuild I've started working on adding vulkan support to the mesa ebuild Unfortunately the vulkan mesa driver requires python3 and the rest of the build requires python2 Not quite sure how to rectify that I'm adding the build here incase someone else can figure it out
Created attachment 430808 [details] mesa-9999.ebuild v2 Still doesn't work due to the python issues but slightly improved
Created attachment 431030 [details] mesa-9999.ebuild v3 I still haven't been able to figure out how the python eclasses work or rather how I can use them to allow both python2 & python3 to be used in the same build As a quick and dirty hack I've stripped out the python configuration options until I can figure it out This gets the Intel Vulkan driver building and installing for me
Created attachment 431488 [details] mesa-9999.ebuild v4 Add back in requirement on mako - still haven't figured out the python eclasses and I'll be away next week - will look at it again when I'm back
Created attachment 435980 [details] mesa-9999.ebuild v5 Support has finally landed for building Vulkan with python2, I've resynced with portage and added Vulkan support Those python2 patches are being backported to mesa-12 so they should be in the next release candidate
Even though I am pretty inexperienced with Vulkan, the last ebuild does indeed seem to work fine, thanks! The ebuild also looks fine to me.
Did python2 support land in mesa 12.0.1? If so, can somebody post an ebuild for building mesa 12 with vulkan support?
Yes it did, will give it a shot when I get home
Created attachment 440518 [details] mesa-12.0.1.ebuild Give this a try, it won't compile for me with llvm-9999
Created attachment 440520 [details] mesa-9999.ebuild v6 Whilst I'm at it resync the 9999 ebuild with portage
Created attachment 440522 [details] mesa-9999.ebuild v6 Obsolete the old one
(In reply to Mike Lothian from comment #8) > Created attachment 440518 [details] > mesa-12.0.1.ebuild > > Give this a try, it won't compile for me with llvm-9999 Well, now I have mesa with vulkan support, but mesa caused file collisions with the vulkan-base package I was using. I had to uninstall it. So now I have libvulkan_intel.so but no libvulkan.so, no vulkaninfo, etc. Detected file collision(s): /usr/include/vulkan/vulkan.h /usr/include/vulkan/vk_platform.h It doesn't make any sense that mesa is installing these files. mesa should instead use the ones installed by the vulkan-base package, IMHO.
I use a different vulkan-base package, so I don't see these collisions, it's currently failing with compile errors, I'll repost it once they've been sorted
(In reply to Mike Lothian from comment #12) > I use a different vulkan-base package, so I don't see these collisions, it's > currently failing with compile errors, I'll repost it once they've been > sorted I'm using the vulkan-base package from the fireburn overlay. Are you sure that your the vulkan-base package doesn't provide vulkan.h? (cause that's what it should do)
Sorry about that, didn't notice as I turned of the warnings over collisions Which package vulkan.h should we keep?
(In reply to Mike Lothian from comment #14) > Which package vulkan.h should we keep? I think we're running straight into some upstream issue here. Why does mesa build with and install its own copy of vulkan.h? Mesa should maybe 1) use the installed vulkan.h and vk_platform.h for its own build 2) not install vulkan.h and vk_platform.h For now, I've simply deleted the two header files from $D in the mesa ebuild. It seems I have a working intel vulkan driver, even though dota crashes. (I've got a Haswell CPU, and Vulkan for Haswell seems to be experimental.)
DOTA2 crashes for me on Slylake and Talos shows over exposed images for the most part
(In reply to Sven from comment #15) This sounds totally plausible. I'll try to address it upstream. Thanks.
Any updates on this?
Breaking news. We may see RADV in Mesa 13 at the end of October. http://www.phoronix.com/scan.php?page=news_item&px=Mesa-13.0-October-Plan It's also reported to be working with The Talos Principle much better now. I haven't tried it myself.
In mesa 13rc3 Vulkan is no built by default. I think it should be nice to have a vulkan use flag to trigger it (I speak for the AMD driver, I don't know about intel)
There's one in the FireBurn overlay, or I can attach it here for you
Created attachment 452116 [details] mesa-9999.ebuild v7
Created attachment 452118 [details] mesa-13.0.0.ebuild
Created attachment 452120 [details, diff] OpenGL45.patch Forgot this is used by the ebuilds to enable OpenGL 4.5 on radeonsi and nvc0
I've added vulkan support to Mesa. To get it, USE=vulkan and VIDEO_CARDS={i965,radeonsi}. I don't know if that's ideal or not, but best to get something into the tree. Sorry it took so long.
