Re: [Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-15 Thread Lionel Landwerlin
Hey Samuel, I think you forgot to define the default value for our driver. I'm not too familiar with this code. Is there a way to have default values for all dri drivers? Thanks, - Lionel On 15/02/17 16:42, Samuel Pitoiset wrote: On 02/15/2017 05:36 PM, Mark Janes wrote: With this series

Re: [Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-15 Thread Mark Janes
With this series, I encounter the following crash using wflinfo: wflinfo: src/mesa/drivers/dri/common/xmlconfig.c:1028: driQueryOptionb: Assertion `cache->info[i].name != ((void *)0)' failed. Samuel Pitoiset writes: > Mesa currently doesn't allow to create 3.1+ compatibility profiles > mainly

Re: [Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-15 Thread Samuel Pitoiset
On 02/15/2017 05:36 PM, Mark Janes wrote: With this series, I encounter the following crash using wflinfo: wflinfo: src/mesa/drivers/dri/common/xmlconfig.c:1028: driQueryOptionb: Assertion `cache->info[i].name != ((void *)0)' failed. Mmh. Can you provide a full backtrace? Samuel Pitoiset

Re: [Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-15 Thread Nicolai Hähnle
On 14.02.2017 16:18, Samuel Pitoiset wrote: Mesa currently doesn't allow to create 3.1+ compatibility profiles mainly because various features are unimplemented and bugs can happen. However, some buggy apps request a compat profile without using any old features unimplemented in mesa, and they f

Re: [Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-14 Thread Edmondo Tommasina
This series is Reviewed-by: Edmondo Tommasina Thanks edmondo On Tue, Feb 14, 2017 at 4:18 PM, Samuel Pitoiset wrote: > Mesa currently doesn't allow to create 3.1+ compatibility profiles > mainly because various features are unimplemented and bugs can > happen. > > However, some buggy apps reque

Re: [Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-14 Thread Marek Olšák
Reviewed-by: Marek Olšák Marek On Tue, Feb 14, 2017 at 4:18 PM, Samuel Pitoiset wrote: > Mesa currently doesn't allow to create 3.1+ compatibility profiles > mainly because various features are unimplemented and bugs can > happen. > > However, some buggy apps request a compat profile without us

[Mesa-dev] [PATCH v2 1/4] driconf: add allow_higher_compat_version option

2017-02-14 Thread Samuel Pitoiset
Mesa currently doesn't allow to create 3.1+ compatibility profiles mainly because various features are unimplemented and bugs can happen. However, some buggy apps request a compat profile without using any old features unimplemented in mesa, and they fail to start. This option should help some ga