From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60639] RV635: Kernel displays black screen when monitor is connect via DisplayPort
Date: Tue, 17 Feb 2015 08:59:34 +0000 [thread overview]
Message-ID: <bug-60639-2300-WvrFImfdWY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60639-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60639
--- Comment #22 from Marco Krüger <krgsch@gmail.com> ---
Created attachment 167291
--> https://bugzilla.kernel.org/attachment.cgi?id=167291&action=edit
AMD Turks - Xrandr
--
You are receiving this mail because:
You are watching the assignee of 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:[~2015-02-17 8:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 8:19 [Bug 60639] New: RV635: Kernel displays black screen when monitor is connect via DisplayPort bugzilla-daemon
2013-07-28 20:16 ` [Bug 60639] " bugzilla-daemon
2013-07-30 4:28 ` bugzilla-daemon
2013-07-31 5:03 ` bugzilla-daemon
2013-07-31 13:07 ` bugzilla-daemon
2013-08-26 3:31 ` bugzilla-daemon
2013-08-26 3:34 ` bugzilla-daemon
2013-08-26 3:36 ` bugzilla-daemon
2013-08-26 3:39 ` bugzilla-daemon
2013-08-26 3:41 ` bugzilla-daemon
2013-08-26 16:34 ` bugzilla-daemon
2013-08-27 2:26 ` bugzilla-daemon
2013-10-01 3:52 ` bugzilla-daemon
2013-10-10 20:54 ` bugzilla-daemon
2013-10-11 5:41 ` bugzilla-daemon
2013-10-11 9:27 ` bugzilla-daemon
2013-11-06 14:17 ` bugzilla-daemon
2014-01-13 21:51 ` bugzilla-daemon
2015-02-17 8:56 ` bugzilla-daemon
2015-02-17 8:58 ` bugzilla-daemon
2015-02-17 8:58 ` bugzilla-daemon
2015-02-17 8:59 ` bugzilla-daemon
2015-02-17 8:59 ` bugzilla-daemon [this message]
2015-02-17 9:00 ` bugzilla-daemon
2015-02-17 14:03 ` 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-60639-2300-WvrFImfdWY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.