From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>, linux-input@vger.kernel.org
Subject: Re: disable touchpad?
Date: Fri, 24 Feb 2012 14:55:35 -0800 [thread overview]
Message-ID: <1475573.qi4MNDPiM5@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <4F480EBA.7020509@canonical.com>
On Friday, February 24, 2012 02:27:06 PM Chase Douglas wrote:
> On 02/24/2012 01:31 PM, Dmitry Torokhov wrote:
> > On Friday, February 24, 2012 12:04:04 PM Randy Dunlap wrote:
> >> (b) My Toshiba Portege laptop has a touchpad on/off button. Is that
> >> supported?
> >
> > Kernel probably emits one of KEY_TOUCHPAD_* for it; whether it is
> > handled
> > in userspace I do not know.
>
> I have heard from some of our engineers who have looked into this that
> the interface for these buttons is not standardized. Sometimes the
> buttons turn off the touchpad in hardware. Sometimes they emit events
> that tell the OS to turn it off, and the OS needs to know how to handle it.
>
> On top of that, LEDs are sometimes there to tell you if the trackpad is
> on or off. These are also not standardized. Sometimes they are hooked up
> to the hardware, and when the hardware is off they go off. Sometimes
> they are just a plain old LED and the OS needs to turn it on and off.
>
> Fun...
That's because hardware designers were so delighted in beauty that
is rfkill buttons, they just had to do the same with touchpads...
--
Dmitry
prev parent reply other threads:[~2012-02-24 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 20:04 disable touchpad? Randy Dunlap
2012-02-24 21:31 ` Dmitry Torokhov
2012-02-24 22:27 ` Chase Douglas
2012-02-24 22:37 ` Seth Forshee
2012-02-25 1:49 ` Randy Dunlap
2012-02-24 22:55 ` Dmitry Torokhov [this message]
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=1475573.qi4MNDPiM5@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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