lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 14 Apr 2010 12:19:30 -0600
From:	"Rick L. Vinyard, Jr." <rvinyard@...nmsu.edu>
To:	liux-input@...r.kernel.org,
	"Dmitry Torokhov" <dmitry.torokhov@...il.com>,
	"Jiri Kosina" <jkosina@...e.cz>,
	"Linux" <linux-kernel@...r.kernel.org>,
	"Linux USB" <linux-usb@...r.kernel.org>
Subject: Handling macros with input devices

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

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ