linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: linux-input@vger.kernel.org
Subject: Logitech MX5000 extra keys
Date: Fri, 06 Feb 2009 19:24:39 +0000	[thread overview]
Message-ID: <1233948279.8950.75.camel@cookie.hadess.net> (raw)

Heya,

I own another keyboard, the Logitech MX5000[1], which is a
keyboard/mouse combo, with a USB dongle (which can switch between HID
and HCI/Bluetooth modes).

Some keys aren't reported at all through the input layer, but there is
code in the mx5000-tools[2] to make those keys work through hiddev.

See eventin():
http://svn.gna.org/viewcvs/mx5000tools/trunk/mx5000d/input_translate.c?rev=15&view=auto

There's a bit more scary code to enable the keys in the library part of
the module.

I was wondering what the best course of action would be to make this
code work out-of-the-box. Would it be better to write a HAL addon, and
do all this work in user-space, or would it be more useful to have
directly in the kernel?

Obviously, if the latter, I'd appreciate a bit of guidance on where I
should add the code.

Cheers


[1]: http://www.amazon.com/Logitech-Cordless-Desktop-Laser-967558-0403/dp/B000AY5ZIS
[2]: http://home.gna.org/mx5000tools/


             reply	other threads:[~2009-02-06 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 19:24 Bastien Nocera [this message]
2009-02-07  1:12 ` Logitech MX5000 extra keys Jiri Kosina
2009-02-09 11:31   ` Bastien Nocera
2009-02-10 10:31     ` Jiri Kosina
2009-02-10 10:54       ` Bastien Nocera
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=1233948279.8950.75.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --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).