From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Michael S. Tsirkin" <mst@dev.mellanox.co.il>
Cc: Hugh Dickins <hugh@veritas.com>, Len Brown <len.brown@intel.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net,
Richard Hughes <hughsient@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: THINKPAD_ACPI_INPUT_ENABLED seems regressive
Date: Wed, 1 Aug 2007 13:24:42 -0300 [thread overview]
Message-ID: <20070801162442.GO23111@khazad-dum.debian.net> (raw)
In-Reply-To: <20070801160805.GB11758@mellanox.co.il>
On Wed, 01 Aug 2007, Michael S. Tsirkin wrote:
> Forcing the selection at compile-time isn't such a great idea IMHO.
> Isn't there a way to support both old and new userspace?
It only afects the *defaults* of various driver knobs that can be freely
modified at runtime:
without THINKPAD_ACPI_INPUT_ENABLED:
hotkey_enable = 0
hotkey_mask unchanged from whatever is already set
hot keys from ibm-acpi 0.14 are mapped to KEY_UNKNOWN, and thus will
generate ACPI events if hotkey_enabled is set to 1.
with THINKPAD_ACPI_INPUT_ENABLED:
hotkey_enable = 1
hotkey_mask = hotkey_recommended_mask
most hot keys are mapped to something other than KEY_UNKNOWN, and
thus will not generate ACPI events but rather input layer events.
You should select whichever works better with your userspace.
--
"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:[~2007-08-01 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 13:07 Hugh Dickins
2007-08-01 15:36 ` Henrique de Moraes Holschuh
2007-08-01 16:08 ` Michael S. Tsirkin
2007-08-01 16:24 ` Henrique de Moraes Holschuh [this message]
2007-08-01 17:03 ` Hugh Dickins
2007-08-01 18:01 ` [ibm-acpi-devel] " Henrique de Moraes Holschuh
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=20070801162442.GO23111@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=hugh@veritas.com \
--cc=hughsient@gmail.com \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mjg59@srcf.ucam.org \
--cc=mst@dev.mellanox.co.il \
/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
all inboxes | Powered by JetHome®