From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42727] radeon KMS with CRT TV
Date: Sat, 3 Mar 2012 10:03:14 GMT [thread overview]
Message-ID: <201203031003.q23A3EcK006402@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42727-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42727
--- Comment #32 from Aur <aprovin@linux62.org> 2012-03-03 10:03:13 ---
I'm back. I'm sorry for the delay...
I started computer with only DVI connected with KMS enabled.
-> xrandr --verbose (KMS-xrandr1-notv)
I connected the S-video cable
-> xrandr --verbose (KMS-xrandr2-tv-connected)
-> ./radeonreg regs avivo (KMS-radeonreg-just-connected)
-> xrandr --output S-video --auto
-> xrandr --verbose (KMS-xrandr3-tv-activated)
-> ./radeonreg regs avivo (KMS-radeonreg-connected-activated)
I started computer with only DVI connected with KMS disabled.
-> xrandr --verbose (UMS-xrandr1-notv)
I connected the S-video cable
-> xrandr --verbose (UMS-xrandr2-tv-connected)
=> TV not detected
-> ./radeonreg regs avivo (UMS-radeonreg-just-connected)
I also add ./radeonreg regs avivo without X session :
kms-radeonreg-noX
ums-radeonreg-noX
There is no change with your patch :
- dmesg (dmesg-patch-noX)
- dmesg (dmesg-patch-withX)
I also attach vbios.rom
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-03-03 10:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 12:06 [Bug 42727] New: radeon KMS with CRT TV bugzilla-daemon
2012-02-04 12:25 ` [Bug 42727] " bugzilla-daemon
2012-02-04 12:37 ` bugzilla-daemon
2012-02-09 9:13 ` bugzilla-daemon
2012-02-09 17:48 ` bugzilla-daemon
2012-02-09 18:29 ` bugzilla-daemon
2012-02-21 16:37 ` bugzilla-daemon
2012-02-26 14:12 ` bugzilla-daemon
2012-02-26 17:41 ` bugzilla-daemon
2012-02-27 2:13 ` bugzilla-daemon
2012-02-27 13:54 ` bugzilla-daemon
2012-02-27 14:26 ` bugzilla-daemon
2012-02-27 14:26 ` bugzilla-daemon
2012-02-27 15:31 ` bugzilla-daemon
2012-02-28 2:10 ` bugzilla-daemon
2012-02-28 12:49 ` bugzilla-daemon
2012-02-28 12:50 ` bugzilla-daemon
2012-02-28 12:50 ` bugzilla-daemon
2012-02-28 12:50 ` bugzilla-daemon
2012-02-28 15:50 ` bugzilla-daemon
2012-02-28 16:29 ` bugzilla-daemon
2012-02-29 21:04 ` bugzilla-daemon
2012-03-01 13:39 ` bugzilla-daemon
2012-03-01 14:40 ` bugzilla-daemon
2012-03-01 14:45 ` bugzilla-daemon
2012-03-01 15:04 ` bugzilla-daemon
2012-03-01 15:53 ` bugzilla-daemon
2012-03-01 16:13 ` bugzilla-daemon
2012-03-01 16:18 ` bugzilla-daemon
2012-03-01 16:26 ` bugzilla-daemon
2012-03-02 13:34 ` bugzilla-daemon
2012-03-02 13:35 ` bugzilla-daemon
2012-03-03 10:03 ` bugzilla-daemon [this message]
2012-03-03 10:04 ` bugzilla-daemon
2012-03-03 10:04 ` bugzilla-daemon
2012-03-03 10:05 ` bugzilla-daemon
2012-03-03 10:05 ` bugzilla-daemon
2012-03-03 10:06 ` bugzilla-daemon
2012-03-03 10:07 ` bugzilla-daemon
2012-03-03 10:07 ` bugzilla-daemon
2012-03-03 10:07 ` bugzilla-daemon
2012-03-03 10:08 ` bugzilla-daemon
2012-03-03 10:08 ` bugzilla-daemon
2012-03-03 10:09 ` bugzilla-daemon
2012-03-03 10:10 ` bugzilla-daemon
2012-03-03 10:10 ` bugzilla-daemon
2012-04-01 4:52 ` bugzilla-daemon
2012-04-01 13:03 ` bugzilla-daemon
2012-04-01 15:29 ` bugzilla-daemon
2012-05-29 4:34 ` 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=201203031003.q23A3EcK006402@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox