Date: Sun, 11 Jan 2004 17:30:50 +0100
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
Message-ID: <20040111163050.GA28671@zombie.inka.de>
References: <3FF6EFE0.9030109@develer.com> <3FFB6A5D.9030606@olaussons.net> <3FFB6E9E.6040500@develer.com> <20040107085104.GA14771@ucw.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20040107085104.GA14771@ucw.cz>
User-Agent: Mutt/1.5.5.1+cvs20040105i
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1188
Lines: 28

#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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/