Thread (17 messages) 17 messages, 6 authors, 2011-02-04

Re: 2.6.38-rc3-git1: Reported regressions 2.6.36 -> 2.6.37

From: Dave Airlie <airlied@gmail.com>
Date: 2011-02-04 01:42:37
Also in: dri-devel, linux-acpi, linux-scsi, lkml, netdev

On Fri, Feb 4, 2011 at 11:11 AM, Linus Torvalds
[off-list ref] wrote:
On Thu, Feb 3, 2011 at 5:05 PM, Keith Packard [off-list ref] wrote:
quoted
The goal is to make it so that when you *do* set a mode, DPMS gets set
to ON (as the monitor will actually be "on" at that point). Here's a
patch which does the DPMS_ON precisely when setting a mode.
Ok, patch looks sane, but it does leave me with the "what about the
'fb_changed' case?" question. Is that case basically guaranteed to not
change any existing dpms state?
Yes its inconsistent behaviour but nothing in the fb_changed case will
affect the DPMS
state. I expect we should probably do that so all paths via that
function turn DPMS on,
and it'll be consistent, might be something for 39.

Dave.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help