linux-kernel - Changing the number of keys supported by the input subsystem

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>] [day] [month] [year] [list]

Message-ID: <20071024220414.GC10219@hardeman.nu>
Date:	Thu, 25 Oct 2007 00:04:14 +0200
From:	David Härdeman <david@...deman.nu>
To:	linux-kernel@...r.kernel.org
Cc:	dmitry.torokhov@...il.com
Subject: Changing the number of keys supported by the input subsystem

Currently the IR input handling of drivers/media/dvb/ttpci/budget-ci.c 
requires a rc5_device module option which specifies the rc5 device code 
to listen to (or as an alternative, all devices). This means, among 
other things, that multiple remotes can't be used with different 
keymaps.

My idea was to drop the module parameter and allow all rc5 device and 
command combinations to be mapped using one keyboard map.

rc5 device codes are 5 bits, command codes are 6 bits, giving a total of 
2048 possible keycodes.

However, the input subsystem is currently limited to 512 entries. So my 
question is whether it would be possible to extend that and/or make the 
size of the keymap (the keybit member of struct input_dev) dynamic?

-- 
David Härdeman
-
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/