On Tue, 9 Sep 2014, Fredrik Hallenberg wrote: > Hi, time for a bump on this one. > > On Sun, Aug 10, 2014 at 11:56 AM, Fredrik Hallenberg > <megahallon@xxxxxxxxx> wrote: > > Here is my attempt on a fix for bug 70181, please review it. It is > > tested on my nordic Corsair K70, if this solution is deemed acceptable > > I can ask some people with other problematic keyboards to test it. > > > > Signed-off-by: Fredrik Hallenberg <megahallon@xxxxxxxxx> > > --- > > drivers/hid/hid-input.c | 14 ++++++++++++++ > > include/linux/hid.h | 1 + > > 2 files changed, 15 insertions(+) > > > > diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c > > index 2619f7f..56429c0 100644 > > --- a/drivers/hid/hid-input.c > > +++ b/drivers/hid/hid-input.c > > @@ -1085,6 +1085,20 @@ void hidinput_hid_event(struct hid_device *hid, struct hid_field *field, struct > > return; > > } > > > > + /* > > + * Some keyboards will report both HID keys 0x31 (\ and |) and > > + * 0x32 (Non-US # and ~) which are both mapped to > > + * KEY_BACKSLASH. This will cause spurious events causing Hmm, makes me wonder if this mapping in hid_keyboard[] is even correct. The footnote in HUT 1.12 specifies very different mappings for different national keyboards. -- Jiri Kosina SUSE Labs -- 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
