Re: [PATCH] Re: bad scancode for USB keyboard

[Olaf Hering]

 On Sun, Jan 11, Vojtech Pavlik wrote:

> On Sun, Jan 11, 2004 at 05:30:50PM +0100, Eduard Bloch wrote:
> 
> > #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?
> 
> Good point. And I'm suffering the consequences already. Up to the
> change, I didn't know that so many keyboards are actually using this
> key, so I supposed it'll be a rather low-impact change. I stand
> corrected now.
> 
> Linus, Andrew, please apply this fix:
> 
> ChangeSet@xxxxxx, 2004-01-11 19:41:05+01:00, vojtech@xxxxxxx
>   input: Fix emulation of PrintScreen key and 103rd Euro key for XFree86.

I tried the 2.6.1-mm2 tree and changed the 84 to 43, but that doesnt
help my USB keyboard. Showkey does still show 84.

static unsigned short x86_keycodes[256] =
...
         80, 81, 82, 83, 43, 93, 86, 87, 88, 94, 95, 85,259,375,260, 90,
...

Maybe adbhid needs a similar tweak? I could not find the place, yet.


-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÃRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/