mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: alan@linux.intel.com, chris@the-brannons.com,
	gregkh@linuxfoundation.org, jslaby@suse.cz
Cc: linux@horizon.com, linux-kernel@vger.kernel.org
Subject: Caps lock XOR on multiple keyboards?
Date: 3 Dec 2012 16:19:11 -0500	[thread overview]
Message-ID: <20121203211911.20156.qmail@science.horizon.com> (raw)

(Not sure who owns this; Cc: to the last few people to touch
drivers/tty/vt/keyboard.c.)

I happen to have both a PS/2 and USB keyboard plugged, in, but was
noticing that the caps lock key seemed inverted.  When the LED was off,
I got all caps (unless I used shift), while when it was on I got normal
lower-case letters.

This quite confused me, until I looked over and saw that someone had
hit caps lock on the PS/2.

Experimenting, it seems that each keyboard has its own caps lock LED
state, and the XOR of the two controls the case of the letters.

The corresponding shift keys have a shared logical state which depends
on who last had a transition.  Holding down left-shift on one can be
cancelled by pressing and releasing left-shift on the other.  (But
left & right shift are tracked separately.)

It would make more sense if each keyboard's caps lock LED controlled
the effect on its keys.  Either give each keyboard a completely separate
caps lock state, or toggle both LEDs when either caps lock is pressed.

Perhaps the answer is "It's too much work to fix; stop doing something
so stupid", but I thought I'd at least mention it.

(Er... it appears that my XOR description was incomplete.  I now have
the keyboard system in a state where *one* caps lock LED has to be on
to get normal lower-case letters.  I was playing with down1/down2/up1/up2
combinations, but I'm not quite sure what happened...)

             reply	other threads:[~2012-12-03 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 21:19 George Spelvin [this message]
2012-12-03 23:58 ` Alan Cox
2013-03-24 10:30   ` Pavel Machek
2013-03-24 10:41     ` Pavel Machek
2013-03-24 22:39     ` Samuel Thibault
2013-03-26 16:54       ` Peter Korsgaard

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=20121203211911.20156.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=alan@linux.intel.com \
    --cc=chris@the-brannons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®