Re: [PATCHv2] Route kbd LEDs through the generic LEDs layer

[Andrew Morton]

On Wed, 4 Sep 2013 19:26:21 +0200 Samuel Thibault <samuel.thibault@xxxxxxxxxxxx> wrote:

> 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.
> 
> This also permits to fix #7063 from userland by using a modifier to implement
> proper CapsLock behavior and have the keyboard caps lock led show that modifier
> state.

I had a version of this in -mm for a long time and there was a
1000-message email discussion which I didn't have a hope of following.

Do you believe that the earlier controversies are now addressed and if
so, how?  Have the earlier participants in that discussion been cc'ed
and have they commented?

In other words, how are we generally getting along with those things?  

I'll put this version into -mm to get it a bit of linux-next exposure,
but I'm hoping that Dmitry will process it?

The one-line change to drivers/tty/vt/keyboard.c no longer applies -
LED_SHOW_MEM has vanished altogether.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/