From: Bastien Nocera <hadess@hadess.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>,
linux-input@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Input event for blocking touchpad
Date: Sun, 28 Nov 2010 14:38:44 +0000 [thread overview]
Message-ID: <1290955125.819.4.camel@novo.hadess.net> (raw)
In-Reply-To: <20101128080743.GE14499@core.coreip.homeip.net>
On Sun, 2010-11-28 at 00:07 -0800, Dmitry Torokhov wrote:
> On Fri, Nov 26, 2010 at 07:10:57PM -0200, Thadeu Lima de Souza Cascardo wrote:
> > Hello,
> >
> > I have a notebook with an ACPI system that notifies about the pressing
> > of the key for blocking touchpad. However, it does not notify it by
> > itself. I was considering sending the event to userspace and let it does
> > the blocking.
> >
> > Since other keys are also notified by this same ACPI object, it's even
> > more natural that I use an input device to send this to userspace.
> >
> > The problem is: there seems to be no event to represent this. Any
> > suggestions?
> >
>
> I have the patch below from Bastien that I will be queueing shortly.
Note that KEY_TOUCHPAD_{ON,OFF} are for when:
1) Your touchpad disables in hardware
2) You can know for certain the status of the device
You'll need to use KEY_TOUCHPAD_TOGGLE in your patch (and make changes
to udev's keyboard remap scripts to map KEY_TOUCHPAD_TOGGLE to F21 until
X can get access to those keycodes.
Cheers
next prev parent reply other threads:[~2010-11-28 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 21:10 Input event for blocking touchpad Thadeu Lima de Souza Cascardo
2010-11-28 8:07 ` Dmitry Torokhov
2010-11-28 14:38 ` Bastien Nocera [this message]
2010-11-30 1:34 ` Zhang Rui
2010-11-30 1:56 ` Thadeu Lima de Souza Cascardo
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=1290955125.819.4.camel@novo.hadess.net \
--to=hadess@hadess.net \
--cc=cascardo@holoscopio.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@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).