From: Bernardo Innocenti <bernie@develer.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Fredrik Olausson <fredrik@olaussons.net>,
lkml <linux-kernel@vger.kernel.org>, Andries Brouwer <aeb@cwi.nl>,
devel@XFree86.org
Subject: Re: bad scancode for USB keyboard
Date: Wed, 07 Jan 2004 20:35:04 +0100 [thread overview]
Message-ID: <3FFC5F68.2090009@develer.com> (raw)
In-Reply-To: <20040107085104.GA14771@ucw.cz>
Vojtech Pavlik wrote:
> On Wed, Jan 07, 2004 at 03:27:42AM +0100, Bernardo Innocenti wrote:
>
>>>I have the same problem with a Logitech cordless desktop.
>>>I can easily change the keycode to generate the right characters when in
>>>console-mode, but XFree gives that key and the Print Screen key the same
>>>keycode.
>>>After changing the xmodmap I can get the unmodified character,
>>>but modifiers doesn't work, it just gives me the same character not
>>>matter what modifier I use (shift, alt, alt_gr etc.)
>>
>>I had fixed my console keymap too, but I've not been able to
>>figure out how to change the X keymap. I've been looking in
>>the /usr/X11R6/lib/X11/xkb/ directory, but perhaps XKB is not
>>being used for old-style keyboard mapping?
>>
>>Could you provide detailed instructions? C coding with missing
>>backslash and bar keys is quite hard :-)
>>
>>Of course, I still thing its' a 2.6 kernel bug and it should be
>>fixed. Vojtech, do you have an idea why it's happening?
>
> The reason is that this key is not the ordinary backslash-bar key, it's
> the so-called 103rd key on some european keyboards. It generates a
> different scancode.
Yes, I've found out it's 84 for the key besides/below the enter key.
> 2.4 used the same keycode for both the scancodes, 2.6 does not, so that
> it's possible to differentiate between the keys on keyboards that have
> both this one and also the standard backslash-bar.
I see... So it appears the fix has to be done in the kbd package and in
XFree86.
The default console keymap should be changed like this:
< keycode 84 = Last_Console
> keycode 84 = backslash bar
Andries Brouwer appears to be the current maintainer of kbd, so I've
pulled him into our thread. This is also being cross-postied to
the devel@XFree86.org list.
In addition, I'm going to open two PRs for these packages in RedHat's
bugzilla to make sure the issue gets properly fixed before it hits the
masses.
fyi, this thread was started here:
http://www.ussg.iu.edu/hypermail/linux/kernel/0401.0/0485.html
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2004-01-07 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 16:37 bad scancode for USB keyboard Bernardo Innocenti
[not found] ` <3FFB6A5D.9030606@olaussons.net>
2004-01-07 2:27 ` Bernardo Innocenti
2004-01-07 8:51 ` Vojtech Pavlik
2004-01-07 19:35 ` Bernardo Innocenti [this message]
2004-01-09 0:31 ` Fredrik Olausson
2004-01-09 1:58 ` Bernardo Innocenti
2004-01-11 16:30 ` Eduard Bloch
2004-01-11 18:44 ` [PATCH] " Vojtech Pavlik
2004-01-14 13:54 ` Olaf Hering
2004-01-14 13:59 ` Vojtech Pavlik
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=3FFC5F68.2090009@develer.com \
--to=bernie@develer.com \
--cc=aeb@cwi.nl \
--cc=devel@XFree86.org \
--cc=fredrik@olaussons.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.