From: Tvrtko Ursulin
Commit ed4596ea992d ("drm/i915/guc: WA to address the Ringbuffer
coherency issue"), based on incorrect assumptions from a partialy
broken commit 0dd356bb6ff5 ("drm/i915: Eliminate Gen9 special
case") used POSTING_READ_FW instead of the POSTING_READ. With the
latter buggy comm
On Thu, Nov 17, 2016 at 09:17:35AM +, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Commit ed4596ea992d ("drm/i915/guc: WA to address the Ringbuffer
> coherency issue"), based on incorrect assumptions from a partialy
> broken commit 0dd356bb6ff5 ("drm/i915: Eliminate Gen9 special
> case")
On 17/11/2016 09:28, Chris Wilson wrote:
On Thu, Nov 17, 2016 at 09:17:35AM +, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Commit ed4596ea992d ("drm/i915/guc: WA to address the Ringbuffer
coherency issue"), based on incorrect assumptions from a partialy
broken commit 0dd356bb6ff5 ("drm/i91
On 11/17/2016 3:06 PM, Tvrtko Ursulin wrote:
On 17/11/2016 09:28, Chris Wilson wrote:
On Thu, Nov 17, 2016 at 09:17:35AM +, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Commit ed4596ea992d ("drm/i915/guc: WA to address the Ringbuffer
coherency issue"), based on incorrect assumptions from
On Mon, Dec 05, 2016 at 03:47:24PM +0530, Kamble, Sagar A wrote:
>
>
> On 11/17/2016 3:06 PM, Tvrtko Ursulin wrote:
> >
> >On 17/11/2016 09:28, Chris Wilson wrote:
> >>On Thu, Nov 17, 2016 at 09:17:35AM +, Tvrtko Ursulin wrote:
> >>>From: Tvrtko Ursulin
> >>>
> >>>Commit ed4596ea992d ("drm/i