On 11-01-26 10:05 AM, Mark Lord wrote: > On 11-01-25 09:00 PM, Dmitry Torokhov wrote: .. >> I wonder if the patch below is all that is needed... > > Nope. Does not work here: > > $ lsinput > protocol version mismatch (expected 65536, got 65537) > Heh.. I just noticed something *new* in the bootlogs on my system: kernel: Registered IR keymap rc-rc5-tv udevd-event[6438]: run_program: '/usr/bin/ir-keytable' abnormal exit kernel: input: i2c IR (Hauppauge) as /devices/virtual/rc/rc0/input7 kernel: ir-keytable[6439]: segfault at 8 ip 00000000004012d2 sp 00007fff6d43ca60 error 4 in ir-keytable[400000+7000] kernel: rc0: i2c IR (Hauppauge) as /devices/virtual/rc/rc0 kernel: ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-0/0-0018/ir0 [ivtv i2c driver #0] That's udev invoking ir-keyboard when the ir-kbd-i2c kernel module is loaded, and that is also ir-keyboard (userspace) segfaulting when run. That behaviour is new, with the proposed "fix" patch from this thread. So the "fix" itself appears to also break userspace. The ir-keyboard program reports: IR keytable control version 0.8.2 Cheers -- 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
