lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 4 Feb 2011 11:42:33 +1000
From:	Dave Airlie <>
To:	Linus Torvalds <>
Cc:	Keith Packard <>,
	Carlos Mafra <>,
	Dave Airlie <>,
	"Rafael J. Wysocki" <>, Takashi Iwai <>,
	Linux Kernel Mailing List <>,
	Maciej Rutecki <>,
	Florian Mickler <>,
	Andrew Morton <>,
	Kernel Testers List <>,
	Network Development <>,
	Linux ACPI <>,
	Linux PM List <>,
	Linux SCSI List <>,
	Linux Wireless List <>,
	DRI <>
Subject: Re: 2.6.38-rc3-git1: Reported regressions 2.6.36 -> 2.6.37

On Fri, Feb 4, 2011 at 11:11 AM, Linus Torvalds
<> wrote:
> On Thu, Feb 3, 2011 at 5:05 PM, Keith Packard <> wrote:
>> 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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists