From: Kevin Milburn <kevin@kmilburn.me.uk>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: support for Logitech Wave
Date: Wed, 30 Apr 2008 18:30:07 +0100 [thread overview]
Message-ID: <200804301830.07161.kevin@kmilburn.me.uk> (raw)
In-Reply-To: <200804301141.08619.linux-user@kmilburn.me.uk>
On Wednesday 30 April 2008 11:41:08 Kevin Milburn wrote:
> Looks like I need to have some fun with getting xkbd and evdev in X working
> properly.....
>
OK, I've had some success with this, but it's left me with a few more
questions.
I can now use all the extra keys which result in a keycode of less than 255,
which appears to be a limitation within the Xorg evdev driver.
while experimenting, I've tried using showkey and setkeycodes commands but
have encountered a few issues..
Firstly, when showkey is set to keycode mode, which sets the ioctl KDSKBMODE
to K_MEDIUMRAW, it show all the expected keycodes. setting it to show
scancodes, which sets the ioctl KDSKBMODE to K_RAW, results in the scancodes
being show for all the expected keys EXCEPT those with a keycode of 392 or
higher (I don't know where the actual break is as this keyboard has no
keycodes between 236 and 392).
Is this a known issue where these scancodes don't appear, or is it something
that needs looking into?
Secondly, the primary reason for trying the above was to obtain the scancodes
so I could alter the keycodes to work with X. Trying to alter one of the
working scancodes (e071) to a new keycode using the setkeycodes command
failed with an 'Invalid Argument'.
Further research lead me to a comment indicating that setkeycodes does not
work on USB keyboards. If this is correct (which it seems to be), is
there any other way of altering the keycodes generated by the kernel?
TIA
Kevin
next prev parent reply other threads:[~2008-04-30 18:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 23:12 support for Logitech Wave Kevin Milburn
2008-04-28 6:59 ` Jiri Kosina
[not found] ` <200804281131.06389.linux-user@kmilburn.me.uk>
2008-04-30 9:21 ` Jiri Kosina
2008-04-30 10:41 ` Kevin Milburn
2008-04-30 17:30 ` Kevin Milburn [this message]
2008-05-01 12:27 ` Kevin Milburn
2008-05-07 9:36 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2008-01-15 13:49 Timo Aaltonen
2008-01-16 16:07 ` Dmitry Torokhov
2008-01-16 21:58 ` Taneli Vähäkangas
2008-01-16 22:00 ` Jiri Kosina
2008-01-16 22:34 ` Timo Aaltonen
2008-01-16 22:40 ` Timo Aaltonen
2008-02-12 6:17 ` Timo Aaltonen
2008-02-12 11:34 ` Jiri Kosina
2008-02-12 11:42 ` Timo Aaltonen
2008-02-12 11:49 ` Jiri Kosina
2008-02-12 11:54 ` Timo Aaltonen
2008-01-16 23:15 ` Taneli Vähäkangas
2008-01-17 13:07 ` Jiri Kosina
2008-01-17 19:52 ` Taneli Vähäkangas
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=200804301830.07161.kevin@kmilburn.me.uk \
--to=kevin@kmilburn.me.uk \
--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).