From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 17902] [830M missing dvo driver] need support for DVO-LVDS via
na2501
Date: Tue, 29 May 2012 19:13:12 +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 AC5139EF87
for ;
Tue, 29 May 2012 12:13:12 -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=17902
--- Comment #75 from thor@math.tu-berlin.de 2012-05-29 12:13:12 PDT ---
Well, I do have a documentation from National Semiconductors, but there is
nothing that would define frequencies or bandwidths - only the sync pulses can
be set, and intput to syncs. So I played writing values into all other
registers with i2cset, but with little success - not any change, actually,
except for the mentioned register. Ok, and you could block off the screen as
well by disabling the sync pulses (not much of a surprise, I guess).
However, leaving all that aside - I'm no longer able to talk to the chip, upon
rebooting i2cdetect gave me all blanks on bus #6. I really wonder what is going
on. Could it be that there is some additional "gating" going on that blocks off
access to this chip unless another register is set? Is that typical?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.