[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150609160339.GB26687@logic.fmi.uni-sofia.bg>
Date: Tue, 9 Jun 2015 19:03:39 +0300
From: Anton Zinoviev <anton@....bas.bg>
To: Samuel Thibault <samuel.thibault@...-lyon.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Pavel Machek <pavel@....cz>,
Pali Rohár <pali.rohar@...il.com>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
rpurdie@...ys.net, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
514464@...s.debian.org
Subject: Re: Bug#514464: caps lock led does not show up
On Tue, Jun 09, 2015 at 04:17:23PM +0200, Samuel Thibault wrote:
>
> 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,
Ok, the inconvenience is not a problem. The problem is I don't
understant the meaning of this. :)
Is there some documentation or a sample code I can read?
Anton Zinoviev
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists