From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?St=E9phane_Marchesin?= <stephane.marchesin@gmail.com>
Subject: Re: [pull] drm-intel-next
Date: Mon, 18 Mar 2013 12:35:46 -0700
Message-ID: <CACP_E+L4EfSAnkecJBMecq4Zbw0wPTvb8BQTubwgAtK5+wrZGw@mail.gmail.com>
References: <20120913141841.GC5693@phenom.ffwll.local>
	<CACP_E+JZ36SXNU4b4GDFRo9KkW28brEEFDEYhyRqR3S4n6JNQg@mail.gmail.com>
	<CAKMK7uHW0YnbZnGH0vLz3aq+EwR7x+f5o7dh6cyttWuEdSpRTQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
In-Reply-To: <CAKMK7uHW0YnbZnGH0vLz3aq+EwR7x+f5o7dh6cyttWuEdSpRTQ@mail.gmail.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>, DRI Development <dri-devel@lists.freedesktop.org>
List-Id: dri-devel@lists.freedesktop.org

-lkml

On Sun, Mar 17, 2013 at 12:46 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Mar 15, 2013 at 3:11 AM, St=E9phane Marchesin
> <stephane.marchesin@gmail.com> wrote:
>>>       drm/i915: read out the modeset hw state at load and resume time
>> This commit regresses modeset on the samsung series 5 chromebook (it
>> is basically a pineview machine with an lvds panel). I don't seem to
>> be able to set any mode on it any longer.
>
> Does that mean the kernel refuses to set the mode, or that you get a
> black screen?
>

I get a black screen.

> For starters I guess we need:
> - drm.debug=3D0xe dmesg from just before that commit
> - same for latest 3.9-rc kernels, presuming it's not broken there
>
> Latest upstream has a minor chance to work better I think since we've
> improved the pfit handling in the setup and teardown sequence a bit.
>
> Generally lvds has been hit&miss on way too many machines
> unfortunately with things randomly breaking and getting fixed again
> (e.g. one of Chris' machines works again with the new code ...). And
> the commit above doesn't really change much in the code itself but it
> does change the order (and timing) of the different enable/disable
> codepaths.

So I did look at the thing a bit, and it triggers the workaround
if (INTEL_INFO(dev)->gen < 4 && !intel_check_plane_mapping(crtc)) {
which seems to be part of the problem (but not the whole problem as
removing that gets me a corrupted display, looks like the second pipe
stays enabled then).

St=E9phane