From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window
Date: Thu, 16 Jun 2016 15:42:12 -0700 [thread overview]
Message-ID: <1466116932.2257.4.camel@HansenPartnership.com> (raw)
In-Reply-To: <1466112547.2311.3.camel@HansenPartnership.com>
On Thu, 2016-06-16 at 14:29 -0700, James Bottomley wrote:
> On Thu, 2016-06-16 at 23:24 +0200, Daniel Vetter wrote:
> > I guess we'll need the bisect on this one to make progress.
>
> Sigh, I was afraid that might be the next step.
OK, I have a curious data point. I assumed the problem would be
somewhere in the drm update, so I started bisecting that at the top.
However, the top most commit:
commit 1d6da87a3241deb13d073c4125d19ed0e5a0c62c
Merge: 1f40c49 a39ed68
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon May 23 11:48:48 2016 -0700
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
Isn't actually bad. There's no flicker here, so whatever caused the
problem came from some update after this.
James
next prev parent reply other threads:[~2016-06-16 22:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:59 James Bottomley
2016-05-31 7:51 ` Jani Nikula
2016-05-31 13:33 ` James Bottomley
2016-06-13 10:14 ` Jani Nikula
2016-06-16 21:15 ` James Bottomley
2016-06-16 21:24 ` [Intel-gfx] " Daniel Vetter
2016-06-16 21:29 ` James Bottomley
2016-06-16 22:42 ` James Bottomley [this message]
2016-06-17 7:28 ` Daniel Vetter
2016-06-17 13:34 ` Jani Nikula
2016-06-17 16:08 ` James Bottomley
2016-06-17 23:06 ` James Bottomley
2016-06-19 21:53 ` James Bottomley
2016-06-20 8:03 ` Jani Nikula
2016-06-21 13:53 ` James Bottomley
2016-06-21 15:44 ` Ville Syrjälä
2016-06-21 21:00 ` James Bottomley
2016-06-23 11:25 ` James Bottomley
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-07 16:14 ` Ville Syrjälä
2016-07-07 16:55 ` James Bottomley
2016-07-07 19:19 ` James Bottomley
2016-07-08 10:19 ` Ville Syrjälä
2016-07-08 14:48 ` James Bottomley
2016-07-08 16:56 ` Ville Syrjälä
2016-09-11 14:10 ` James Hogan
2016-09-13 13:59 ` Jani Nikula
2016-06-23 12:52 ` Steven Newbury
2016-06-23 12:59 ` Jani Nikula
2016-06-23 13:14 ` Steven Newbury
2016-06-24 10:59 ` Chris Wilson
2016-06-24 11:48 ` Steven Newbury
2016-06-24 12:42 ` Chris Wilson
2016-07-12 10:08 ` Daniel Vetter
2016-09-14 9:43 ` Jani Nikula
2016-06-17 8:12 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1466116932.2257.4.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome