From: Jerone Young <jerone.young@canonical.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Fix Keymapping for upcoming Dell Laptops
Date: Thu, 25 Mar 2010 13:28:40 +0000 [thread overview]
Message-ID: <1269523720.2535.55.camel@laptop> (raw)
In-Reply-To: <1269478288.2969.1214.camel@laptop>
I left them out on purpose in the resubmit. It turned out that the way
these work (currently) under Windows is that the key press does two
things.
- it turns off the touchpad through the bios
- it sends the keypress scan code to the OS
Under Windows the driver/daemon catches the keypress but it's only so it
can show a nice on screen display. Doesn't try to cut it off or on via
the OS.
Currently (working to fix with Dell), If these are mapped under Linux
what happens is. The hardware first cutoff the touchpad, but then what
happens is the software will then toggle this setting. So you end up in
one of two states:
- never being able to turn off the touchpad
- never being able to turn on the touchpad
Will submit another patch with these once can get this sorted out.
Thanks,
Jerone
On Thu, 2010-03-25 at 08:34 +0100, Martin Pitt wrote:
> Hello Jerone,
>
> Jerone Young [2010-03-24 20:00 -0500]:
> > I need to resubmit this patch as I put "touchpadtoggle" instead of f22.
> > [...]
> > > +0xD8 touchpadtoggle #toggle touchpad OFF
> > > +0xD9 touchpadtoggle #toogle touchpad ON
>
> Hm, your resubmitted patch does not contain those two at all any more.
> Is the kernel default already correct for those two on newer Dells
> then? Or were they just forgotten?
>
> Thanks,
>
> Martin
next prev parent reply other threads:[~2010-03-25 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 0:51 [PATCH] Fix Keymapping for upcoming Dell Laptops Jerone Young
2010-03-25 1:00 ` Jerone Young
2010-03-25 7:34 ` Martin Pitt
2010-03-25 13:28 ` Jerone Young [this message]
2010-03-28 12:25 ` Martin Pitt
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=1269523720.2535.55.camel@laptop \
--to=jerone.young@canonical.com \
--cc=linux-hotplug@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).