> thinkpad_acpi does send scancodes, but only when it's reporting KEY_UNKNOWN
Ah, that would be part of the problem. In the reported cases, the faulty keys didn't have an unknown, but a wrong key code assigned.
To be honest I'm not quite sure what you mean by the ordering issue. From what I understand, the input_event struct has both the scan and the key code, and there's one event sent with both? But even if there are two separate events for this, keymap -i just prints any incoming EV_KEY event, it doesn't discard any of them.
> thinkpad_acpi does send scancodes, but only when it's reporting KEY_UNKNOWN
Ah, that would be part of the problem. In the reported cases, the faulty keys didn't have an unknown, but a wrong key code assigned.
To be honest I'm not quite sure what you mean by the ordering issue. From what I understand, the input_event struct has both the scan and the key code, and there's one event sent with both? But even if there are two separate events for this, keymap -i just prints any incoming EV_KEY event, it doesn't discard any of them.