On Thu, Sep 04, 2014 at 08:15:32PM +0300, Ville Syrjälä wrote:
On Tue, Sep 02, 2014 at 02:57:37PM +0100, Chris Wilson wrote:
If we successfully confuse the hardware, and cause it to drop a queued
pageflip, we wait for 60s and issue a warning before continuing on with
the modeset. However,
On Fri, Sep 05, 2014 at 09:27:16AM +0200, Daniel Vetter wrote:
On Thu, Sep 04, 2014 at 08:15:32PM +0300, Ville Syrjälä wrote:
On Tue, Sep 02, 2014 at 02:57:37PM +0100, Chris Wilson wrote:
If we successfully confuse the hardware, and cause it to drop a queued
pageflip, we wait for 60s and
On Fri, Sep 05, 2014 at 08:31:20AM +0100, Chris Wilson wrote:
On Fri, Sep 05, 2014 at 09:27:16AM +0200, Daniel Vetter wrote:
On Thu, Sep 04, 2014 at 08:15:32PM +0300, Ville Syrjälä wrote:
On Tue, Sep 02, 2014 at 02:57:37PM +0100, Chris Wilson wrote:
If we successfully confuse the
On Tue, Sep 02, 2014 at 02:57:37PM +0100, Chris Wilson wrote:
If we successfully confuse the hardware, and cause it to drop a queued
pageflip, we wait for 60s and issue a warning before continuing on with
the modeset. However, this leaves the pending pageflip still stuck
indefinitely. Pretend
If we successfully confuse the hardware, and cause it to drop a queued
pageflip, we wait for 60s and issue a warning before continuing on with
the modeset. However, this leaves the pending pageflip still stuck
indefinitely. Pretend to userspace that it does complete, and let us
start afresh
