search for: 29ba89b2371d466

Displaying 4 results from an estimated 4 matches for "29ba89b2371d466".

2014 Sep 23
2
[PATCH] drm/nv84+: fix fence context seqno's
On Tue, Sep 23, 2014 at 2:23 AM, Ted Percival <ted at tedp.id.au> wrote: > On 09/22/2014 03:08 AM, Maarten Lankhorst wrote: >> This fixes a regression introduced by "drm/nouveau: rework to new fence interface" >> (commit 29ba89b2371d466). >> >> The fence sequence should not be reset after creation, the old value is used instead. >> On destruction the final value is written, to prevent another source of accidental >> wraparound in case of a channel being destroyed after a hang, and unblocking any other >&...
2014 Sep 22
2
[PATCH] drm/nv84+: fix fence context seqno's
This fixes a regression introduced by "drm/nouveau: rework to new fence interface" (commit 29ba89b2371d466). The fence sequence should not be reset after creation, the old value is used instead. On destruction the final value is written, to prevent another source of accidental wraparound in case of a channel being destroyed after a hang, and unblocking any other channel that may wait on the about-to-be...
2014 Sep 22
0
[PATCH] drm/nv84+: fix fence context seqno's
On 09/22/2014 03:08 AM, Maarten Lankhorst wrote: > This fixes a regression introduced by "drm/nouveau: rework to new fence interface" > (commit 29ba89b2371d466). > > The fence sequence should not be reset after creation, the old value is used instead. > On destruction the final value is written, to prevent another source of accidental > wraparound in case of a channel being destroyed after a hang, and unblocking any other > channel that ma...
2014 Sep 23
0
[PATCH] drm/nv84+: fix fence context seqno's
...4 om 07:35 schreef Ben Skeggs: > On Tue, Sep 23, 2014 at 2:23 AM, Ted Percival <ted at tedp.id.au> wrote: >> On 09/22/2014 03:08 AM, Maarten Lankhorst wrote: >>> This fixes a regression introduced by "drm/nouveau: rework to new fence interface" >>> (commit 29ba89b2371d466). >>> >>> The fence sequence should not be reset after creation, the old value is used instead. >>> On destruction the final value is written, to prevent another source of accidental >>> wraparound in case of a channel being destroyed after a hang, and unblocking...