From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 46711] Monitor not turning on after DisplayPort re-plug in Xorg
Date: Tue, 17 Apr 2012 15:45:04 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id AE1F99F368
for ;
Tue, 17 Apr 2012 08:45:04 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=46711
--- Comment #11 from Alex Deucher 2012-04-17 08:45:04 PDT ---
Created attachment 60177
--> https://bugs.freedesktop.org/attachment.cgi?id=60177
possible fix
(In reply to comment #10)
>
> So my question is why this saved_state business in radeon_connector_hotplug?
We don't want to change the DPMS state or the logic won't work for hotplug. If
this is the first time the monitor is plugged in, there is no mode set so we
don't want to turn the display on as it won't work, we just want to send the
event to userspace. If the user has configured the display already and then
replugs it or powers it off manually, then we want to power it back up in the
hotplug handler as that is what they expect.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.