Messages in this thread | | | Date | Sun, 19 Jul 2009 12:31:04 -0700 | From | Dmitry Torokhov <> | Subject | Re: [PATCH 1/3] ir-kbd-i2c: Allow use of ir-kdb-i2c internal get_key funcs and set ir_type |
| |
On Sun, Jul 19, 2009 at 02:26:53PM -0400, Mark Lord wrote: > (resending.. somebody trimmed linux-kernel from the CC: earlier) > > Jean Delvare wrote: >> On Sun, 19 Jul 2009 10:38:37 -0400, Mark Lord wrote: >>> I'm debugging various other b0rked things in 2.6.31 here right now, >>> so I had a closer look at the Hauppauge I/R remote issue. >>> >>> The ir_kbd_i2c driver *does* still find it after all. >>> But the difference is that the output from 'lsinput' has changed >>> and no longer says "Hauppauge". Which prevents the application from >>> finding the remote control in the same way as before. >> >> OK, thanks for the investigation. >> >>> I'll hack the application code here now to use the new output, >>> but I wonder what the the thousands of other users will do when >>> they first try 2.6.31 after release ? >> >> Where does lsinput get the string from? > .. > > Here's a test program for you: >
And I think have a fix for that, commit
f936601471d1454dacbd3b2a961fd4d883090aeb
in the for-linus branch of my tree.
-- Dmitry
| |