[Mesa-dev] [AppVeyor] mesa-webhook master #15096 completed

2020-03-30 Thread AppVeyor
Build mesa-webhook 15096 completed Commit 02ad147c5c by Alyssa Rosenzweig on 3/31/2020 12:54 AM: pan/bi: Fix handling of constants with COMBINE\n\nWe should never see COMBINE constants explicitly since they'll become\nmoves anyway, so we can simplify that. On t

[Mesa-dev] [AppVeyor] mesa-webhook master #15095 failed

2020-03-30 Thread AppVeyor
Build mesa-webhook 15095 failed Commit 50e3b2e390 by Icecream95 on 3/24/2020 4:33 AM: panfrost: Correctly identify format 0x4c\n\nReviewed-by: Alyssa Rosenzweig \nTested-by: Marge Bot \nPart-of: Configure your notification preferences __

[Mesa-dev] [PATCH kmscube v2] meson.build: Change c_std to gnu99

2020-03-30 Thread Fabio Estevam
Since commit 301a556b8ece ("add fps reporting") the header is included, which causes build failures with c99 extension on ARM32: ../common.c: In function 'get_time_ns': ../common.c:376:18: error: storage size of 'tv' isn't known struct timespec tv; ^~ ../common.c:377:16: error

Re: [Mesa-dev] [PATCH kmscube] meson.build: Do not set c_std

2020-03-30 Thread Fabio Estevam
Hi Rob, On Mon, Mar 30, 2020 at 6:29 PM Fabio Estevam wrote: > > When building kmscube in Buildroot for ARM the following > errors are seen: > > ../common.c: In function 'get_time_ns': > ../common.c:376:18: error: storage size of 'tv' isn't known > struct timespec tv; > ^~ > .

[Mesa-dev] [PATCH kmscube] meson.build: Do not set c_std

2020-03-30 Thread Fabio Estevam
When building kmscube in Buildroot for ARM the following errors are seen: ../common.c: In function 'get_time_ns': ../common.c:376:18: error: storage size of 'tv' isn't known struct timespec tv; ^~ ../common.c:377:2: warning: implicit declaration of function 'clock_gettime'; di

Re: [Mesa-dev] Remove classic drivers or fork src/mesa for gallium?

2020-03-30 Thread Kristian Høgsberg
On Mon, Mar 30, 2020, 7:59 AM Adam Jackson wrote: > On Sun, 2020-03-29 at 09:45 -0700, Kristian Høgsberg wrote: > > > As for loading, doesn't glvnd solve that? > > It could. It does not. Right now there's not a (good) way for the DDX > driver to communicate a preferred implementation name to the

Re: [Mesa-dev] Remove classic drivers or fork src/mesa for gallium?

2020-03-30 Thread Adam Jackson
On Sun, 2020-03-29 at 09:45 -0700, Kristian Høgsberg wrote: > As for loading, doesn't glvnd solve that? It could. It does not. Right now there's not a (good) way for the DDX driver to communicate a preferred implementation name to the GLX client. xserver's glx just knows it needs an implementatio