On Tue, Nov 11, 2014 at 11:34:58AM +, Michel Thierry wrote:
> On 11/10/2014 4:38 PM, Mika Kuoppala wrote:
> >>- int (*init_context)(struct intel_engine_cs *ring);
> >>+ int (*init_context)(struct intel_ringbuffer *ringbuf);
> >What is the rationale of this? This seem
On 11/10/2014 4:38 PM, Mika Kuoppala wrote:
Arun Siluvery writes:
From: Michel Thierry
Following the legacy ring submission example, update the
ring->init_context() hook to support the execlist submission mode.
v2: update to use the new workaround macros and cleanup unused code.
This takes
Arun Siluvery writes:
> From: Michel Thierry
>
> Following the legacy ring submission example, update the
> ring->init_context() hook to support the execlist submission mode.
>
> v2: update to use the new workaround macros and cleanup unused code.
> This takes care of both bdw and chv workaround
From: Michel Thierry
Following the legacy ring submission example, update the
ring->init_context() hook to support the execlist submission mode.
v2: update to use the new workaround macros and cleanup unused code.
This takes care of both bdw and chv workarounds.
v2.1: Add missing call to init_c
From: Michel Thierry
Following the legacy ring submission example, update the
ring->init_context() hook to support the execlist submission mode.
v2: update to use the new workaround macros and cleanup unused code.
This takes care of both bdw and chv workarounds.
Issue: VIZ-4092
Issue: GMIN-3475
