From: Pavel Machek <pavel@ucw.cz>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: "Antonino A. Daplas" <adaplas@pol.net>,
Andrew Morton <akpm@linux-foundation.org>,
sylvain.meyer@worldonline.fr,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Intel FB pixel clock calculation fix
Date: Fri, 26 Oct 2007 19:51:43 +0200 [thread overview]
Message-ID: <20071026175143.GB1573@elf.ucw.cz> (raw)
In-Reply-To: <m3veah75u6.fsf@maximus.localdomain>
On Tue 2007-09-11 14:18:57, Krzysztof Halasa wrote:
> 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.
I don't think this is -stable kind of bug.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-26 17:51 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
2007-09-12 4:17 ` suresh gani
2007-10-26 17:51 ` Pavel Machek [this message]
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=20071026175143.GB1573@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=adaplas@pol.net \
--cc=akpm@linux-foundation.org \
--cc=khc@pm.waw.pl \
--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).