[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cb42bb0ece8066ff0c4a1b69d11e8e56.squirrel@intranet.cs.nmsu.edu>
Date: Thu, 15 Apr 2010 09:20:31 -0600
From: "Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>
To: "Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc: liux-input@...r.kernel.org, "Jiri Kosina" <jkosina@...e.cz>,
"Linux" <linux-kernel@...r.kernel.org>,
"Linux USB" <linux-usb@...r.kernel.org>
Subject: Re: Handling macros with input devices
Dmitry Torokhov wrote:
> Hi Rick,
>
> On Wed, Apr 14, 2010 at 12:19:30PM -0600, Rick L. Vinyard, Jr. wrote:
>> One of the sticking points I have with the G13 driver is that I'd like
>> it
>> to have support for macros. The reason I'd like to support macros is
>> that
>> the G13's raison d'etre is to allow the end user to customize the device
>> with their own macros.
>>
>> However, I've been looking around and I can't find any support for
>> macros
>> within the kernel.
>>
>> In particular, I have support for getkeycode and setkeycode ioctl's. I
>> was
>> thinking of supporting at least setkeycode to allow a standard way to
>> set
>> a one key macro. Supporting getkeycode and setting keybit are more
>> problematic.
>>
>> If someone has already brought this issue up I apologize, but I couldn't
>> find any discussion on the linux-input list relating to macros (at least
>> other than preprocessor macros).
>>
>> Any suggestions?
>>
>
> I consider macro handling to be userspace task. If needed, macro
> sequences can be injected back into the kernel via uinput devices to be
> consumed by regualar applications.
That clarifies alot. Thanks.
--
Rick
--
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