On 03/07/2018 04:29 PM, Emil Velikov wrote:
On 7 March 2018 at 06:02, Tapani Pälli <tapani.pa...@intel.com> wrote:
On 03/07/2018 12:36 AM, Marek Olšák wrote:
On Mon, Mar 5, 2018 at 7:33 AM, Tapani Pälli <tapani.pa...@intel.com>
On 03/02/2018 03:25 PM, Andres Gomez wrote:
This way we won't fail when validating just because we may have a non
overriden core version that is lower than the requested one, even when
the compat version is high enough.
Do I understand correctly that this happens because when version asked is
3.2 then we always do core context, even when overriding to compat
No. 3.2COMPAT will set both core and compat version limits to 3.2.
I see, I was trying to understand why core version matters when using compat
profile but I'm not sure I get it, it probably should not matter.
In some cases you'd get a program using third party middle-ware.
For many instances of those one component is using a core while the
other a compat profile.
Right, that makes sense. Thanks Emil!
Admittedly the whole extension overriding is a bit of a band-aid
(hack) and it's not worth spending much too time on it ;-)
mesa-dev mailing list