From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26195] New: Green screen on HDMI with RV730
Date: Sun, 24 Jan 2010 06:56:10 -0800 (PST) [thread overview]
Message-ID: <bug-26195-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=26195
Summary: Green screen on HDMI with RV730
Product: DRI
Version: XOrg CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: mike@fireburn.co.uk
CC: mike@fireburn.co.uk
I've noticed on both Linus's mainline and the radeon testing branch
that I have a green tinge to the screen after KMS is initialised
I've done my best with git bisect however there are a few un-compilable commits
I've narrowed it down too:
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
4143e919ea999c9356ae4f71b5a3a80e075290d5
f92a8b6758bdc0f277c4f42aa7d736a205ac9ded
5801ead6bd6bddf5505d6eab55f84d8ee8106cd8
6a93cb250a60af1bb7b4070949f8546a2fdc52ef
1a66c95a64c9ae0bc8382254f544b24b23f498ec
ffd09c648a76a1cf96872c033e98d4730f9b10a4
54d9cb47dd6a754e434e5adeccb3a1e2835594fd
746c1aa4d100f7441423050f34be79f401fbf7d4
5fbfce7fc906c4a9e3d5e0872e5d6affaca54761
d904ef9b00a4473af16766e99f17bdbb5f0fde65
58682f107ad5178e47a45af3af1851442d05d7fc
We cannot bisect more!
I hope this helps - for information each of these was compiled with
radeon built in and the R600_rlc.bin and R700_rlc.bin compiled into
the kernel too
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
--
next reply other threads:[~2010-01-24 14:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 14:56 bugzilla-daemon [this message]
2010-01-24 16:55 ` [Bug 26195] Green screen on HDMI with RV730 bugzilla-daemon
2010-01-27 17:33 ` bugzilla-daemon
2010-01-27 17:34 ` bugzilla-daemon
2010-01-29 19:23 ` bugzilla-daemon
2010-02-25 9:29 ` bugzilla-daemon
2010-02-25 14:46 ` bugzilla-daemon
2010-02-25 15:35 ` bugzilla-daemon
2010-02-25 15:56 ` bugzilla-daemon
2010-02-25 23:02 ` bugzilla-daemon
2010-02-25 23:24 ` bugzilla-daemon
2010-02-26 11:50 ` bugzilla-daemon
2010-02-26 11:54 ` bugzilla-daemon
2010-02-27 14:38 ` bugzilla-daemon
2010-02-27 14:38 ` bugzilla-daemon
2010-03-05 21:04 ` bugzilla-daemon
2010-03-05 23:22 ` bugzilla-daemon
2010-03-06 1:25 ` bugzilla-daemon
2010-04-04 14:03 ` bugzilla-daemon
2010-04-04 14:05 ` bugzilla-daemon
2010-04-04 14:11 ` bugzilla-daemon
2010-04-13 5:11 ` bugzilla-daemon
2010-04-13 12:56 ` bugzilla-daemon
2010-04-13 13:37 ` bugzilla-daemon
2010-04-13 19:21 ` bugzilla-daemon
2010-04-13 19:59 ` bugzilla-daemon
2010-04-13 20:56 ` bugzilla-daemon
2010-04-13 21:04 ` bugzilla-daemon
2011-06-30 10: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-26195-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 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.