From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Jackson Subject: Re: Setting proper video mode Date: Mon, 31 Oct 2011 12:42:47 -0400 Message-ID: <4EAED007.3060004@redhat.com> References: <1319893248.7964.58.camel@tower.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by gabe.freedesktop.org (Postfix) with ESMTP id 374B79E86C for ; Mon, 31 Oct 2011 09:55:31 -0700 (PDT) In-Reply-To: <1319893248.7964.58.camel@tower.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Jarek Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On 10/29/11 9:00 AM, Jarek wrote: > Is there something beside the modeline, which my affect setting display > mode ? How to compare what is set with iegd that the display is working, > and how to force xf86-video-intel to do the same ? The first thing that comes to mind is infoframe setup for HDMI. Is this an HDMI display? Also, how does the output of intel_reg_dumper compare between the two drivers? > The modeline is exactly the same, except refresh rate, which in iegd is > 61Hz, and in xf86-video-intel is 61.7 - I don't think that such small > difference may affect the display. If they're exactly the same then they can't really have different refresh rates. Refresh rate is a derived quantity, the modeline actually stores the pixel clock rate. If you were seeing different refresh rates in the log file then you were seeing an artifact of the roundoff math of the thing printing them. On the other hand you might be reporting the refresh rate as seen on the LCD's on-screen display, if it has one, in which case it's a little weirder. That would indicate that you really are sending different timings to the display, possibly because the PLL search code in iegd picked a different answer. But dumping the m/n/p registers would tell you. - ajax