From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Yves-Alexis Perez <corsac@debian.org>
Cc: Thomas Renninger <trenn@suse.de>,
ak@linux.intel.com, linux-acpi@vger.kernel.org,
linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Julia Jomantaite <julia.jomantaite@gmail.com>,
marcus@better.se, dannybaumann@web.de
Subject: Re: [PATCH 1/2] ACPI Video: Ignore devices that aren't present in hardware
Date: Thu, 3 Jul 2008 20:24:05 +0100 [thread overview]
Message-ID: <20080703192405.GB32260@srcf.ucam.org> (raw)
In-Reply-To: <20080703162134.GI6755@corsac.net>
On Thu, Jul 03, 2008 at 06:21:34PM +0200, Yves-Alexis Perez wrote:
> I dont know if it's the same thing, but I remember at one time that when
> pressing my brightness keys (on a T61, intel graphics), the acpi event
> appeared in /proc/acpi/event like 1 second later. I didn't check
> precisely, but it could really be those 750ms. Irrc, this was only
> happening after first suspend to ram.
Yes, it's the same issue.
> Do these patches mean that, maybe in 2.6.27, brightness keys would work
> directly from kernel, without needing hal, gnome-power-manager or
> anything else, like X?
Right.
> I can try those patches and report back, but on which kernel should I
> apply them? 2.6.26-rc8? Or some git?
It's against drm git - search the dri-devel archives for the patch.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-07-03 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 16:05 [PATCH 1/2] ACPI Video: Ignore devices that aren't present in hardware Thomas Renninger
2008-07-03 16:08 ` Matthew Garrett
2008-07-03 16:15 ` Thomas Renninger
2008-07-03 16:16 ` Matthew Garrett
2008-07-03 16:21 ` Yves-Alexis Perez
2008-07-03 19:24 ` Matthew Garrett [this message]
2008-07-04 10:08 ` Thomas Renninger
2008-07-04 10:18 ` Matthew Garrett
2008-07-04 3:09 ` Henrique de Moraes Holschuh
2008-07-04 9:13 ` Matthew Garrett
2008-07-04 11:55 ` Henrique de Moraes Holschuh
2008-07-04 17:39 ` Matthew Garrett
2008-07-04 19:49 ` Henrique de Moraes Holschuh
2008-07-05 15:46 ` Henrique de Moraes Holschuh
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=20080703192405.GB32260@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=corsac@debian.org \
--cc=dannybaumann@web.de \
--cc=julia.jomantaite@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcus@better.se \
--cc=trenn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.