From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 76564] [AMD Fusion E-350] HDMI refresh rates doesn't match expectations Date: Sat, 29 Mar 2014 18:18:29 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2108924701==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 5A3796EB0E for ; Sat, 29 Mar 2014 11:18:29 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============2108924701== Content-Type: multipart/alternative; boundary="1396117109.87d71CDb1.17074"; charset="us-ascii" --1396117109.87d71CDb1.17074 Date: Sat, 29 Mar 2014 18:18:29 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D76564 --- Comment #36 from Christian K=C3=B6nig --- (In reply to comment #35) > (In reply to comment #34) > > Why not increase the ref_div? hardware frying? That way you can get the > > clock exactly right. > >=20 > > For example: 148.5 =3D 100 * 29.7 / 4 * 5 > > 74.2 =3D 100 * 37.1 / 5 * 10 >=20 > 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 c= an > never exactly generate the clock that is requested by the television I gu= ess. >=20 > Perhaps something else is wrong with the PLL then The PLL is fine, you can't just represent some frequencies 100% correct. I'm already digging into making more use of the ref divider, just give me s= ome time to get the algorithem straight. --=20 You are receiving this mail because: You are the assignee for the bug. --1396117109.87d71CDb1.17074 Date: Sat, 29 Mar 2014 18:18:29 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 36 on bug 76564<= /a> from Christian K=C3=B6nig
(In reply to comment #=
35)
> (In reply to comment #34)
> > Why not increase the ref_div? hardware frying? That way you can g=
et the
> > clock exactly right.
> >=20
> > For example: 148.5 =3D 100 * 29.7 / 4 * 5
> >              74.2  =3D 100 * 37.1 / 5 * 10
>=20
> 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 PL=
L can
> never exactly generate the clock that is requested by the television I=
 guess.
>=20
> Perhaps something else is wrong with the PLL then

The PLL is fine, you can't just represent some frequencies 100% correct.

I'm already digging into making more use of the ref divider, just give me s=
ome
time to get the algorithem straight.


You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1396117109.87d71CDb1.17074-- --===============2108924701== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============2108924701==--