public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "davej@codemonkey.org.uk" <davej@codemonkey.org.uk>,
	"Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Miramontes Caton,
	Jairo Daniel" <jairo.daniel.miramontes.caton@intel.com>,
	"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [regression] [git pull] drm for 4.3
Date: Thu, 24 Sep 2015 16:26:28 +0300	[thread overview]
Message-ID: <877fng54or.fsf@intel.com> (raw)
In-Reply-To: <20150924035108.GA19724@codemonkey.org.uk>

On Thu, 24 Sep 2015, "davej@codemonkey.org.uk" <davej@codemonkey.org.uk> wrote:
> On Wed, Sep 23, 2015 at 11:07:56AM +0000, Lankhorst, Maarten wrote:
>  > Hey,
>  > 
>  > Dave Jones schreef op di 22-09-2015 om 21:49 [-0400]:
>  > > 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.
>  > Looks like a (reopened) dup of 91952?
>  > 
>  > Can you apply "[PATCH] drm/i915: Add primary plane to mask if it's
>  > visible", and get me the results?
>
> This doesn't apply on top of Linus' current tree.
> If you let me know what it's dependant on, I'll do a build with
> those patches tomorrow.

It's now part of the drm-intel-fixes pull request [1], maybe it's
easiest to pull that in? Just four commits on top of
v4.3-rc2. Alternatively pick it up from our repo [2].

Thanks,
Jani.



[1] http://mid.gmane.org/87si646uyf.fsf@intel.com
[2] http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-fixes&id=721a09f7393de6c28a07516dccd654c6e995944a

>
> 	Dave
>  

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-09-24 13:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.1509042337590.19786@skynet.skynet.ie>
2015-09-07 18:45 ` [git pull] drm for 4.3 Dave Jones
2015-09-21 18:48   ` Dave Jones
2015-09-22 15:00     ` Jesse Barnes
2015-09-22 15:13       ` [regression] " Daniel Vetter
2015-09-22 16:15         ` Matt Roper
2015-09-23  1:49           ` Dave Jones
2015-09-23 11:07             ` Lankhorst, Maarten
2015-09-24  3:51               ` davej
2015-09-24 13:26                 ` Jani Nikula [this message]
2015-09-30  1:07                   ` davej
2015-09-30  6:56                     ` Daniel Vetter
2015-10-19 20:19                       ` davej
2015-10-19 21:54                         ` Daniel Vetter
2015-10-20  5:33                           ` Dave Airlie
2015-10-20 14:42                             ` davej
2015-09-29  6:43                 ` [regression] boot to the blackscreen with the kernel 4.3 zhuhuachun

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=877fng54or.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=davej@codemonkey.org.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jairo.daniel.miramontes.caton@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@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