Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-02 Thread Martin Peres
On 01/03/16 16:33, Olivier Galibert wrote: I can confirm tri/cube work with latest git. Talos Principle refuses to start because of missing vkCmdBeginQuery, time to jump into the docs to see how much of gen8 is copy-able there. OG. Indeed, I got vkcube to work on HSW. I recompiled

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Jason Ekstrand
On Mar 1, 2016 1:10 AM, "Martin Peres" wrote: > > On 29/02/16 20:48, Jason Ekstrand wrote: >> >> On Fri, Feb 26, 2016 at 2:18 AM, Olivier Galibert wrote: >>> >>> Ok, I can tell you that 3DSTATE_DEPTH_BUFFER and >>> 3DSTATE_STENCIL_BUFFER seem perfectly

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Olivier Galibert
I can confirm tri/cube work with latest git. Talos Principle refuses to start because of missing vkCmdBeginQuery, time to jump into the docs to see how much of gen8 is copy-able there. OG. On Tue, Mar 1, 2016 at 10:28 AM, Jacek Konieczny wrote: > On 2016-03-01 10:10,

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Olivier Galibert
Beware of path issues, vk* has no error checking and gives funky values to the driver if it fails at finding its extra files. OG. On Tue, Mar 1, 2016 at 10:10 AM, Martin Peres wrote: > On 29/02/16 20:48, Jason Ekstrand wrote: > > On Fri, Feb 26, 2016 at 2:18 AM, Olivier

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Martin Peres
On 01/03/16 13:21, Kenneth Graunke wrote: On Tuesday, March 1, 2016 11:10:25 AM PST Martin Peres wrote: On 29/02/16 20:48, Jason Ekstrand wrote: On Fri, Feb 26, 2016 at 2:18 AM, Olivier Galibert > wrote: Ok, I can tell you that

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Kenneth Graunke
On Tuesday, March 1, 2016 11:10:25 AM PST Martin Peres wrote: > On 29/02/16 20:48, Jason Ekstrand wrote: > > On Fri, Feb 26, 2016 at 2:18 AM, Olivier Galibert > > wrote: > > > > Ok, I can tell you that 3DSTATE_DEPTH_BUFFER and > >

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Jacek Konieczny
On 2016-03-01 10:10, Martin Peres wrote: On 29/02/16 20:48, Jason Ekstrand wrote: On Fri, Feb 26, 2016 at 2:18 AM, Olivier Galibert > wrote: Ok, I can tell you that 3DSTATE_DEPTH_BUFFER and 3DSTATE_STENCIL_BUFFER seem perfectly correct

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-03-01 Thread Martin Peres
On 29/02/16 20:48, Jason Ekstrand wrote: On Fri, Feb 26, 2016 at 2:18 AM, Olivier Galibert > wrote: Ok, I can tell you that 3DSTATE_DEPTH_BUFFER and 3DSTATE_STENCIL_BUFFER seem perfectly correct (assuming the gem address-patching-in

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-29 Thread Jason Ekstrand
On Fri, Feb 26, 2016 at 2:18 AM, Olivier Galibert wrote: > Ok, I can tell you that 3DSTATE_DEPTH_BUFFER and > 3DSTATE_STENCIL_BUFFER seem perfectly correct (assuming the gem > address-patching-in works for the depth buffer address). I'll see if > I can find a past version

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-26 Thread Olivier Galibert
Ok, I can tell you that 3DSTATE_DEPTH_BUFFER and 3DSTATE_STENCIL_BUFFER seem perfectly correct (assuming the gem address-patching-in works for the depth buffer address). I'll see if I can find a past version that works. OG. On Wed, Feb 17, 2016 at 4:31 PM, Jason Ekstrand

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-17 Thread Olivier Galibert
Ok, I'll do that, thanks :-) No matter what, I'll learn interesting things. OG. On Wed, Feb 17, 2016 at 4:31 PM, Jason Ekstrand wrote: > On Tue, Feb 16, 2016 at 11:22 PM, Olivier Galibert > wrote: >> >> I'm actually interested about how one goes

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-17 Thread Thomas Helland
17. feb. 2016 16.37 skrev "Jason Ekstrand" : > > On Tue, Feb 16, 2016 at 11:41 PM, Iago Toral wrote: >> >> Hey Jason, >> >> this is awesome news, congrats to all the people involved! > > > Thanks! > >> >> Did you have a chance to try the new driver with

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-17 Thread Jason Ekstrand
On Tue, Feb 16, 2016 at 11:41 PM, Iago Toral wrote: > Hey Jason, > > this is awesome news, congrats to all the people involved! > Thanks! > Did you have a chance to try the new driver with anything other than > conformance tests or small demos? I know it is still in a very

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-17 Thread Jason Ekstrand
On Tue, Feb 16, 2016 at 11:22 PM, Olivier Galibert wrote: > I'm actually interested about how one goes about debugging that kind > of problem, if you have pointers. I would have an idea or two on how > to go about it if it was in userspace only, but once it crosses into >

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-16 Thread Iago Toral
Hey Jason, this is awesome news, congrats to all the people involved! Did you have a chance to try the new driver with anything other than conformance tests or small demos? I know it is still in a very early stage but I'd like to know your impressions about how much of an improvement it brings

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-16 Thread Olivier Galibert
I'm actually interested about how one goes about debugging that kind of problem, if you have pointers. I would have an idea or two on how to go about it if it was in userspace only, but once it crosses into the kernel I'm not sure what strategies are best. Best, OG. On Wed, Feb 17, 2016 at

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-16 Thread Jason Ekstrand
On Tue, Feb 16, 2016 at 1:21 PM, Olivier Galibert wrote: > Hi, > > I'm getting gpu hangs with the lunarg examples (cube and tri) on my > Haswell (64 bits). I attach /sys/class/drm/card0/error fwiw. How > should I go about debugging that? > It's a depth-stencil issue and

Re: [Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-16 Thread Connor Abbott
The first thing I would do is to try running it under valgrind and see if there are any errors. Make sure to have the valgrind development headers installed when building mesa, as anvil has a lot of special valgrind hooks builtin that it will only use if it finds the header during the build. On

[Mesa-dev] ANNOUNCE: An open-source Vulkan driver for Intel hardware

2016-02-16 Thread Jason Ekstrand
The Intel mesa team is pleased to announce a brand-new open-source Vulkan driver for Intel hardware. We've been working hard on this over the course of the past year or so and are excited to finally share it with the community. We will work on up-streaming the driver in the next few weeks and