From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, mgarski@post.pl,
linux-input@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
Richard Purdie <rpurdie@rpsys.net>
Subject: Re: [PATCH] Route kbd leds through the generic leds layer (3rd version)
Date: Sat, 6 Mar 2010 13:30:58 +0100 [thread overview]
Message-ID: <20100306123058.GE5203@const.famille.thibault.fr> (raw)
In-Reply-To: <20100306065457.GE28759@elf.ucw.cz>
Pavel Machek, le Sat 06 Mar 2010 07:54:57 +0100, a écrit :
> > That being said, usermode tools which want to set up the modifiers and
> > connect the input LEDs to them need an easy and proper way to do so.
> > Having central input::numlock and such still seems a good thing.
>
> This is something where I'm not too sure. Opening few files in
> sequence is not that hard to the userland so "group of leds"
> abstraction does not make too much sense...
But then userland has to monitor keyboard hotplug. At the moment,
neither kbd nor console-setup use a daemon to handle keyboards, and I
doubt their authors will be happy to have to.
Samuel
next prev parent reply other threads:[~2010-03-06 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 1:20 [PATCH] Route kbd leds through the generic leds layer Samuel Thibault
2010-02-25 1:38 ` [PATCH] Route kbd leds through the generic leds layer (3rd version) Samuel Thibault
2010-02-25 10:20 ` Dmitry Torokhov
2010-02-25 12:23 ` Richard Purdie
2010-02-25 21:47 ` Samuel Thibault
2010-02-25 21:44 ` Samuel Thibault
2010-02-26 3:54 ` Dmitry Torokhov
2010-02-26 10:35 ` Samuel Thibault
2010-03-06 6:54 ` Pavel Machek
2010-03-06 12:30 ` Samuel Thibault [this message]
2010-03-07 8:25 ` Pavel Machek
2010-03-07 12:06 ` Samuel Thibault
2010-03-06 6:52 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100306123058.GE5203@const.famille.thibault.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarski@post.pl \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®