The PC only has so many possible keycodes (with E0 and E1 it's still
in the sub-300 range.) It won't fit within 128, but I would really
like an algorithmic mapping from scancodes to keycodes so we don't
continue to have this problem.
For example, using a 16-bit keycode model:
Scancode Keycode (binary)
mxxxxxxx m0000000 0xxxxxxx
E0 mxxxxxxx m0000000 1xxxxxxx
E1 mxxxxxxx yyyyyyyy mxxxxxxx yyyyyyyy
m = make/break bit
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - 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/