From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations
Date: Sat, 29 Mar 2014 16:29:19 +0000 [thread overview]
Message-ID: <bug-76564-502-tWPHsXmND9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76564-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 676 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76564
--- Comment #35 from jeroen <jeroenk61@hotmail.com> ---
(In reply to comment #34)
> Why not increase the ref_div? hardware frying? That way you can get the
> clock exactly right.
>
> For example: 148.5 = 100 * 29.7 / 4 * 5
> 74.2 = 100 * 37.1 / 5 * 10
Just noticed that the clock values shown by xrandr are already rounded. So the
74.2MHz for 23.976fps actually is 74.17MHz. This would mean the PLL can never
exactly generate the clock that is requested by the television I guess.
Perhaps something else is wrong with the PLL then
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1559 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-03-29 16:29 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 17:32 [Bug 76564] New: [AMD Fusion E-350] Radeon UVD giving incorrect fps when playing videos bugzilla-daemon
2014-03-24 17:34 ` [Bug 76564] " bugzilla-daemon
2014-03-24 17:38 ` [Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations bugzilla-daemon
2014-03-24 17:39 ` bugzilla-daemon
2014-03-24 17:42 ` bugzilla-daemon
2014-03-24 18:49 ` bugzilla-daemon
2014-03-24 19:06 ` bugzilla-daemon
2014-03-24 19:16 ` bugzilla-daemon
2014-03-24 19:40 ` bugzilla-daemon
2014-03-24 20:39 ` bugzilla-daemon
2014-03-25 19:16 ` bugzilla-daemon
2014-03-25 19:55 ` bugzilla-daemon
2014-03-25 20:14 ` bugzilla-daemon
2014-03-25 20:21 ` bugzilla-daemon
2014-03-26 19:30 ` bugzilla-daemon
2014-03-26 20:50 ` bugzilla-daemon
2014-03-27 17:14 ` bugzilla-daemon
2014-03-27 17:53 ` bugzilla-daemon
2014-03-27 17:53 ` bugzilla-daemon
2014-03-27 18:22 ` bugzilla-daemon
2014-03-27 18:23 ` bugzilla-daemon
2014-03-27 18:24 ` bugzilla-daemon
2014-03-27 18:53 ` bugzilla-daemon
2014-03-28 14:08 ` bugzilla-daemon
2014-03-28 14:34 ` bugzilla-daemon
2014-03-28 14:37 ` bugzilla-daemon
2014-03-28 14:42 ` bugzilla-daemon
2014-03-28 15:18 ` bugzilla-daemon
2014-03-28 16:04 ` bugzilla-daemon
2014-03-28 16:22 ` bugzilla-daemon
2014-03-28 17:02 ` bugzilla-daemon
2014-03-28 17:06 ` bugzilla-daemon
2014-03-28 17:56 ` bugzilla-daemon
2014-03-28 18:06 ` bugzilla-daemon
2014-03-29 11:20 ` bugzilla-daemon
2014-03-29 14:03 ` bugzilla-daemon
2014-03-29 16:29 ` bugzilla-daemon [this message]
2014-03-29 18:18 ` bugzilla-daemon
2014-03-29 21:10 ` bugzilla-daemon
2014-03-30 12:33 ` bugzilla-daemon
2014-03-30 13:39 ` bugzilla-daemon
2014-03-30 15:27 ` bugzilla-daemon
2014-03-30 16:18 ` bugzilla-daemon
2014-03-31 7:49 ` bugzilla-daemon
2014-03-31 14:17 ` bugzilla-daemon
2014-03-31 15:59 ` bugzilla-daemon
2014-03-31 18:09 ` bugzilla-daemon
2014-03-31 20:42 ` bugzilla-daemon
2014-04-02 15:18 ` bugzilla-daemon
2014-04-02 16:20 ` bugzilla-daemon
2014-04-02 17:50 ` bugzilla-daemon
2014-04-02 19:59 ` bugzilla-daemon
2014-04-02 20:07 ` bugzilla-daemon
2014-04-02 20:25 ` bugzilla-daemon
2014-04-03 3:24 ` bugzilla-daemon
2014-04-03 3:34 ` bugzilla-daemon
2014-04-03 4:16 ` bugzilla-daemon
2014-04-03 7:39 ` bugzilla-daemon
2014-04-03 16:59 ` bugzilla-daemon
2014-04-03 19:26 ` bugzilla-daemon
2014-04-03 19:27 ` bugzilla-daemon
2014-04-03 19:29 ` bugzilla-daemon
2014-04-04 8:06 ` bugzilla-daemon
2014-04-04 17:50 ` bugzilla-daemon
2014-04-23 8:46 ` bugzilla-daemon
2014-04-23 15:43 ` bugzilla-daemon
2014-04-23 15:45 ` bugzilla-daemon
2014-04-24 6:37 ` bugzilla-daemon
2014-04-24 13:49 ` bugzilla-daemon
2014-04-24 15:53 ` bugzilla-daemon
2014-04-27 13:12 ` bugzilla-daemon
2014-04-27 13:25 ` bugzilla-daemon
2014-04-27 14:42 ` bugzilla-daemon
2014-04-27 14:58 ` bugzilla-daemon
2014-04-27 15:27 ` bugzilla-daemon
2014-04-27 15:37 ` bugzilla-daemon
2014-04-27 17:15 ` bugzilla-daemon
2014-04-27 17:48 ` bugzilla-daemon
2014-04-28 8:23 ` bugzilla-daemon
2014-05-04 8:39 ` bugzilla-daemon
2014-05-04 8:40 ` bugzilla-daemon
2014-05-04 8:41 ` bugzilla-daemon
2014-05-04 8:41 ` bugzilla-daemon
2014-05-04 8:42 ` bugzilla-daemon
2014-05-04 8:42 ` bugzilla-daemon
2014-05-04 11:02 ` bugzilla-daemon
2014-05-04 13:48 ` bugzilla-daemon
2014-05-04 13:58 ` bugzilla-daemon
2014-05-04 14:45 ` bugzilla-daemon
2014-05-05 19:59 ` bugzilla-daemon
2016-06-15 12:03 ` bugzilla-daemon
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=bug-76564-502-tWPHsXmND9@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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