<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations" href="https://bugs.freedesktop.org/show_bug.cgi?id=76564#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations" href="https://bugs.freedesktop.org/show_bug.cgi?id=76564">bug 76564</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to <a href="show_bug.cgi?id=76564#c10">comment #10</a>) > (In reply to <a href="show_bug.cgi?id=76564#c8">comment #8</a>) > > Okay, but doesnt that mean in this case it is a problem with the display > > (HDMI?) clock, as I am not using HDMI audio? > > > > Is there a way I could get more detailed logging of what is happening on my > > system? > > I don't know how XBMC calculates the frame rate off hand. The PLL used to > generate the display clock may not always match the exact pixel clock of the > monitor. The driver calculates pll dividers to get as close as possible to > the pixel clock of the display mode. See radeon_compute_pll_avivo() in > radeon_display.c Yeah, but on multiple occasions I had the feeling that fglrx might do a better job on this than the radeon kernel module. We might want to take a second look at this and try to compare the settings fglrx and radeon uses for the same mode.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>