From: Samuel Thibault <sthibault@debian.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Tom Vier <tom@triadsys.com>,
"594089@bugs.debian.org" <594089@bugs.debian.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: Bug#594089: keyboard-configuration: caps lock keycode problem
Date: Wed, 27 Oct 2010 17:22:42 +0200 [thread overview]
Message-ID: <20101027152242.GO4725@const.famille.thibault.fr> (raw)
In-Reply-To: <99F91536-4413-430C-9932-7CEF6AB656DB@gmail.com>
Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit :
> On Oct 27, 2010, at 5:05 AM, Samuel Thibault <sthibault@debian.org> wrote:
>
>
> Dmitry Torokhov, le Wed 27 Oct 2010 02:10:29 -0700, a écrit :
>
> Also, based on evtest data I only see presses/releases for one key
> (Caps Lock, Right Shift, etc.) I do not see the presses for the additional
> keys in the evtest stream so I am baffled as to where the additional
> scancode is coming from... Do you have some funky keymap loaded?
> Anything interesting in dumpkeys?
>
>
> Err, since the duplicates appear in scancodes already, is the content of
> dumpkeys really involved?
>
> Evtest data does not show any additional events, so the additional scancodes
> must be coming from the legacy keyboard driver.
Sure, but dumpkeys shows the table from scancodes to keycodes, not from
input events to scancodes.
Samuel
next prev parent reply other threads:[~2010-10-27 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100823154353.2805.13525.reportbug@tom.tse>
[not found] ` <20100903235540.GA9149@const>
[not found] ` <4C866913.3030201@triadsys.com>
[not found] ` <4C8E6861.1070502@triadsys.com>
2010-10-24 14:41 ` Samuel Thibault
2010-10-25 4:50 ` Dmitry Torokhov
2010-10-25 13:37 ` Tom Vier
2010-10-25 18:03 ` Samuel Thibault
2010-10-25 18:25 ` Dmitry Torokhov
2010-10-26 14:50 ` Tom Vier
2010-10-26 14:46 ` Tom Vier
2010-10-26 16:18 ` Dmitry Torokhov
2010-10-26 21:04 ` Tom Vier
2010-10-27 9:10 ` Dmitry Torokhov
2010-10-27 12:05 ` Samuel Thibault
[not found] ` <99F91536-4413-430C-9932-7CEF6AB656DB@gmail.com>
2010-10-27 15:22 ` Samuel Thibault [this message]
2010-10-27 16:08 ` Dmitry Torokhov
2010-10-27 18:34 ` Tom Vier
2010-10-27 19:25 ` Dmitry Torokhov
2010-10-27 20:20 ` H Hartley Sweeten
2010-10-27 20:25 ` Dmitry Torokhov
2010-10-29 8:55 ` Jiri Kosina
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=20101027152242.GO4725@const.famille.thibault.fr \
--to=sthibault@debian.org \
--cc=594089@bugs.debian.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@triadsys.com \
/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®