From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43487] [HD6320] Corrupted displays (LVDS and HDMI) after connecting HDMI
Date: Sat, 03 Dec 2011 11:23:42 +0000 [thread overview]
Message-ID: <bug-43487-502-78NryqSCXs@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-43487-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=43487
--- Comment #1 from Rafał Miłecki <zajec5@gmail.com> 2011-12-03 03:23:42 PST ---
** LVDS corruption **
LVDS corruption consists of two problems:
1) Display is corrupted
2) Everything is moved (bottom and right parts of display are black)
Ad 1
After booting (without HDMI connected) register 0x6818 is set to 0x00000640.
When I connect HDMI, driver changes it to 0x00000580. I have no idea why does
it happen, but it's source of the corruption. Setting it back with:
avivotool regset 0x6818 0x00000640
removes corruption. I believe register is defined as:
#define EVERGREEN_GRPH_PITCH 0x6818
With fglrx register 0x6818 is set to 0x640 all the time (with HDMI and without)
Ad 2
After booting (without HDMI connected) register 0x6810 is set to 0x00000000.
When I connect HDMI, driver changes it to 0x00142000. It's the source of moved
display. Setting it back with:
avivotool regset 0x6810 0x00000000
removes movement. I believe register is defined as:
#define EVERGREEN_GRPH_PRIMARY_SURFACE_ADDRESS 0x6810
With fglrx register 0x6810 is set to 0 all the time (with HDMI and without)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-12-03 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 11:13 [Bug 43487] New: [HD6320] Corrupted displays (LVDS and HDMI) after connecting HDMI bugzilla-daemon
2011-12-03 3:33 ` [Bug 43487] " bugzilla-daemon
2011-12-03 11:23 ` bugzilla-daemon [this message]
2011-12-03 11:47 ` bugzilla-daemon
2011-12-03 12:09 ` 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-43487-502-78NryqSCXs@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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