Em 09-11-2010 04:32, Dmitry Torokhov escreveu: > On Mon, Nov 08, 2010 at 12:14:48PM -0200, Mauro Carvalho Chehab wrote: >> Em 08-11-2010 11:41, jonsmirl@xxxxxxxxx escreveu: >>> On Mon, Nov 8, 2010 at 8:34 AM, jonsmirl@xxxxxxxxx <jonsmirl@xxxxxxxxx> wrote: >>>> To achieve plug and play at least one of four choices has to happen: >>> >>> There is another option, the IR maps get integrated into user space >>> keyboard mapping package. This may be possible with the new >>> libxkbcommon package. >> >> That seems interesting. >> > > I disagree here. libxkbcommon provides X interface while applications > might want to access evdev nodes directly. Let me express better: I don't think we should integrate X with the udev tool, but, eventually, we could make some X package dependent of v4l-utils. Not sure if libxkbdcommon is the better way to do it, as I don't have it installed here on my machines. > If anything, parts of > ir-utils dealing with keymap selection should be moved into udev. Maybe > we should split utilities that select protocol from the keymap setting > and use udev keymap utilities to do the task. It doesn't make sense to split keymap and protocol selection. Just loading a keyboard table but not changing the IR protocol is useless, as the device will not be selected. Besides that, the tool that do both is really simple (and, btw, it also allows changing the map for a non-RC device, by using one parameter that skips the usage of the sysfs nodes at /sys/class/rc): # ir-keytable -d /dev/input/event4 -r scancode 0x0000 = KEY_LEFTCTRL (0x1d) Enabled protocols: Cheers, Mauro -- 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
