From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756389Ab0DNSTg (ORCPT ); Wed, 14 Apr 2010 14:19:36 -0400 Received: from mail.cs.nmsu.edu ([128.123.64.3]:40139 "EHLO mail.cs.nmsu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756254Ab0DNSTf (ORCPT ); Wed, 14 Apr 2010 14:19:35 -0400 Message-ID: <054d04d6a47f4ba368c8d75f8d8fb08f.squirrel@intranet.cs.nmsu.edu> Date: Wed, 14 Apr 2010 12:19:30 -0600 Subject: Handling macros with input devices From: "Rick L. Vinyard, Jr." To: liux-input@vger.kernel.org, "Dmitry Torokhov" , "Jiri Kosina" , "Linux" , "Linux USB" User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? -- Rick