From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 27314] displayport link training fails on certain panels
(channel equalization fails)
Date: Wed, 23 Mar 2011 09:46:22 -0700 (PDT)
Message-ID: <20110323164623.12B0F13004E@annarchy.freedesktop.org>
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 15F159E74D
for ;
Wed, 23 Mar 2011 09:46:23 -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=27314
--- Comment #36 from Alex Deucher 2011-03-23 09:46:22 PDT ---
(In reply to comment #35)
> Just out of curiosity, why is link training implemented on driver level and not
> on drm level? I see that nouvau and radeon each have their own implementation.
> The algorithm does not depend on the card, right? Only the way voltage,
> patterns etc are set does. Maybe by merging them the problem can be found.
The link training algo is the same across all chips in theory (it's defined in
a VESA spec). However, there are often a lot of asic specific things that need
to be handled. It would probably be doable if you could figure out the right
set of callbacks and driver adjustable fields to make all the drivers happy.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.