From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Nathanael D. Noblet" <nathanael@gnat.ca>
Cc: joeyli <jlee@suse.com>,
jlee@novell.com, platform-driver-x86@vger.kernel.org
Subject: Re: Acer-WMI disables touchpad and other issues
Date: Thu, 13 Sep 2012 17:03:41 +0100 [thread overview]
Message-ID: <20120913160341.GA13029@srcf.ucam.org> (raw)
In-Reply-To: <5051FFFA.3010506@gnat.ca>
On Thu, Sep 13, 2012 at 09:47:06AM -0600, Nathanael D. Noblet wrote:
> Hello Joey li,
>
> On 09/13/2012 04:05 AM, joeyli wrote:
> >On the other hand,
> >I checked your dmideocde on brc#848720, the 0x82 is the RIGHT acpi code
> >to you for touchpad_toggle key, that means acer-wmi should emit
> >KEY_TOUCHPAD_TOGGLE to userland. There have another thing also listen
> >the KEY_TOUCHPAD_TOGGLE and do the change. I checked the
> >gnome-settings-daemon, it just show up OSD but didn't change touchpad
> >status.
>
> I was discussing this with Matthew Garrett in #fedora-kernel. He's
> telling me that if the hardware does the enabling/disabling that it
> should not emit _TOGGLE, but that it should emit KEY_TOUCHPAD_ON or
> KEY_TOUCHPAD_OFF instead. I'm in no place to know one way or the
> other. I've CC'd him on this so the discussion of the issue can
> continue to figure out what the source problem is.
Right - TOUCHPAD_TOGGLE is a request from the hardware that the desktop
environment change the state. In this case hitting the key is causing
the hardware to change its state directly, and therefore it should just
be sending KEY_TOUCHPAD_ON or KEY_TOUCHPAD_OFF.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-09-13 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 16:45 Acer-WMI disables touchpad and other issues Nathanael D. Noblet
2012-08-16 3:33 ` joeyli
2012-09-13 4:35 ` Nathanael D. Noblet
2012-09-13 10:05 ` joeyli
2012-09-13 15:27 ` Nathanael D. Noblet
2012-09-13 19:25 ` joeyli
2012-09-13 15:47 ` Nathanael D. Noblet
2012-09-13 16:03 ` Matthew Garrett [this message]
2012-09-13 18:49 ` joeyli
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=20120913160341.GA13029@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jlee@novell.com \
--cc=jlee@suse.com \
--cc=nathanael@gnat.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.