On Mon, Jan 29, 2018 at 12:08 PM, Rob Clark wrote:
> On Mon, Jan 29, 2018 at 2:39 PM, Ilia Mirkin wrote:
>> On Mon, Jan 29, 2018 at 2:26 PM, Rob Clark wrote:
>>> If we can't create a 3.2 core context, fall back to a 3.1 context.
>>> ---
>>> run.c | 17 +++--
>>> 1 file changed, 15 i
On Mon, 2018-01-29 at 15:08 -0500, Rob Clark wrote:
> Hmm, does that mean there is no way to create a 3.1 core profile if a
> driver supports 3.1 compat?
This is where the "forward-compatible" bit matters, iirc. If you ask
for 3.1FC you shouldn't get ARB_compatibility.
- ajax
___
On Mon, Jan 29, 2018 at 2:39 PM, Ilia Mirkin wrote:
> On Mon, Jan 29, 2018 at 2:26 PM, Rob Clark wrote:
>> If we can't create a 3.2 core context, fall back to a 3.1 context.
>> ---
>> run.c | 17 +++--
>> 1 file changed, 15 insertions(+), 2 deletions(-)
>>
>> diff --git a/run.c b/run
On Mon, Jan 29, 2018 at 2:26 PM, Rob Clark wrote:
> If we can't create a 3.2 core context, fall back to a 3.1 context.
> ---
> run.c | 17 +++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/run.c b/run.c
> index 79d771e..2056ebd 100644
> --- a/run.c
> +++ b/run.
If we can't create a 3.2 core context, fall back to a 3.1 context.
---
run.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/run.c b/run.c
index 79d771e..2056ebd 100644
--- a/run.c
+++ b/run.c
@@ -383,9 +383,22 @@ create_context(EGLDisplay egl_dpy, EGLConfig
