From: Krzysztof Halasa <khc@pm.waw.pl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sylvain.meyer@worldonline.fr, linux-kernel@vger.kernel.org,
"Antonino A. Daplas" <adaplas@pol.net>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] Intel FB pixel clock calculation fix
Date: Tue, 11 Sep 2007 14:18:57 +0200 [thread overview]
Message-ID: <m3veah75u6.fsf@maximus.localdomain> (raw)
In-Reply-To: <20070910225221.f0eaf22c.akpm@linux-foundation.org> (Andrew Morton's message of "Mon, 10 Sep 2007 22:52:21 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
>> Intel framebuffer mis-calculated pixel clocks.
> and... what are the consequences of this miscalculation? I need to know
> such things so that I can decide whether a change is needed in 2.6.23. And
> 2.6.22.
The pixel clock (and thus both H and V sync) will be slower than
requested, so if you set the minimum allowed the display may not
sync. In case of really old CRT display it could theoretically
damage it.
I'm using it with PAL TV (using RGB input - SCART connector) and
the bug prevented it from working at all (TV requirements are more
strict and made the bug visible).
I think 2.6.22 would be overkill, .23 - not sure.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-09-11 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3ir6il3wl.fsf@maximus.localdomain>
2007-09-11 5:52 ` [PATCH] Intel FB pixel clock calculation fix Andrew Morton
2007-09-11 12:18 ` Krzysztof Halasa [this message]
2007-09-12 4:17 ` suresh gani
2007-10-26 17:51 ` Pavel Machek
2007-10-26 19:58 ` Krzysztof Halasa
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=m3veah75u6.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=adaplas@pol.net \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvain.meyer@worldonline.fr \
/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).