[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110225093332.GC14053@core.coreip.homeip.net>
Date: Fri, 25 Feb 2011 01:33:32 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Keng-Yü Lin <keng-yu.lin@...onical.com>
Cc: Martin Pitt <martin.pitt@...onical.com>,
Corentin Chary <corentin.chary@...il.com>,
Matthew Garrett <mjg@...hat.com>,
acpi4asus-user@...ts.sourceforge.net,
platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org,
tyson.chen@...onical.com
Subject: Re: [PATCH] eeepc-wmi: set the touchpad toggle key code to F21
On Fri, Feb 25, 2011 at 05:22:43PM +0800, Keng-Yü Lin wrote:
> On Fri, Feb 25, 2011 at 3:18 PM, Dmitry Torokhov
> <dmitry.torokhov@...il.com> wrote:
> > I believe that the kernel should use KEY_TOUCHPAD_TOGGLE and userspace
> > should use udev's key re-mapping facilities while X is unable to process
> > keycodes above 255 to adjust to the keycode du jour. If all kernel
> > drivers were to use KEY_TOUCHPAD_TOGGLE then remapping would be much
> > easier (the utility would simply check capabilities for
> > KEY_TOUCHPAD_TOGGLE and do the remap).
>
> Can udev re-map a key code to another?
Not directly.
>
> Am I correct that udev can only re-map a scan code to a specified key code.
Right, so once you determined via capabilities that device emits
KEY_TOUCHPAD_TOGGLE you query the keymap (using EVIOCGKEYCODE2; by
index) and replace all entries that are mapped to KEY_TOUCHPAD_TOGGLE to
whatever you want.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists