From: Jerone Young <jerone.young@canonical.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Fix mute key on older Thinkpads by OSI blacklisting them
Date: Sat, 24 Apr 2010 19:08:29 -0500 [thread overview]
Message-ID: <1272154109.1839.345.camel@laptop> (raw)
In-Reply-To: <20100424211601.GA16731@srcf.ucam.org>
On Sat, 2010-04-24 at 22:16 +0100, Matthew Garrett wrote:
> 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?
Well it's a daemon and a suite. Don't know if you have ever seen a
Thinkpad with Windows? .. but has a lot of Think tools & such. Apart of
these tools is an OSD as well.
What I gather (could be wrong). It waits for some bit to change in th EC
indicating the mute has been changed. Then it alerts Windows that an the
event happens and changes things at that Level (maybe by sending a mute
key press??) .. but at the Windows userspace Level things get muted and
unmuted properly. In turn muting both speakers & headphones.
Jerone
> > 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.
As mentioned in the first email, Lenovo has stopped doing this with the
newly release Thinkpads (ex. X201 & T410). By blacklisting these they
act the same as newer Thinkpads.
>
next prev parent reply other threads:[~2010-04-25 0:08 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
2010-04-25 0:08 ` Jerone Young [this message]
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=1272154109.1839.345.camel@laptop \
--to=jerone.young@canonical.com \
--cc=linux-acpi@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