[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <21d7e9970710161332h7694579dp277ce774b0ce3956@mail.gmail.com>
Date: Wed, 17 Oct 2007 06:32:55 +1000
From: "Dave Airlie" <airlied@...il.com>
To: "Linus Torvalds" <torvalds@...ux-foundation.org>
Cc: "Matthew Garrett" <mjg59@...f.ucam.org>,
"Henrique de Moraes Holschuh" <hmh@....eng.br>,
"Jeremy Katz" <katzj@...hat.com>, linux-kernel@...r.kernel.org,
davej@...hat.com, "Dmitry Torokhov" <dmitry.torokhov@...il.com>
Subject: Re: [PATCH] Map volume and brightness events on thinkpads
> > But it *is* a key press!
>
> To get somewhat back on track: volume and brightness (and similar - lid
> close etc) events clearly are keypresses.
>
> However, I would also argue that a keypress that is acted on by the
> firmware automatically is *different* from a keypress that hasn't been
> acted on: one is a "key was pressed *and* hardware did something
> automatically", and the other is just a "key was pressed" event.
>
We also have cases where userspace may have told ACPI to stop the
firmware acting on the keypress which may or may not be known to the
piece of the kernel dealing with keypresses... hence just pass the key
up to userspace and let it deal with it.
Dave.
-
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/
Powered by blists - more mailing lists