From: Mike Isely <isely@isely.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Dave Airlied <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org,
Mike Isely at pobox <isely@pobox.com>
Subject: Re: [PATCH 2/2] drm/i915/lvds: Use i915.lvds_fixed_mode= as a last resort
Date: Wed, 4 May 2011 17:14:14 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.1.10.1105041703500.8641@cnc.isely.net> (raw)
In-Reply-To: <alpine.DEB.1.10.1104211745040.18161@cnc.isely.net>
On Thu, 21 Apr 2011, Mike Isely wrote:
> On Thu, 21 Apr 2011, Chris Wilson wrote:
>
> > On Thu, 21 Apr 2011 17:30:21 -0500 (CDT), Mike Isely <isely@isely.net> wrote:
> > > It looks like the driver did notice the specified mode and used it -
> > > because the display's refresh rate did get adjusted and the overall
> > > resolution is correct. However the display timings are slightly "off",
> > > the image is stretched a few pixels off the right edge and a few lines
> > > off the bottom edge. Yet the same modeline given to "video=" in
> > > combination with my controversial disable-fixed-mode patch however
> > > produces a perfectly aligned image.
> >
> > Adding a few printk will help. And perhaps comparing the resultant register
> > settings with intel_reg_dumper.
>
> Oh absolutely. But right now I'm not doing a very fair apples-to-apples
> comparison. I need to address that first and make sure nothing else is
> influencing this.
>
> -Mike
>
Chris:
Sorry this simple thing has taken 2 weeks, but I'm having to time-slice
a lot of different tasks at the moment. People keep pulling me away
from this :-( However I've finally dug down and found the problem.
There's a bug in the function drm_mode_parse_command_line_for_connector
(the subject of this thread) that is leaving the margins field
uninitialized. This has been the cause all along for the differing
results I was getting.
This bug didn't start with the underlying patch ("Use
i915.lvds_fixed_mode= as a last resort"). I also looked at
drm_fb_helper_connector_parse_command_line from before this patch and it
looks like the same bug exists there. Amazing that nobody has noticed
this.
Patch to follow.
-Mike
--
Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
next prev parent reply other threads:[~2011-05-04 22:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 6:43 [PATCH 1/2] drm: Export the command-line mode parser Chris Wilson
2011-04-17 6:43 ` [PATCH 2/2] drm/i915/lvds: Use i915.lvds_fixed_mode= as a last resort Chris Wilson
2011-04-18 16:46 ` Mike Isely
2011-04-18 17:46 ` Mike Isely
2011-04-20 19:48 ` Mike Isely
2011-04-20 19:56 ` Chris Wilson
2011-04-20 20:09 ` Mike Isely
2011-04-21 22:30 ` Mike Isely
2011-04-21 22:37 ` Chris Wilson
2011-04-21 22:46 ` Mike Isely
2011-05-04 22:14 ` Mike Isely [this message]
2011-05-04 22:18 ` [PATCH] drm/i915: Fix unset margins flag in drm_mode_parse_command_line_for_connector Mike Isely
2011-05-05 2:40 ` Robert Lowery
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=alpine.DEB.1.10.1105041703500.8641@cnc.isely.net \
--to=isely@isely.net \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=isely@pobox.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;
as well as URLs for NNTP newsgroup(s).