From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26926] New: [KMS][RV635] broken colors/fonts on DVI-0 (DVI-1 is OK)
Date: Sat, 6 Mar 2010 07:03:08 -0800 (PST) [thread overview]
Message-ID: <bug-26926-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26926
Summary: [KMS][RV635] broken colors/fonts on DVI-0 (DVI-1 is OK)
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: zajec5@gmail.com
I've just tried KMS on my RV635 and my old D-SUB (analog) LCD displays colors
incorrectly when using DVI-0. When switching to DVI-1 it works fine.
Any idea what can be a reason? In both cases we use INTERNAL_KLDSCP_DACx.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-06 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 15:03 bugzilla-daemon [this message]
2010-03-06 15:03 ` [Bug 26926] [KMS][RV635] broken colors/fonts on DVI-0 (DVI-1 is OK) bugzilla-daemon
2010-03-06 15:04 ` bugzilla-daemon
2010-03-06 15:04 ` bugzilla-daemon
2010-03-06 15:04 ` bugzilla-daemon
2010-03-06 15:05 ` bugzilla-daemon
2010-03-06 15:08 ` bugzilla-daemon
2010-03-06 15:11 ` bugzilla-daemon
2010-03-06 15:28 ` bugzilla-daemon
2010-03-06 20:00 ` bugzilla-daemon
2010-04-19 18:48 ` bugzilla-daemon
2010-04-19 18:50 ` bugzilla-daemon
2010-04-22 5:29 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-26926-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox