From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@linux.intel.com>,
linux-input@vger.kernel.org, jkosina@suse.cz
Cc: George Spelvin <linux@horizon.com>,
chris@the-brannons.com, gregkh@linuxfoundation.org,
jslaby@suse.cz, linux-kernel@vger.kernel.org,
samuel.thibault@ens-lyon.org
Subject: Re: Caps lock XOR on multiple keyboards?
Date: Sun, 24 Mar 2013 11:41:53 +0100 [thread overview]
Message-ID: <20130324104153.GA4586@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130324103018.GA4156@amd.pavel.ucw.cz>
On Sun 2013-03-24 11:30:18, Pavel Machek wrote:
> Hi!
> On Mon 2012-12-03 23:58:48, Alan Cox wrote:
> > On 3 Dec 2012 16:19:11 -0500
> > "George Spelvin" <linux@horizon.com> wrote:
> >
> > > (Not sure who owns this; Cc: to the last few people to touch
> > > drivers/tty/vt/keyboard.c.)
> >
> > linux-input is probably the best place to discuss this
>
> Added few more ccs. Yes, I see that too, in kernels such as debian
> 2.6.32. It may be even older than that, but I was not using docking
> heavily in the old days.
>
> Symptoms for me are that pretty often capslock LED will start show
> opposite of true capslock state. I normally use X these days.
Ok... so it is:
Each capslock key only controls the local LED, but affects global
state.
So I turn on capslock on PS/2 keyboard its led is on. But I type on
USB keyboard, its capslock led is off, but I type in all caps. Oops.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2013-03-24 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:19 George Spelvin
2012-12-03 23:58 ` Alan Cox
2013-03-24 10:30 ` Pavel Machek
2013-03-24 10:41 ` Pavel Machek [this message]
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=20130324104153.GA4586@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=alan@linux.intel.com \
--cc=chris@the-brannons.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=samuel.thibault@ens-lyon.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®