linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Vier <tom@triadsys.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Samuel Thibault <sthibault@debian.org>,
	594089@bugs.debian.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Bug#594089: keyboard-configuration: caps lock keycode problem
Date: Mon, 25 Oct 2010 09:37:26 -0400	[thread overview]
Message-ID: <4CC58816.3090301@triadsys.com> (raw)
In-Reply-To: <20101025045003.GA1438@core.coreip.homeip.net>

On 10/25/2010 12:50 AM, Dmitry Torokhov wrote:
> On Sun, Oct 24, 2010 at 04:41:51PM +0200, Samuel Thibault wrote:
>> The short story is: Tom's keyboard sends all that when he presses caps
>> lock:
>>
>> press: 0x3a 0xe0 0x66
>> repeat: 0x3a
>> release: 0xba 0xe0 0xe6
>>
>> 0xe0 0x66 happens to be the "favorites" key on his keyboard with
>> internet navigation keys.  I thus believe there's a bug in his keyboard
>> that needs to be filtered at the kernel level.
>>
>> The long story can be read on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594089
>
> Hmm, the question is whether the real "favorites" key send the same
> usage and the fake one after caps lock. Any chance Tom could locate
> evtest utility and see what MSC_SCAN events being emitted?
>
> Thanks.

Sure. Here's caps-lock:

Event: time 1288013671.633008, -------------- Report Sync ------------
Event: time 1288013674.171812, type 4 (Misc), code 4 (ScanCode), value 70039
Event: time 1288013674.171853, type 1 (Key), code 58 (CapsLock), value 1
Event: time 1288013674.171862, -------------- Report Sync ------------
Event: time 1288013674.172210, type 17 (LED), code 1 (CapsLock), value 1
Event: time 1288013674.299553, type 4 (Misc), code 4 (ScanCode), value 70039
Event: time 1288013674.299580, type 1 (Key), code 58 (CapsLock), value 0
Event: time 1288013674.299593, -------------- Report Sync ------------


Right-shift (the other problem key):

Event: time 1288013798.388025, -------------- Report Sync ------------
Event: time 1288013800.742088, type 4 (Misc), code 4 (ScanCode), value 700e5
Event: time 1288013800.742130, type 1 (Key), code 54 (RightShift), value 1
Event: time 1288013800.742142, -------------- Report Sync ------------
Event: time 1288013800.861777, type 4 (Misc), code 4 (ScanCode), value 700e5
Event: time 1288013800.861812, type 1 (Key), code 54 (RightShift), value 0
Event: time 1288013800.861824, -------------- Report Sync ------------

--
Tom Vier <tom@triadsys.com>
Senior Net/Sys Admin
Triad Systems Engineering, Inc.

  reply	other threads:[~2010-10-25 13:46 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       ` Bug#594089: keyboard-configuration: caps lock keycode problem Samuel Thibault
2010-10-25  4:50         ` Dmitry Torokhov
2010-10-25 13:37           ` Tom Vier [this message]
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
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=4CC58816.3090301@triadsys.com \
    --to=tom@triadsys.com \
    --cc=594089@bugs.debian.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sthibault@debian.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;
as well as URLs for NNTP newsgroup(s).