From: Bastien Nocera <hadess@hadess.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: Logitech MX5000 extra keys
Date: Tue, 10 Feb 2009 10:54:29 +0000 [thread overview]
Message-ID: <1234263269.5677.939.camel@cookie.hadess.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0902101113360.11630@jikos.suse.cz>
On Tue, 2009-02-10 at 11:31 +0100, Jiri Kosina wrote:
> On Mon, 9 Feb 2009, Bastien Nocera wrote:
>
> > Problem is that it's not just a mapping problem, as the keys don't get
> > out of the kernel at all. The code in hid-lg.c looks more like what's
> > required. Not sure whether the magic is the same to enable the extra
> > keys on this keyboard.
>
> It's possible (and, in fact, quite probable), that quirk similar (or even
> the very same) to what is implemented in lg_report_fixup() would be
> neeeded.
>
> You can verify by adding the VID/PID of your device to struct
> hid_device_id lg_devices[] with LG_RDESC flag.
I did, but without success (I didn't see the line "fixing up Logitech
keyboard report descriptor" in the kernel logs). In user-space, the
device needs to be poked to get the device to do something when the
extra keys are pressed. I guess something similar is needed here.
I'll leave work on this for a while until I get more time to experiment.
Cheers
next prev parent reply other threads:[~2009-02-10 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 19:24 Logitech MX5000 extra keys Bastien Nocera
2009-02-07 1:12 ` Jiri Kosina
2009-02-09 11:31 ` Bastien Nocera
2009-02-10 10:31 ` Jiri Kosina
2009-02-10 10:54 ` Bastien Nocera [this message]
2009-02-10 17:13 ` 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=1234263269.5677.939.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=jkosina@suse.cz \
--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).