> > and when xkb is disabled (which i assume is what XkbDisable does), where > > does the mapping come from then? > > When XKB is disabled, the mapping comes from the OS; take a look > at programs/Xserver/hw/xfree86/common/xf86KbdLnx.c in xf86KbdGetMapping.
thank you keith. i guess i'm beginning to understand. a little bit. :-) it seems the server will only map the scancodes it already knows about, since it starts from a known list of AT keycodes. if a new scancode comes along, there's no way to get it mapped through to an X event. :-( in a different message, assuming xkb is enabled, you wrote: > > > so, reading between the lines, i guess the mapping i'm looking for > > > from hardware scancodes to X11 keycodes, in the XFree86 server, is > > > hard-coded in a platform-specific driver somewhere? > > > > The mapping is all contained in keyboard specific files found in > > /usr/X11R6/lib/X11/xkb. The organization of those files is probably > > only obvious to the original XKB authors. but again, since there are no scancode values in any of those files, i think there must be a hard-coded set of assumptions in this path as well. as an editorial comment, this is all much harder and obtuse than i expected it to be. paul =--------------------- paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 36.3 degrees) _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
