From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49943] radeon/drm: Hotplug udev events stop working
Date: Fri, 18 May 2012 13:35:44 +0000 [thread overview]
Message-ID: <bug-49943-502-akUGT3Isrn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49943-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=49943
--- Comment #1 from Harald Judt <h.judt@gmx.at> 2012-05-18 06:35:44 PDT ---
Ok, I've run radeonreg, here is the output:
Before HDMI connected:
0x601c 0x00000000 (0)
0x6028 0x06000012 (100663314)
0x6034 0x00000012 (18)
0x6040 0x00000000 (0)
0x604c 0x00000000 (0)
0x6058 0x00000000 (0)
HDMI connected:
0x601c 0x00000000 (0)
0x6028 0x06000012 (100663314)
0x6034 0x00000012 (18)
0x6040 0x00000000 (0)
0x604c 0x00000000 (0)
0x6058 0xff000012 (-16777198)
HDMI disconnected:
0x601c 0x00000000 (0)
0x6028 0x06000012 (100663314)
0x6034 0x00000012 (18)
0x6040 0x00000000 (0)
0x604c 0x00000000 (0)
0x6058 0xff0ff000 (-15732736)
The value of reg 0x6058 changes (HDMI-0). As you can see, after HDMI has been
disconnected, it is different from the original value (0). I suspect that there
is some problem with this?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-05-18 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:00 [Bug 49943] New: radeon/drm: Hotplug udev events stop working bugzilla-daemon
2012-05-18 13:35 ` bugzilla-daemon [this message]
2012-05-18 13:45 ` [Bug 49943] " bugzilla-daemon
2012-05-20 12:05 ` bugzilla-daemon
2012-06-14 16:44 ` bugzilla-daemon
2012-06-14 22:14 ` bugzilla-daemon
2012-06-14 22:20 ` bugzilla-daemon
2012-06-14 23:09 ` bugzilla-daemon
2012-09-21 16:05 ` bugzilla-daemon
2012-10-04 15:50 ` bugzilla-daemon
2012-10-04 16:20 ` bugzilla-daemon
2019-11-19 8:26 ` 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-49943-502-akUGT3Isrn@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