From: Andy Furniss <andyqos@ukfsn.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Radeon monitor + hdmi TV regression between drm-core-next and drm-fixes
Date: Sun, 04 Nov 2012 21:00:53 +0000 [thread overview]
Message-ID: <5096D785.80401@ukfsn.org> (raw)
In-Reply-To: <CADnq5_Oo54p7-t-H4Bt5QOCHehDMJAvZb0zw18=R1-M=0zkGrA@mail.gmail.com>
Alex Deucher wrote:
> On Sun, Nov 4, 2012 at 10:27 AM, Andy Furniss <andyqos@ukfsn.org> wrote:
>> For the last 2 years when running a DVI 60Hz monitor with a radeon HD4890
>> and a (native 50Hz) HDMI TV I've been able to boot/startx with the TV off
>> and then turn TV on and -
>>
>> xrandr --output DVI-0 --auto
>>
>> to bring up the the TV and get a clone of monitor.
>>
>> This still works with drm-core-next but not with drm-fixes (todays or from a
>> few days ago).
>>
>> With df I now loose the monitor with signal out of range when doing above,
>> the TV output is OK. To get the monitor back I need to turn off TV, then
>> off/auto the monitor.
>>
>> xrandr --output DVI-0 --off
>> xrandr --output DVI-1 --off
>> xrandr --output DVI-1 --auto
>>
>> The output from xrandr while the monitor is showing signal out of range
>> looks normal.
>>
>> If I boot with the TV on it works OK.
>
> Can you bisect?
29dbe3bcd2e28e71823febdca989d63d5c27d152 is the first bad commit
commit 29dbe3bcd2e28e71823febdca989d63d5c27d152
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Fri Oct 5 10:22:02 2012 -0400
drm/radeon: allocate PPLLs from low to high
The order shouldn't matter, but there have been problems
reported on certain older asics. This behaves more
like the original code before the PPLL allocation
rework.
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>
next prev parent reply other threads:[~2012-11-04 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 15:27 Radeon monitor + hdmi TV regression between drm-core-next and drm-fixes Andy Furniss
2012-11-04 16:03 ` Alex Deucher
2012-11-04 21:00 ` Andy Furniss [this message]
2012-11-05 15:56 ` Alex Deucher
2012-11-05 17:54 ` Andy Furniss
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=5096D785.80401@ukfsn.org \
--to=andyqos@ukfsn.org \
--cc=alexdeucher@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).