Hello, Samuel Thibault, le Thu 05 Feb 2009 12:39:08 +0100, a écrit : > And about the led issue, we need to ask the kernel for an interface to > be able to configure which lock should drive which led. Dmitry Torokhov, le Mon 08 Jun 2015 14:43:07 -0700, a écrit : > If user wants all keyboards to light up CapsLock LED when VT state locks > CtrlL modifier they need to write a udev rule or similar to set up > "kbd-ctrlllock" trigger for all appearing "input%::capslock" LED class > devices. Anton, this is the interface proposed by the input maintainer, Dmitry, to change which modifiers gets to light the keyboard LEDs (the exact names may change, but the principle should be firm). I know this is inconvenient for console-setup for handling hotplugged keyboards, but Dmitry prefers to avoid introducing a virtual multiplexer as explained below: > Having such virtual multiplexing object just adds complexity and is > hard to untange (see /dev/input/mice and all the issues we had with > synaptics driver trying to exclude it's data stream from it). Samuel -- 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
