public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: i915 driver doesn't find all Modelines that nouveau driver finds
Date: Tue, 3 Mar 2015 15:03:43 +0200	[thread overview]
Message-ID: <20150303130343.GC11371@intel.com> (raw)
In-Reply-To: <1425327376.5905.14.camel@interlinx.bc.ca>

On Mon, Mar 02, 2015 at 03:16:16PM -0500, Brian J. Murrell wrote:
> On Mon, 2015-03-02 at 20:44 +0200, Ville Syrjälä wrote:
> > On Mon, Mar 02, 2015 at 07:07:47PM +0100, Daniel Vetter wrote:
> > > On Mon, Mar 02, 2015 at 11:33:39AM -0500, Brian J. Murrell wrote:
> > > > 
> > > > [   50.508381] [drm:drm_mode_debug_printmodeline] Modeline 27:"1600x1200" 0 202500 1600 1664 1856 2160 1200 1201 1204 1250 0x40 0x5
> > > > [   50.508383] [drm:drm_mode_prune_invalid] Not using 1600x1200 mode 15
> > > > [   50.508385] [drm:drm_mode_debug_printmodeline] Modeline 28:"1600x1200" 0 189000 1600 1664 1856 2160 1200 1201 1204 1250 0x40 0x5
> > > > [   50.508385] [drm:drm_mode_prune_invalid] Not using 1600x1200 mode 15
> > > > [   50.508387] [drm:drm_mode_debug_printmodeline] Modeline 66:"1400x1050" 0 179500 1400 1504 1656 1912 1050 1053 1057 1105 0x40 0x6
> > > > [   50.508388] [drm:drm_mode_prune_invalid] Not using 1400x1050 mode 15
> > > > [   50.508390] [drm:drm_mode_debug_printmodeline] Modeline 71:"1600x1200" 0 175500 1600 1664 1856 2160 1200 1201 1204 1250 0x40 0x5
> > > > [   50.508390] [drm:drm_mode_prune_invalid] Not using 1600x1200 mode 15
> > > > 
> 
> > The <180MHz modes are dropped only due to the +5% we add to account for SSC on
> > FDI. I wonder if we really need that much?
> 
> I guess this would get me the "71" modeline but not the "27" one.  Any
> idea what refresh rate that "71" would be at?  I forget how to do all of
> that video timing math.

175500*1000/2160/1250 = 65

Oh that's an a CRT monitor you have there. Been a while since I've
come across one of those :) 65Hz on a CRT sounds like a good way to
get a headache to me.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-03 13:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01 19:12 i915 driver doesn't find all Modelines that nouveau driver finds Brian J. Murrell
2015-03-02  9:07 ` Chris Wilson
2015-03-02 11:16   ` Brian J. Murrell
2015-03-02 16:33   ` Brian J. Murrell
2015-03-02 18:07     ` Daniel Vetter
2015-03-02 18:44       ` Ville Syrjälä
2015-03-02 20:16         ` Brian J. Murrell
2015-03-03 13:03           ` Ville Syrjälä [this message]
2015-03-03 13:16             ` Brian J. Murrell
2015-03-03 13:31               ` Ville Syrjälä
2015-03-03 16:44                 ` Brian J. Murrell
2015-03-03 18:40                   ` Jani Nikula
2015-03-03 19:04                     ` Brian J. Murrell
2015-03-03 19:16                       ` Jani Nikula
2015-03-02 20:08       ` Brian J. Murrell

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=20150303130343.GC11371@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=brian@interlinx.bc.ca \
    --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