This patch enables ppc users with ADB keyboards to use caps lock as control key. Behaviour is off by default, so it should be non-breaking for everyone else. Reproducible: Always Steps to Reproduce: 1. Remap caps lock to control (eg using xmodmap, xorg.conf options, ...) Actual Results: As the current code in adbhid.c seems to generate keypress/keyrelease events immediately even if caps lock is still pressed, remapping results in a non-functional caps lock key Expected Results: caps lock should be able to act as control ;) Additional information is available at Andrew McNabb's post to LKML
Forgot to add: this patch applies cleanly to gentoo-sources-2.6.23-r2
Get this accepted upstream please... http://dev.gentoo.org/~dsd/genpatches/faq.htm
Created attachment 136547 [details, diff] proposed patch to drivers/macintosh/adbhid.c
apparently nobody cares upstream, since Andrew McNabb posted this back in July. i'm just sick of patching the kernel manually, and to me it seems this shouldn't create problems as it's off by default. so why don't include it into the gentoo patchset?
Can you please test vanilla-sources-2.6.24_rc8. This commit might be relevant: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9f31c05ea0f5690d002ae30710fc0fbe0f0c201f
that patch seems to suggest that the patch posted on this bug (that adds restore_capslock_events) has also been merged, so this should just be a case of adding both upstream patches to our kernel
(In reply to comment #6) > that patch seems to suggest that the patch posted on this bug (that adds > restore_capslock_events) has also been merged, so this should just be a case of > adding both upstream patches to our kernel Agreed. And here's a link to the first patch to make our lives easier once we get confirmation that the problem is solved in 2.6.24_rc8
Once more with link. Sorry for the bugspam: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=9a402b649d9c4f5ac17c1368702c9f51219c484b
Please test with gentoo-sources-2.6.24 and report the results back here. Thanks.
This should be fixed in 2.6.24, please reopen if not. Given that it's a low priority feature and we're actively working on 2.6.24, I don't plan to backport it to 2.6.23.
