From: Eduard Bloch <edi@gmx.de>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: bad scancode for USB keyboard
Date: Sun, 11 Jan 2004 17:30:50 +0100 [thread overview]
Message-ID: <20040111163050.GA28671@zombie.inka.de> (raw)
In-Reply-To: <20040107085104.GA14771@ucw.cz>
#include <hallo.h>
* Vojtech Pavlik [Wed, Jan 07 2004, 09:51:04AM]:
> 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.
Fine, but there are a lot of USB keyboard that _work_ that way, where
the "103rd" key is really positioned as the one and the only one '# key.
And the current stable X release does NOT know about the new scancode.
You realize that you intentionaly broke compatibility within a stable
kernel release?
> 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.
*May* be a nice feature, but such things require better planning.
Regards,
Eduard (going to revert that change before compiling 2.6.1 now).
--
Am Abend manche Hülle fällt, die sonst des Leibes Fülle hält.
next prev parent reply other threads:[~2004-01-11 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 16:37 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
2004-01-09 0:31 ` Fredrik Olausson
2004-01-09 1:58 ` Bernardo Innocenti
2004-01-11 16:30 ` Eduard Bloch [this message]
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=20040111163050.GA28671@zombie.inka.de \
--to=edi@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome