From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Tom Vier <tom@triadsys.com>,
Samuel Thibault <sthibault@debian.org>,
"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 13:25:34 -0700 [thread overview]
Message-ID: <201010271325.37935.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764819C63F4@AUSP01VMBX24.collaborationhost.net>
On Wednesday, October 27, 2010 01:20:09 pm H Hartley Sweeten wrote:
> Wednesday, October 27, 2010 12:25 PM, Dmitry Torokhov wrote:
> >> I: Bus=0003 Vendor=046d Product=c30a Version=0110
> >> N: Name="Logitech Logitech USB Keyboard"
> >> P: Phys=usb-0000:00:13.0-2/input0
> >> S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.0/input/input9
> >> U: Uniq=
> >> H: Handlers=kbd event2
> >> B: EV=120013
> >> B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
> >> B: MSC=10
> >> B: LED=1f
> >>
> >> I: Bus=0003 Vendor=046d Product=c30a Version=0110
> >> N: Name="Logitech Logitech USB Keyboard"
> >> P: Phys=usb-0000:00:13.0-2/input1
> >> S: Sysfs=/devices/pci0000:00/0000:00:13.0/usb5/5-2/5-2:1.1/input/input10
> >> U: Uniq=
> >> H: Handlers=kbd mouse2 event3
> >> B: EV=17
> >> B: KEY=fffffffffffff f8403340000 60d8fafd01d008 1f000000000000 0
> >> B: REL=103
> >> B: MSC=10
> >
> > Hmm, this keyboard registers 2 input devices... I wonder, if you press
> > CapsLock/Favories and RightShift/Previous and monitor both event devices
> > with evtest - will it report events on both devices at once?
>
> I haven't really been following this thread but I think the two input
> devices is normal if the keyboard has multi-media keys. All the "extra"
> keys show up as a separate input device.
>
> You might get the CapsLock and RightShift events on one device and the
> Favorites and Previous events on the other.
It is normal on sane devices however in this case there are "ghost"
key presses coming from an unknown source.
--
Dmitry
next prev parent reply other threads:[~2010-10-27 20:25 UTC|newest]
Thread overview: 19+ 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
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
2010-10-27 15:06 ` Dmitry Torokhov
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 [this message]
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=201010271325.37935.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=594089@bugs.debian.org \
--cc=hartleys@visionengravers.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sthibault@debian.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;
as well as URLs for NNTP newsgroup(s).