From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bruce Hill <bruce@slackwarebox.com>
Subject: Re: [PATCH v3] thinkpad-acpi: Improve hardware volume controls
Date: Sat, 14 May 2011 15:41:51 -0300 [thread overview]
Message-ID: <20110514184151.GD7171@khazad-dum.debian.net> (raw)
In-Reply-To: <BANLkTinb2dOLsmbZ7HwK_gQTkX_+eo5jpQ@mail.gmail.com>
On Sat, 14 May 2011, Andrew Lutomirski wrote:
> I think that on Windows on everything older than X220, pressing mute
> unconditionally mutes the sound, so it's a nice way to tell the system
> "don't make noise, regardless of what current settings are."
Yay, so the thinkpads have been un-dumbeddown. I love uplifting!
> The behavior I implemented reads the default from BIOS so that we do
> the right thing (or at least the thing that Lenovo intended) on all of
Does the BIOS have a setup "control" for the user to chose MUTE behaviour?
> Later on, maybe we could convince PulseAudio to notice the mixer we
> expose and do something even nicer (like show a hardware mute OSD).
*PLEASE* do. I once talked with the ALSA guys about actually doing a
piggyback mixer control and attaching it to the HDA/AC97 mixer of the
internal soundcard, but it was not exactly easy or kosher to do that at that
level.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2011-05-14 18:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 22:18 [RFC PATCH] thinkpad-acpi: Improve hardware volume controls Andy Lutomirski
2011-05-09 23:53 ` Henrique de Moraes Holschuh
2011-05-10 0:38 ` Andrew Lutomirski
2011-05-10 1:04 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
2011-05-10 2:36 ` Andrew Lutomirski
2011-05-10 3:41 ` Andrew Lutomirski
2011-05-10 10:27 ` Henrique de Moraes Holschuh
2011-05-10 10:39 ` Andrew Lutomirski
[not found] ` <BANLkTikgKj9yBUTLiFVj4tP2LNSzbExo1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-10 10:44 ` [PATCH v2] " Andy Lutomirski
2011-05-10 10:25 ` [ibm-acpi-devel] [RFC PATCH] " Henrique de Moraes Holschuh
2011-05-12 13:48 ` Matthew Garrett
2011-05-12 14:24 ` Andrew Lutomirski
2011-05-12 14:39 ` Matthew Garrett
2011-05-12 14:50 ` Andrew Lutomirski
[not found] ` <BANLkTikX7mMu2me6+O1e-Ub=Cbzerd=J3Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-12 15:39 ` Dmitry Torokhov
2011-05-12 19:33 ` Andrew Lutomirski
2011-05-12 20:42 ` Dmitry Torokhov
2011-05-14 15:34 ` [PATCH v3] " Andy Lutomirski
2011-05-14 15:47 ` Matthew Garrett
2011-05-14 15:55 ` Andrew Lutomirski
2011-05-14 18:41 ` Henrique de Moraes Holschuh [this message]
2011-05-15 19:22 ` Andrew Lutomirski
2011-05-12 21:43 ` [RFC PATCH] " Henrique de Moraes Holschuh
2011-05-16 13:49 ` [PATCH v4] " 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=20110514184151.GD7171@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=bruce@slackwarebox.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=luto@mit.edu \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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