On Mon, Jun 09, 2014 at 10:06:29PM +0300, Jani Nikula wrote:
On Mon, 09 Jun 2014, Ville Syrjälä ville.syrj...@linux.intel.com wrote:
On Mon, Jun 09, 2014 at 09:12:18PM +0300, Jani Nikula wrote:
On Fri, 06 Jun 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
It causes black screen on
On Tue, 10 Jun 2014, Daniel Vetter dan...@ffwll.ch wrote:
On Mon, Jun 09, 2014 at 10:06:29PM +0300, Jani Nikula wrote:
On Mon, 09 Jun 2014, Ville Syrjälä ville.syrj...@linux.intel.com wrote:
On Mon, Jun 09, 2014 at 09:12:18PM +0300, Jani Nikula wrote:
On Fri, 06 Jun 2014, Chris Wilson
On Fri, 06 Jun 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
It causes black screen on bootup and is approximately 100x slower than
running with FBC disabled, so the GPU runs at a high frequency for much
longer - completely contrary to the power saving claims. It also still
has mutex
On Mon, Jun 09, 2014 at 09:12:18PM +0300, Jani Nikula wrote:
On Fri, 06 Jun 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
It causes black screen on bootup and is approximately 100x slower than
running with FBC disabled, so the GPU runs at a high frequency for much
longer - completely
On Mon, 09 Jun 2014, Ville Syrjälä ville.syrj...@linux.intel.com wrote:
On Mon, Jun 09, 2014 at 09:12:18PM +0300, Jani Nikula wrote:
On Fri, 06 Jun 2014, Chris Wilson ch...@chris-wilson.co.uk wrote:
It causes black screen on bootup and is approximately 100x slower than
running with FBC
It causes black screen on bootup and is approximately 100x slower than
running with FBC disabled, so the GPU runs at a high frequency for much
longer - completely contrary to the power saving claims. It also still
has mutex deadlocks in multi-head scenarios, which can lead to a
system/X lockup.
On Fri, Jun 06, 2014 at 10:37:11AM +0100, Chris Wilson wrote:
It causes black screen on bootup and is approximately 100x slower than
running with FBC disabled, so the GPU runs at a high frequency for much
longer - completely contrary to the power saving claims. It also still
has mutex
