On Wed, May 28, 2014 at 09:19:05AM +0100, Chris Wilson wrote:
> On Tue, Feb 25, 2014 at 03:13:37PM +0200, ville.syrj...@linux.intel.com wrote:
> > From: Ville Syrjälä
> >
> > I tried to fix the C3 vs. vblank interrupt issues reportd in [1], but
> > it looks like the AGPBUSY# stuff doesn't help th
On Wed, May 28, 2014 at 12:46:12PM +0300, Ville Syrjälä wrote:
> On Wed, May 28, 2014 at 09:19:05AM +0100, Chris Wilson wrote:
> > The slow vblank delivery issue remains iirc though.
>
> Yeah supposedly that's the case on gen3. This series does fix my 855
> though. Unfortunately I've not come acro
On Wed, May 28, 2014 at 09:19:05AM +0100, Chris Wilson wrote:
> On Tue, Feb 25, 2014 at 03:13:37PM +0200, ville.syrj...@linux.intel.com wrote:
> > From: Ville Syrjälä
> >
> > I tried to fix the C3 vs. vblank interrupt issues reportd in [1], but
> > it looks like the AGPBUSY# stuff doesn't help th
On Tue, Feb 25, 2014 at 03:13:37PM +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> I tried to fix the C3 vs. vblank interrupt issues reportd in [1], but
> it looks like the AGPBUSY# stuff doesn't help there for some reason. I
> guess either the board isn't wired correctly, o
From: Ville Syrjälä
I tried to fix the C3 vs. vblank interrupt issues reportd in [1], but
it looks like the AGPBUSY# stuff doesn't help there for some reason. I
guess either the board isn't wired correctly, or we're missing
something else. I doubt the BM wakup mechanism itself would be
broken sin
