[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20100307120604.GE5203@const.famille.thibault.fr>
Date: Sun, 7 Mar 2010 13:06:04 +0100
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Pavel Machek <pavel@....cz>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
Alexey Dobriyan <adobriyan@...il.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
alan@...rguk.ukuu.org.uk, mgarski@...t.pl,
linux-input@...r.kernel.org, Vojtech Pavlik <vojtech@...e.cz>,
Richard Purdie <rpurdie@...ys.net>
Subject: Re: [PATCH] Route kbd leds through the generic leds layer (3rd version)
Pavel Machek, le Sun 07 Mar 2010 09:25:19 +0100, a écrit :
> But you mentioned having per-keyboard led would be quite easy, it does
> not seem to be controversial, so perhaps that's way to go, first?
Thinking more about it, what about the following:
keyboard numlock trigger -> input numlock led -> input numlock trigger -> input keyboard led
Userland applications which want to redirect leds for (a priori) all
keyboards change the trigger used by the input numlock led. Userland
applications which want to redirect leds for a particular keyboard can
change the trigger user by the particular input keyboard led.
Samuel
--
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