Problems with X..

[Matthias Muthmann]

On Mo, 2005-03-07 at 22:17 +0100, Dejan Lesjak wrote:

> I see, this should eliminate concern that previous patches remapped last line 
> to weird codes... Digging a bit through this I hope that we're at least a bit 
> closer to something. I think we could use the mapping for wsconsole for sun 
> keyboards: Looking at keycodes we should get (this is a type5 keyboard, 
> right?) in /usr/X11R6/lib/X11/xkb/keycodes/sun - for de layout of type5 
> keyboard key Y is <AB01> so the code should be 107. Now before mapping in 
> driver (for which these patches are) is converted to this code, MIN_KEYCODE 
> (defined as 8 in this case) is added to scancode, so that one should be 99. 
> As we already subtract 1 before addition of MIN_KEYCODE, scancode should be 
> 100 or 0x64, which is what we have in wsSun map in bsd_KbdMap.c.
> Anyway... if my rambling above is correct, this is what you could try: of 
> previous patches keep only patch-kbd_sparc_2.c (remove patch-bsd_kbd.c and 
> patch-bsd_KbdMap.c) and add the patch here:
> http://www.ijs.si/~lesi/xorg/patch-bsd_KbdMap.c.2
> Better? Worse? Horrible?
> 
> 
> Dejan
> 
Well, it depends on your definition of better worse an horrible, but I'd
say something between worse to horrible ;).
The keys are completely messed up (its a German type5c keyboard).
Some examples:
1: keycode 9 (keysym 0x1005ff77, SunAudioLowerVolume)
0: keycode 18 (keysym 0xffc9, F12)
a: keycode 37 (keysym 0x31, 1), XLookupString gives 1 bytes: (31) "1"
l: keycode 45 (keysym 0x39, 9), XLookupString gives 1 bytes: (39) "9"
y: keycode 51 (keysym 0xff63, Insert)
.: keycode 59 (keysym 0xff50, Home)
End: keycode 102 (keysym 0xff68, Find)

-- 
Matthias Muthmann <mmuthmann at gmx.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20050308/6a5cc05a/attachment.bin