On 2024/01/20 2:01, Faith Ekstrand wrote:
We already have several places where we're doing significant layering.
It started with sharing the WSI code
I wish that it be possible to compile WSI implementation as separate
Vulkan layer *.so module instead of hardcoding and duplicating it to
each
On one hand I think it's a great idea. Moving code out of drivers to common
means fixing bugs helps everyone, and implementing new features is the same.
On the other hand, everyone's already got code that works, which means both
a lot of work to switch that code over to common and then the usual
Hi Jordan
Thanks for digging into this!
On Fri, Jan 19, 2024 at 12:10:37PM -0800, Jordan Justen wrote:
> On 2024-01-18 04:37:52, Stefan Dirsch wrote:
> > Hi
> >
> > I noticed that with version 23.3.x Mesa no longer can be built with python
> > 2.6. It still worked with Mesa 23.2.1.
>
> As
On Thu, Jan 18, 2024 at 01:37:52PM +0100, Stefan Dirsch wrote:
> Hi
>
> I noticed that with version 23.3.x Mesa no longer can be built with python
> 2.6. It still worked with Mesa 23.2.1.
Of course I've meant python 3.6. Sorry for the confusion!
> It fails with
>
> [ 95s] Traceback (most
On 2024-01-18 04:37:52, Stefan Dirsch wrote:
> Hi
>
> I noticed that with version 23.3.x Mesa no longer can be built with python
> 2.6. It still worked with Mesa 23.2.1.
As mentioned in other emails, this was typo where 3.6 was intended.
>
> It fails with
>
> [ 95s] Traceback (most recent
On Fri, Jan 19, 2024 at 12:35:58PM -0500, Matt Turner wrote:
> On Thu, Jan 18, 2024 at 10:22 AM Stefan Dirsch wrote:
> > I noticed that with version 23.3.x Mesa no longer can be built with python
> > 2.6. It still worked with Mesa 23.2.1.
>
> For anyone who got this far and was completely
On Thu, Jan 18, 2024 at 10:22 AM Stefan Dirsch wrote:
> I noticed that with version 23.3.x Mesa no longer can be built with python
> 2.6. It still worked with Mesa 23.2.1.
For anyone who got this far and was completely incredulous... this
(and the subject) is typo'd -- the problem is about
Yeah, this one's gonna hit Phoronix...
When we started writing Vulkan drivers back in the day, there was this
notion that Vulkan was a low-level API that directly targets hardware.
Vulkan drivers were these super thin things that just blasted packets
straight into the hardware. What little code
