linux-kernel - Re: [PATCH] Add Intel ACPI IGD OpRegion support

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <20080806001301.GA10630@srcf.ucam.org>
Date:	Wed, 6 Aug 2008 01:13:01 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Yves-Alexis Perez <corsac@...ian.org>
Cc:	airlied@...ux.ie, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org
Subject: Re: [PATCH] Add Intel ACPI IGD OpRegion support

On Tue, Aug 05, 2008 at 11:47:54PM +0200, Yves-Alexis Perez wrote:

> In booted into X (with hal, powersaved, dbus etc. running), and then,
> tada, brightness keys work. There is a 750ms (I guess) delay, and I
> don't know who is really responsible, I guess X is. (and thus I guess
> the opregion is the one needed, and X manages the brightness. If the
> kernel was, it would be working even in single user)

The 750ms delay is from thinkpad-acpi. I sent a patch to Henrique which 
makes it go away, but I'm not entirely sure what the ACPI method 
concerned is supposed to be doing. The opregion code won't currently run 
until X is started because the drm layer requires X to be the foreground 
vt before handling IRQs.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/