From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Route kbd LEDs through the generic LEDs layer
Date: Fri, 12 Jul 2013 13:36:56 +0200 [thread overview]
Message-ID: <20130712113655.GA4227@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130707101028.GD5651@type.youpi.perso.aquilenet.fr>
Hi!
> This permits to reassign keyboard LEDs to something else than keyboard "leds"
> state, by adding keyboard led and modifier triggers connected to a series
> of VT input LEDs, themselves connected to VT input triggers, which
> per-input device LEDs use by default. Userland can thus easily change the LED
> behavior of (a priori) all input devices, or of particular input devices.
Nice! Leds now have proper /sys interface.
But... I boot up, switch from X to console, press capslock, and no
reaction anywhere.
Note that this is notebook with usb keyboard plugged in (and two
monitors), but I believe this worked before...
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2013-07-12 11:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201011112205.oABM5KVJ005298@imap1.linux-foundation.org>
[not found] ` <201011111440.07882.dmitry.torokhov@gmail.com>
[not found] ` <20110102090935.GV32469@atrey.karlin.mff.cuni.cz>
[not found] ` <20110102103210.GA25662@core.coreip.homeip.net>
[not found] ` <20110102225741.GX5480@const.famille.thibault.fr>
[not found] ` <20110112182702.GA9168@core.coreip.homeip.net>
[not found] ` <20111114040613.GA4992@type.famille.thibault.fr>
2012-12-21 0:34 ` [PATCH] Route kbd LEDs through the generic LEDs layer Samuel Thibault
2013-07-07 10:10 ` Samuel Thibault
2013-07-12 11:36 ` Pavel Machek [this message]
2013-07-12 12:42 ` Samuel Thibault
2013-07-12 23:33 ` Pavel Machek
2013-07-13 9:35 ` Samuel Thibault
2013-07-15 9:12 ` Pavel Machek
2013-07-15 9:27 ` Peter Korsgaard
2013-07-15 15:03 ` David Herrmann
2013-07-15 19:08 ` Samuel Thibault
2013-07-17 15:14 ` David Herrmann
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=20130712113655.GA4227@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).