linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Schmitt <tcwardrobe@gmail.com>
To: linux-input@vger.kernel.org
Subject: Logitech Wave Y-RCP140 on not-original receiver
Date: Thu, 11 Apr 2013 05:11:03 +0200	[thread overview]
Message-ID: <516629C7.6080108@gmail.com> (raw)

Hi folks,

first, please bear with me if I ask some too basic questions here, as I 
did not find any comprehensive resources on the web to answer those 
"beginner questions" and / or my head started to smoke as some stuff I 
found was kind of too deep into the whole input layer stuff and got me 
rather confused on the way...

The situation:
I got a Logitech Wave keyboard (which was already discussed on this list 
back in 2008) connected to an usb receiver which does not belong to the 
keyboard originally. It has the USB-ID "046d:c505" and is shown as 
"Logitech, Inc. Cordless Mouse+Keyboard Receiver". I have several 
wireless Logitech keyboards and at least two receivers, but only one of 
them pairs successfully with the Wave-keyboard. All "normal" keys work, 
even some of the additional keys work, but some do not show a thing via 
showkey / xev / evtest. Only via usbmon I can see some action while 
pressing those dead keys.

The problem:
Mucho grande confusion and no idea where my head stands... as I've read 
the mentioned thread from back in 2008 I have the impression that the 
keyboard should at least recognize some of the additional keys, as some 
talk was going on there to include some quirks in some logitech-function 
in its hid-driver. The rest would not work because of the "higher than 
keycode 255"-issue, but even there I am not quite sure anymore.
Anyway, as only the most basic additional keys work (probably those that 
the keyboard had that shipped with the receiver originally) I *assume* 
that is because the kernel does not bother with the other keycodes the 
keyboard sends, as the original keyboard for that receiver did not have 
those keys?

The questions:
First, obvioulsy, is my assumption right? Do most additional keys not 
work because I use a not-originally-shipped-with receiver?
Second, I guess it would not make any sense adding the receiver I use 
for that keyboard to the mentioned "quirks"-section in the logitech 
hid-driver as I may be the only person on this planet using that 
combination. ;) But can I request the running kernel to see the receiver 
as the originally-shipped-with receiver? Or do I need to patch the 
source on my own? Does that even make any sense or is it a bogus idea 
and I just don't see it?
Third, if the kernel sees my receiver as the "original" one, setkeycode 
and the like will do the rest to make *all* keys work in X?
Forth, every 30 seconds without any keys pressed I see this with usbmon 
for that device (bus):

 > dd4a4680 1694370199 S Ci:4:011:0 s c0 09 0003 0000 0008 8 <
 > dd4a4680 1694373253 C Ci:4:011:0 0 8 = 043e800f 00008001

Normally not even worth asking, but as I am writing this mail, I may 
also include that question. :) Any idea what that is? Some 
ping-pong-thing to see if a device is still there?

regards and greetings
Michael
(I am subscribed, no cc needed, but I won't mind...)

                 reply	other threads:[~2013-04-11  3:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=516629C7.6080108@gmail.com \
    --to=tcwardrobe@gmail.com \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).