From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 69675] audio broken in 24Hz/24p since 3.11 (regression) Date: Thu, 26 Sep 2013 04:48:44 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1610932203==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2F555E61A4 for ; Wed, 25 Sep 2013 21:48:44 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1610932203== Content-Type: multipart/alternative; boundary="1380170924.aEBAFb1.32283"; charset="us-ascii" --1380170924.aEBAFb1.32283 Date: Thu, 26 Sep 2013 04:48:43 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=69675 --- Comment #10 from Pierre Ossman --- (In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #4) > > > Something like this: > > > > Not really, the selection doesn't work like that - clock has to match > > exactly to the table value, it is not an upper bound. > > I just meant to patch the table so that you end up using the pre-defined > values for CTS and N rather than calculating them from the formula. > > { xxx, 11648, 210937, 17836, 234375, 11648, 140625 }, /* 74.25/1.001 MHz */ > > Replace xxx with whatever clock value the drm edid code gives you for > 74.25/1.001 MHz. > So what should I actually try for the second patch? What you wrote? Or the value from the mode line? :) -- You are receiving this mail because: You are the assignee for the bug. --1380170924.aEBAFb1.32283 Date: Thu, 26 Sep 2013 04:48:44 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 10 on bug 69675 from 
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > Something like this:
> > 
> > Not really, the selection doesn't work like that - clock has to match
> > exactly to the table value, it is not an upper bound.
> 
> I just meant to patch the table so that you end up using the pre-defined
> values for CTS and N rather than calculating them from the formula.
> 
> {  xxx, 11648, 210937, 17836, 234375, 11648, 140625 }, /*  74.25/1.001 MHz */
> 
> Replace xxx with whatever clock value the drm edid code gives you for
> 74.25/1.001 MHz.
> 

So what should I actually try for the second patch? What you wrote? Or the
value from the mode line? :)

You are receiving this mail because:
  • You are the assignee for the bug.
--1380170924.aEBAFb1.32283-- --===============1610932203== 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 --===============1610932203==--