From: Bastien Nocera <hadess@hadess.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: Trying to remap a wrongly labelled key
Date: Wed, 04 Feb 2009 12:52:11 +0000 [thread overview]
Message-ID: <1233751931.30414.715.camel@cookie.hadess.net> (raw)
In-Reply-To: <alpine.LRH.1.10.0902021329210.22097@twin.jikos.cz>
On Mon, 2009-02-02 at 13:32 +0100, Jiri Kosina wrote:
<snip>
> Hi Bastien,
Hey Jiri,
> for HID devices, the 'scancode' is in fact the full usage as reported by
> the device (i.e. including the HID usage page), not only the usage code
> itself. I.e. in your case this should be 0xc0183.
Good catch, thanks. FYI, hal-info patch is now done:
http://thread.gmane.org/gmane.comp.freedesktop.hal/12792
Just need to move onto the next keyboard now :)
Cheers
prev parent reply other threads:[~2009-02-04 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 16:08 Trying to remap a wrongly labelled key Bastien Nocera
2009-02-02 12:32 ` Jiri Kosina
2009-02-04 12:52 ` Bastien Nocera [this message]
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=1233751931.30414.715.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).