From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jerone Young <jerone.young@canonical.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Fix mute key on older Thinkpads by OSI blacklisting them
Date: Sat, 24 Apr 2010 22:16:01 +0100 [thread overview]
Message-ID: <20100424211601.GA16731@srcf.ucam.org> (raw)
In-Reply-To: <1272142178.1839.138.camel@laptop>
On Sat, Apr 24, 2010 at 03:49:38PM -0500, Jerone Young wrote:
> The issue is the way Windows does it is through a userspace daemon. By
> making it OSI=Linux (just as with the Thinkpads currently already in
> blacklist.c ..*61 line) the machines just send the OS a key press.
And how does that userspace daemon receive the event?
> Since newer thinkpads as well as most other OEM machines take this
> model. It provides a much better user experience then what it is like
> today.
It's a model-specific quirk in generic code, so it's massively desirable
to avoid this especially since it encourages other OEMs to do the same
kind of thing.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-04-24 21:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 22:48 [PATCH] Fix mute key on older Thinkpads by OSI blacklisting them Jerone Young
2010-04-24 2:01 ` Henrique de Moraes Holschuh
2010-04-24 2:14 ` Jerone Young
2010-04-24 2:19 ` Jerone Young
2010-04-24 3:10 ` Henrique de Moraes Holschuh
2010-04-24 4:15 ` Jerone Young
2010-04-24 16:01 ` Matthew Garrett
2010-04-24 20:49 ` Jerone Young
2010-04-24 21:16 ` Matthew Garrett [this message]
2010-04-25 0:08 ` Jerone Young
2010-04-25 2:28 ` Henrique de Moraes Holschuh
2010-04-25 18:28 ` Jerone Young
2010-04-25 18:44 ` Matthew Garrett
2010-04-25 18:57 ` Jerone Young
2010-04-25 18:59 ` Matthew Garrett
2010-04-25 19:19 ` Jerone Young
2010-04-26 10:11 ` Henrique de Moraes Holschuh
2010-04-27 5:50 ` Jerone Young
2010-04-25 19:02 ` Jerone Young
2010-04-26 10:38 ` Henrique de Moraes Holschuh
2010-04-27 5:44 ` Jerone Young
2010-04-25 0:19 ` Jerone Young
2010-05-03 11:45 ` Andy Lutomirski
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=20100424211601.GA16731@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jerone.young@canonical.com \
--cc=linux-acpi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).