From: Thomas Richter <richter@rus.uni-stuttgart.de>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Thomas Richter" <thor@math.tu-berlin.de>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: Breaking suspend/resume by the Pipe A quirk
Date: Tue, 03 Jun 2014 17:19:26 +0200 [thread overview]
Message-ID: <538DE77E.9080502@rus.uni-stuttgart.de> (raw)
In-Reply-To: <20140603151426.GC4772@nuc-i3427.alporthouse.com>
Am 03.06.2014 17:14, schrieb Chris Wilson:
> On Tue, Jun 03, 2014 at 05:04:52PM +0200, Thomas Richter wrote:
>> Am 03.06.2014 16:45, schrieb Daniel Vetter:
>>
>>>
>>> Yeah, both connectors use CRTC 0. Have you tried what happens if you:
>>> - disable DVI1 first (--off)
>>> - then enable it on crtc 1?
>>
>> Same difference, internal screen goes blank with --off, and stays
>> blank after moving it to crtc 1 if I try to re-enable it with --auto
>> or --mode.
>
> The oddity in the config is that the LVDS is reported as disconnected.
> That should not be happening unless there is some sharing going on
> inside the DVO chip.
Please note that on this specific notebook, the internal screen is
connected via DVI, not via LVDS. I don't know what they did with the
LVDS output, it's probably - as said - just disconnected.
The R31 has its panel connected via LVDS, and here I can set resolutions
independently just fine.
Currently compiling the patch, takes a while on a 1GHhz/1GB P-3 machine. (-;
Greetings,
Thomas
next prev parent reply other threads:[~2014-06-03 15:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 14:02 830GM still woes Thomas Richter
2014-05-16 14:41 ` Chris Wilson
2014-05-16 15:09 ` Daniel Vetter
2014-05-16 16:04 ` Ville Syrjälä
2014-05-16 16:50 ` Daniel Vetter
[not found] ` <23914_1400259040_537641E0_23914_9298_1_20140516165034.GT8790@phenom.ffwll.local>
2014-05-17 10:58 ` Thomas Richter
2014-05-29 14:10 ` Thomas Richter
2014-05-29 21:19 ` Breaking suspend/resume by the Pipe A quirk Thomas Richter
2014-06-02 8:27 ` Daniel Vetter
2014-06-02 10:34 ` [PATCH] Align i830 watermark to cache lines Thomas Richter
2014-06-02 10:41 ` Breaking suspend/resume by the Pipe A quirk Thomas Richter
2014-06-02 15:27 ` Daniel Vetter
2014-06-02 15:38 ` [Patch] Disabling the pipe A quirk for the Fujitsu S6010 Thomas Richter
2014-06-02 15:56 ` Daniel Vetter
2014-06-02 16:52 ` Thomas Richter
2014-06-02 17:39 ` Daniel Vetter
2014-06-02 18:44 ` Thomas Richter
[not found] ` <1027_1401722832_538C97D0_1027_15897_1_20140602152702.GU19050@phenom.ffwll.local>
2014-06-03 14:38 ` Breaking suspend/resume by the Pipe A quirk Thomas Richter
2014-06-03 14:45 ` Daniel Vetter
2014-06-03 15:04 ` Thomas Richter
2014-06-03 15:14 ` Chris Wilson
2014-06-03 15:19 ` Thomas Richter [this message]
2014-06-03 15:26 ` Chris Wilson
2014-06-03 15:50 ` Thomas Richter
2014-06-03 16:03 ` Chris Wilson
[not found] ` <17205_1401811442_538DF1F2_17205_16362_1_20140603160352.GA6129@nuc-i3427.alporthouse.com>
2014-06-04 22:43 ` Bug: Pipe A underrun on resolution switching on 830MG Thomas Richter
2014-06-08 21:20 ` Broken suspend/resume on i830 (with debug information) Thomas Richter
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=538DE77E.9080502@rus.uni-stuttgart.de \
--to=richter@rus.uni-stuttgart.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thor@math.tu-berlin.de \
--cc=ville.syrjala@linux.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