From: Dave Jones <davej@codemonkey.org.uk>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Dave Airlie <airlied@linux.ie>,
Linus Torvalds <torvalds@linux-foundation.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Lankhorst, Maarten" <maarten.lankhorst@intel.com>,
Jairo Miramontes <jairo.daniel.miramontes.caton@intel.com>
Subject: Re: [regression] [git pull] drm for 4.3
Date: Tue, 22 Sep 2015 21:49:09 -0400 [thread overview]
Message-ID: <20150923014909.GA18010@codemonkey.org.uk> (raw)
In-Reply-To: <20150922161558.GB24128@intel.com>
On Tue, Sep 22, 2015 at 09:15:58AM -0700, Matt Roper wrote:
> On Tue, Sep 22, 2015 at 05:13:55PM +0200, Daniel Vetter wrote:
> > On Tue, Sep 22, 2015 at 08:00:17AM -0700, Jesse Barnes wrote:
> > > Cc'ing Maarten and Matt; I'm guessing this may be related to one of
> > > their recent patches.
>
> Sounds like this showed up before my recent work, but I think I might
> have seen similar problems while working on atomic watermarks; the
> issues I was seeing were because the initial hardware readout could
> leave primary->visible set to true even when the CRTC was off. My
> series (which is still under development) contains this patch to fix
> that:
>
> http://patchwork.freedesktop.org/patch/59564/
>
> Does applying that help with the problems reported here?
No difference at all for me.
Dave
next prev parent reply other threads:[~2015-09-23 1:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 22:40 [git pull] drm for 4.3 Dave Airlie
2015-09-07 18:45 ` Dave Jones
2015-09-21 18:48 ` Dave Jones
2015-09-22 15:00 ` [Intel-gfx] " Jesse Barnes
2015-09-22 15:13 ` [regression] " Daniel Vetter
2015-09-22 16:15 ` Matt Roper
2015-09-23 1:49 ` Dave Jones [this message]
2015-09-23 11:07 ` Lankhorst, Maarten
2015-09-24 3:51 ` davej
2015-09-24 13:26 ` Jani Nikula
2015-09-30 1:07 ` davej
2015-09-30 6:56 ` Daniel Vetter
2015-10-19 20:19 ` davej
2015-10-19 21:54 ` [Intel-gfx] " Daniel Vetter
2015-10-20 5:33 ` Dave Airlie
2015-10-20 14:42 ` davej
2015-09-29 6:43 ` [Intel-gfx] [regression] boot to the blackscreen with the kernel 4.3 zhuhuachun
2015-09-08 2:03 ` [git pull] drm for 4.3 Stephen Rothwell
2015-09-08 3:01 ` Dave Airlie
2015-09-08 4:04 ` Stephen Rothwell
2015-09-08 4:56 ` Dave Airlie
2015-09-08 18:19 ` Linus Torvalds
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=20150923014909.GA18010@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jairo.daniel.miramontes.caton@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).