public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Francois Rigaut <frigaut@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Fwd: Re: Macbook Pro Retina display problems
Date: Wed, 08 Aug 2012 00:17:50 +1000	[thread overview]
Message-ID: <5021238E.7040609@gmail.com> (raw)
In-Reply-To: <20120807125342.GD10377@phenom.ffwll.local>

Daniel,

ok, updated intel-gpu-tools and dumped the various config.
Unfortunately, X froze when I tried the to switch to pipe C (--crtc 2). 
I have three dumps with the various config:

http://maumae.net/retina/intel_corrupted_drm_debug/ird_inteldie << 
that's with i915.die=1

http://maumae.net/retina/intel_corrupted_drm_debug/ird_i915_loaded_notC_inX 
 << that's with i915 loaded, within X, and not switched to pipe C (had 
restarted X after the freeze mentionned above)

http://maumae.net/retina/intel_corrupted_drm_debug/ird_i915_loaded_from_fb 
 << that with i915 loaded, switch to pipe C (probably not working) and 
done in a console (the freeze didn't affect the keyboard so I was able 
to switch VT). Probably not very useful.

Hope that helps,
Thanks,
Francois

On Tue 07 Aug 2012 22:53:42 EST, Daniel Vetter wrote:
> On Tue, Aug 07, 2012 at 06:08:51PM +1000, Francois Rigaut wrote:
>> Daniel,
>>
>> nope, the hack didn't succeed. No apparent change.
>
> Ok, I've updated the reg_dumper to also dump the registers for pipe C. Can
> you please update your intel-gpu-tools checkout and then grab a new
> register dump for both i915 loaded and not loaded?
>
> To make comparing easier, please switch the panel to pipe C when i915 is
> loaded with
>
> $ xrandr --output eDP1 --auto --crtc 2
>
> that way the register dumps are much easier to compare.
>
> Thanks, Daniel

  reply	other threads:[~2012-08-07 14:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5019E550.40608@mso.anu.edu.au>
2012-08-02  3:37 ` Fwd: Re: Macbook Pro Retina display problems Francois Rigaut
2012-08-06  7:12   ` Daniel Vetter
2012-08-06  8:59     ` Francois Rigaut
2012-08-06  9:17       ` Daniel Vetter
2012-08-06 13:40         ` Francois Rigaut
2012-08-06 19:31           ` Daniel Vetter
2012-08-07  8:08             ` Francois Rigaut
2012-08-07 12:53               ` Daniel Vetter
2012-08-07 14:17                 ` Francois Rigaut [this message]
2012-08-07 15:19                   ` Daniel Vetter
2012-08-07 16:19                   ` Daniel Vetter
2012-08-08 12:35                     ` Francois Rigaut
2012-08-08 20:07                       ` Daniel Vetter
2012-08-10 16:49 Bernhard Froemel
2012-08-10 17:18 ` 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=5021238E.7040609@gmail.com \
    --to=frigaut@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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