From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 48880] Set mode has different timings than requested on VGA
Date: Thu, 19 Apr 2012 14:20:44 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 1F71C9E7D9
for ;
Thu, 19 Apr 2012 07:20: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
https://bugs.freedesktop.org/show_bug.cgi?id=48880
--- Comment #21 from Alex Deucher 2012-04-19 07:20:44 PDT ---
(In reply to comment #20)
> What about the BIOS bug angle? Because kernel is not setting up the hardware
> directly, but asking the BIOS to do it, right? Is that out of the question?
It's not out of the question, but I highly doubt it. The driver calculates the
pll dividers and the atom table basically writes them to the pll registers. If
there was a bug in the table, I'd expect it to cause problems across the board,
not just on one mode on one monitor. We've had lots of these kind of bugs over
the course of the driver's life. Some combinations of dividers and monitors
are just not happy. The trick is to tweak the algo just enough to fix the
problematic monitor while not breaking others. I'll test
RADEON_PLL_USE_FRAC_FB_DIV on the hw I have here and if all goes well, I'll
send it to Dave.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.