From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Richter <thor@math.tu-berlin.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: drm/i915/ns2501: Update from git working
Date: Wed, 9 Oct 2013 00:00:32 +0200 [thread overview]
Message-ID: <20131008220032.GI8303@phenom.ffwll.local> (raw)
In-Reply-To: <52547189.7050600@math.tu-berlin.de>
On Tue, Oct 08, 2013 at 10:56:41PM +0200, Thomas Richter wrote:
> Hi Daniel, dear kernel developers,
>
> just tried the 3.12.rc3+ from the intel-drm git. This version
> *worked* again, pretty much the same way the 3.10.10 "worked".
>
> Side effects are, however, quite the same when you connect an
> external monitor:
>
> If connected while the gdm login screen is on, the external monitor
> works fine with the internal TFT (mirroring is turned on).
> Resolutions
> 1024x768 and 800x600 are fine, switching to 640x480 locks up the
> internal DVO, the external monitor keeps working. Note that the DVO
> does *not* lock up if the external monitor is not connect (probably
> a frequency issue, need to check).
>
> Booting with the external monitor connected creates a "locked up"
> display on the internal TFT, and a flickering display on the
> external
> screen as if the watermark levels are not set correctly. The
> external screen shows a horizontal offset of approximately half the
> screen
> width (scrolled to the right), but jumps back to its correct
> position irregularly. Note that this type of flickering is different
> from the flicker
> created by panning on the 835GM (already reported this problem),
> which shows a regular 30Hz flicker.
>
> Once the gdm comes up, the internal TFT keeps dead, and the external
> shows only a black screen but with a working mouse pointer.
> Logging in blindly restores a working screen on both monitors.
>
> So thanks for the update, seems to have worked, but is still not
> working perfectly. External monitors are not supported correctly,
> and panning is still a problem, even with a "linear" framebuffer.
My drm-intel git branch doesn't yet have the two patches that are meant to
replace your ns2501 hack ... So I'm not too sure what exactly you've
tested that made things magically better?
For me the key to get rid of the black screen was the two sna patches, not
the kernel stuff here.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-10-08 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 10:25 [PATCH 1/3] drm/i915: rip out gen2 reset code Daniel Vetter
2013-10-08 10:25 ` [PATCH 2/3] drm/i915/dvo: call ->mode_set callback only when the port is running Daniel Vetter
2013-10-08 11:31 ` Chris Wilson
2013-10-08 10:25 ` [PATCH 3/3] drm/i915/ns2501: Rip out the reenable hack Daniel Vetter
2013-10-08 10:29 ` [PATCH 1/3] drm/i915: rip out gen2 reset code Chris Wilson
2013-10-08 12:23 ` Daniel Vetter
[not found] ` <26192_1381227964_5253DDBB_26192_8102_1_1381227943-4409-3-git-send-email-daniel.vetter@ffwll.ch>
2013-10-08 20:56 ` drm/i915/ns2501: Update from git working Thomas Richter
2013-10-08 22:00 ` Daniel Vetter [this message]
[not found] ` <26192_1381269615_5254806F_26192_12488_1_20131008220032.GI8303@phenom.ffwll.local>
2013-10-09 5:02 ` Thomas Richter
2013-10-09 7:13 ` Daniel Vetter
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=20131008220032.GI8303@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thor@math.tu-berlin.de \
/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