From: Adam Jackson <ajax@redhat.com>
To: Jarek <jarek@poczta.srv.pl>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Setting proper video mode
Date: Mon, 31 Oct 2011 12:42:47 -0400 [thread overview]
Message-ID: <4EAED007.3060004@redhat.com> (raw)
In-Reply-To: <1319893248.7964.58.camel@tower.local>
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
next prev parent reply other threads:[~2011-10-31 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 13:00 Setting proper video mode Jarek
2011-10-31 16:42 ` Adam Jackson [this message]
2011-10-31 17:48 ` Jarek
2011-10-31 18:29 ` Adam Jackson
-- strict thread matches above, loose matches on Subject: below --
2011-11-02 10:46 jarek
2011-11-02 15:03 ` Adam Jackson
2011-11-03 10:17 jarek
2011-11-03 15:36 ` Adam Jackson
2011-11-04 8:52 jarek
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=4EAED007.3060004@redhat.com \
--to=ajax@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jarek@poczta.srv.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.