Andrew Morton <[EMAIL PROTECTED]> 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
