> I see. Then I would say that you need to supply both - kemap > and an optional function to mangle scancode if needed. The hardware supports an keypad with up to 8x8 keys: 256 keys. So you want me to setup a keymap table with 256 entries in the driver. And then either user-space or board-support code will populate this table? I won't need that for my board, but I can see how this makes the driver more generally usable. So I can live with that. :-) What I'd do is: if the keymap table entry is empty, then call the board-specific handler function if it's defined. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
