Henrique de Moraes Holschuh wrote: > This is something you can probably help fix, by writing that keymap, > actually. It uses the standard xorg XKB layer, and you can force > evdev to use it. I already see a "/usr/share/X11/xkb/keycodes/evdev" file which describes itself as a "translation from evdev scancodes to something resembling xfree86 keycodes." From all I can see it's a mapping from seemingly-arbitrary <KEY> names to equally arbitrary numeric values between 8 and 255. If this is what I am to change, I have no idea what key names or values I ought to use. Also, there are well over 200 mappings in this file already; presumably those were not made up at random, but I have no idea where these mappings came from or what other systems will stop working correctly if I change or replace them. Am I creating and proposing a replacement for this file or a different evdev mapping file which X.org should include as an alternative? Sorry for so many questions. I'd like to help make this work if I can, but I'm not sure how. :-( ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
