From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76231] New: radeon: DCE2 & DCE3 HDMI setup should be updated/improved (to match fglrx)
Date: Wed, 14 May 2014 20:56:23 +0000 [thread overview]
Message-ID: <bug-76231-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=76231
Bug ID: 76231
Summary: radeon: DCE2 & DCE3 HDMI setup should be
updated/improved (to match fglrx)
Product: Drivers
Version: 2.5
Kernel Version: torvalds/linux.git
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: zajec5@gmail.com
Regression: No
Created attachment 136121
--> https://bugzilla.kernel.org/attachment.cgi?id=136121&action=edit
Log of fglrx with DCE 2.0 and DCE 3.0 cards (HDMI setup)
Current code isn't based on a perfect RE method, we were mostly observing
registers, not tracing fglrx operations.
It should be a good idea to trace fglrx operations and improve radeon's code to
match it as much as possible.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2014-05-14 20:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-76231-2300@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.