From: Jon Masters <jonathan@jonmasters.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: PROBLEM: i915 modesetting - weird offset graphics (v2.6.37-rc1-27-gff8b16d)
Date: Fri, 05 Nov 2010 15:58:56 -0400 [thread overview]
Message-ID: <1288987136.3916.306.camel@constitution.bos.jonmasters.org> (raw)
In-Reply-To: <1288908847.3916.303.camel@constitution.bos.jonmasters.org>
On Thu, 2010-11-04 at 18:14 -0400, Jon Masters wrote:
> On Thu, 2010-11-04 at 13:41 +0000, Chris Wilson wrote:
> > On Thu, 04 Nov 2010 09:37:01 -0400, Jon Masters <jonathan@jonmasters.org> wrote:
> > > Also, the intel-gfx list is moderated with auto-rejection. Do I really
> > > need to subscribe to the list just to get a mail through?
> >
> > A few of the Intel gfx engineers are at Plumbers. If you tell Jesse about
> > it, he may be able to convince the powers-that-be to change the policy.
>
> I didn't see this mail in time. I did show a few folks the corruption,
> ran the kernel with drm.debug=4, etc. and checked the modelines. xrandr
> and the kernel seem to report the same modes each time, but obviously
> the display is shifted. I see various changes in git (everything from
> EDID reading to actual modeline changes in the i915 code - various weird
> margin settings seem to exist that might well cause some offset in the
> display) that could be responsible, so I will bisect it now for you.
Bisection is running. Should post something over the weekend.
Jon.
next prev parent reply other threads:[~2010-11-05 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 7:25 PROBLEM: i915 modesetting - weird offset graphics (v2.6.37-rc1-27-gff8b16d) Jon Masters
2010-11-04 7:29 ` Jon Masters
2010-11-05 21:03 ` Jon Masters
2010-11-04 13:37 ` Jon Masters
2010-11-04 13:41 ` Chris Wilson
2010-11-04 22:14 ` Jon Masters
2010-11-05 19:58 ` Jon Masters [this message]
2010-11-04 23:25 ` Alan W. Irwin
2010-11-11 8:02 ` Maciej Rutecki
2010-11-11 8:22 ` Jon Masters
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=1288987136.3916.306.camel@constitution.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=chris@chris-wilson.co.uk \
--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