[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B0AB60B.2030006@s5r6.in-berlin.de>
Date: Mon, 23 Nov 2009 17:19:23 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Krzysztof Halasa <khc@...waw.pl>
CC: Mauro Carvalho Chehab <mchehab@...hat.com>,
Jarod Wilson <jarod@...hat.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-kernel@...r.kernel.org,
Mario Limonciello <superm1@...ntu.com>,
linux-input@...r.kernel.org, linux-media@...r.kernel.org,
Janne Grunau <j@...nau.net>,
Christoph Bartelmus <lirc@...telmus.de>
Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was:
Re: [PATCH 1/3 v2] lirc core device driver infrastructure
Krzysztof Halasa wrote:
> Mauro Carvalho Chehab <mchehab@...hat.com> writes:
>
>> Event input has the advantage that the keystrokes will provide an unique
>> representation that is independent of the device.
>
> This can hardly work as the only means, the remotes have different keys,
> the user almost always has to provide customized key<>function mapping.
Modern input drivers in the mainline kernel have a scancode-to-keycode
translation table (or equivalent) which can be overwritten by userspace.
The mechanism to do that is the EVIOCSKEYCODE ioctl.
(This is no recommendation for lirc. I have no idea whether a
pulse/space -> scancode -> keycode translation would be practical there.)
--
Stefan Richter
-=====-==--= =-== =-===
http://arcgraph.de/sr/
--
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