From: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
To: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
Cc: linux-input@vger.kernel.org
Subject: Re: Handling macros with input devices
Date: Wed, 14 Apr 2010 13:08:40 -0600 [thread overview]
Message-ID: <858c533f3330c7d6804eaf1162c71a03.squirrel@intranet.cs.nmsu.edu> (raw)
In-Reply-To: <054d04d6a47f4ba368c8d75f8d8fb08f.squirrel@intranet.cs.nmsu.edu>
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
parent reply other threads:[~2010-04-14 19:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <054d04d6a47f4ba368c8d75f8d8fb08f.squirrel@intranet.cs.nmsu.edu>]
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=858c533f3330c7d6804eaf1162c71a03.squirrel@intranet.cs.nmsu.edu \
--to=rvinyard@cs.nmsu.edu \
--cc=linux-input@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).