From: Marty Plummer <netz.kernel@gmail.com>
To: linux-input@vger.kernel.org
Subject: Generic all-purpose keycodes for gaming keyboards?
Date: Fri, 13 Nov 2015 10:50:43 -0600 [thread overview]
Message-ID: <564614E3.2050805@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 788 bytes --]
Greetings,
As many of you are no doubt aware there has been a large amount of new 'gaming'
keyboards and mice entering the market from various manufacturers, each with
their own oddities and every developer that seeks to support them has in turn
came up with their own way to handle these keyboards. In particular my interest
is in setting up some standard way to handle these, especially those with macro
and/or profile buttons, such as mapping them to a set of specially purposed
keycodes (I've seen BTN_TRIGGER_HAPPY? used for this purpose, but I don't think
that was the original intent for those keycodes) just for use with these sort of
devices, eg, BTN_KEYBOARD_MACRO? and BTN_KEYBOARD_PROFILE? and so on. How doable
do you guys think such an infrastructure would be?
[-- Attachment #1.2: 0xC030918D.asc --]
[-- Type: application/pgp-keys, Size: 3168 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2015-11-13 16:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=564614E3.2050805@gmail.com \
--to=netz.kernel@gmail.com \
--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).