On Tue, 20 Jan 2009 14:50:26 -0500 "Devin Heitmueller" <devin.heitmueller@xxxxxxxxx> wrote: > On Tue, Jan 20, 2009 at 2:43 PM, matthieu castet > <castet.matthieu@xxxxxxx> wrote: > > Hi, > > > > Mauro Carvalho Chehab wrote: > >> > >> On Mon, 19 Jan 2009 21:35:52 +0100 > >> matthieu castet <castet.matthieu@xxxxxxx> wrote: > >> > >> > >> Matthieu, > >> > >> You can replace the ir-kbd-i2c keys using the standard input ioctls for > >> it. > >> Take a look at v4l2-apps/util/keycode app. It allows you to read and > >> replace > >> any IR keycodes on the driver that properly implements the event support > >> (including ir-kbd-i2c). > > > > great I wasn't aware of this. > > But this doesn't seem very friendly : all remote keycodes are in kernel. > > If you want to change the remote, you have to do/provide the keycode for > > your remote even if it is already in kernel. > > > > Matthieu > > Matthieu, > > Your assessment of the current situation is correct. Yes, it's a > pretty annoying situation. It does have the upside that we > automatically provide the right keycodes for whatever remote comes by > default with a particular product, but obviously it is a mess if you > want to use some different remote and if your remote wasn't supported, > adding support requires a kernel recompile. No. Replacing the keycodes is as easy as adding something like this on your rc.local, or adding an equivalent udev rule: ./v4l2-apps/util/keycode /dev/input/event3 ./v4l2-apps/util/keycodes/avertv_303 This will replace the keys of the input device (assumed above that the event device is event3) by the keys at avertv_303 file. The in-kernel tables are just the default ones for that device. Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
