https://bugs.freedesktop.org/show_bug.cgi?id=107224
--- Comment #8 from Timothy Arceri <t_arc...@yahoo.com.au> ---
(In reply to Alex Smith from comment #7)
> Thanks for confirming.
>
> It looks like we have a bug where we fail to identify Mesa properly as a
> result of compatibility profile support being added, which causes us to go
> down a path for a different driver that incorrectly adds that configuration
> option. That then persists even after switching back to an older Mesa
> version.
>
> We're looking into what we can do here, but I can confirm it is not a Mesa
> bug.
Hmm ... I'm seeing the same issue on a i965 skylake machine that should never
have exposed compatibility profile support.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
