On Wed, May 03, 2017 at 03:42:42PM +0100, Emil Velikov wrote:
> On 3 May 2017 at 15:29, Chris Wilson wrote:
> > On Wed, Apr 12, 2017 at 02:58:50PM +0100, Emil Velikov wrote:
> >> On 11 April 2017 at 17:11, Chris Wilson wrote:
> >> > Jump through the layers of abstraction between egl and dri in or
On 3 May 2017 at 15:29, Chris Wilson wrote:
> On Wed, Apr 12, 2017 at 02:58:50PM +0100, Emil Velikov wrote:
>> On 11 April 2017 at 17:11, Chris Wilson wrote:
>> > Jump through the layers of abstraction between egl and dri in order to
>> > feed the context priority attribute through to the backend
On Wed, Apr 12, 2017 at 02:58:50PM +0100, Emil Velikov wrote:
> On 11 April 2017 at 17:11, Chris Wilson wrote:
> > Jump through the layers of abstraction between egl and dri in order to
> > feed the context priority attribute through to the backend. This
> > requires us to read the value from the
On 11 April 2017 at 17:11, Chris Wilson wrote:
> Jump through the layers of abstraction between egl and dri in order to
> feed the context priority attribute through to the backend. This
> requires us to read the value from the base _egl_context, convert it to
> a DRI attribute, parse it again in
On 17-04-11 17:11:55, Chris Wilson wrote:
Jump through the layers of abstraction between egl and dri in order to
feed the context priority attribute through to the backend. This
requires us to read the value from the base _egl_context, convert it to
a DRI attribute, parse it again in the generic
Jump through the layers of abstraction between egl and dri in order to
feed the context priority attribute through to the backend. This
requires us to read the value from the base _egl_context, convert it to
a DRI attribute, parse it again in the generic context creator before
passing it to the dri
