lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20071026175143.GB1573@elf.ucw.cz> Date: Fri, 26 Oct 2007 19:51:43 +0200 From: Pavel Machek <pavel@....cz> To: Krzysztof Halasa <khc@...waw.pl> Cc: Andrew Morton <akpm@...ux-foundation.org>, sylvain.meyer@...ldonline.fr, linux-kernel@...r.kernel.org, "Antonino A. Daplas" <adaplas@....net>, linux-fbdev-devel@...ts.sourceforge.net Subject: Re: [PATCH] Intel FB pixel clock calculation fix On Tue 2007-09-11 14:18:57, Krzysztof Halasa wrote: > Andrew Morton <akpm@...ux-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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists