From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
linux-kernel@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH 2.6.29] eeepc-laptop: report brightness control events via the input layer
Date: Sat, 13 Jun 2009 13:55:38 +0100 [thread overview]
Message-ID: <507032D758%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <71cd59b00906130306w319c0fc2i376bb03323845b80@mail.gmail.com>
I demand that Corentin Chary may or may not have written...
> On Sat, Jun 13, 2009 at 11:33 AM, Alan Jenkins<alan-jenkins@tuffmail.co.uk>
> wrote:
[snip]
>> The firmware still changes the brightness immediately. It seems
>> that when g-p-m gets delayed, it responds _wrongly_. It doesn't realize
>> that the firmware already changed the brightness, so it changes the
>> brightness again.
Should it be changing the brightness at all? I ask because every laptop which
I've used will change the brightness without userspace being involved.
(Although it's possible that g-p-m might get brightness-change events from
some source other than that which is used to report the laptop's own
brightness controls...)
[snip]
> Version: 2.24.2-2ubuntu8
> Ok I can reproduce [the brightness being changed inappropriately from
> userspace].
> I want to check if we can't fix g-p-m before reverting the patch. If
> there is no way to fix it, I'll revert.
I don't see that it can ever be reliable in the face of the brightness having
already been changed without userspace involvement short of being able to
tell it to report only on some/all events from some input devices.
--
| Darren Salt | linux at youmustbejoking | nr. Ashington, | Doon
| Debian GNU/Linux | or ds ,demon,co,uk | Northumberland | Army
| + Generate power using sun, wind, water, nuclear. FORGET COAL AND OIL.
A foolish consistency is the hobgoblin of little minds.
next prev parent reply other threads:[~2009-06-13 13:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 17:57 Darren Salt
2009-04-04 4:18 ` Matthew Garrett
2009-04-04 8:33 ` Corentin Chary
2009-04-04 12:20 ` Darren Salt
2009-04-04 12:35 ` Corentin Chary
2009-04-04 22:10 ` Darren Salt
2009-04-05 8:22 ` Corentin Chary
2009-06-08 15:24 ` Alan Jenkins
2009-06-13 8:55 ` Corentin Chary
2009-06-13 9:33 ` Alan Jenkins
2009-06-13 10:06 ` Corentin Chary
2009-06-13 12:55 ` Darren Salt [this message]
2009-06-13 17:51 ` Alan Jenkins
2009-06-14 19:26 ` Corentin Chary
2009-06-15 8:09 ` Alan Jenkins
2009-06-15 8:12 ` Alan Jenkins
2009-06-16 8:33 ` [gpm] " Richard Hughes
2009-06-16 8:34 ` Alan Jenkins
2009-06-16 8:47 ` Richard Hughes
2009-06-16 9:44 ` Corentin Chary
2009-06-16 10:04 ` Richard Hughes
2009-06-18 13:33 ` Alan Jenkins
2009-06-18 22:44 ` Corentin Chary
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=507032D758%linux@youmustbejoking.demon.co.uk \
--to=linux@youmustbejoking.demon.co.uk \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=corentin.chary@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome