[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B055F24.8030307@zytor.com>
Date: Thu, 19 Nov 2009 07:07:16 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Samuel Thibault <samuel.thibault@...-lyon.org>,
Alexey Dobriyan <adobriyan@...il.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
alan@...rguk.ukuu.org.uk, mgarski@...t.pl
Subject: Re: [PATCH] kbd: (#7063) make CapsLock work as expected even for
non-ASCII
On 11/19/2009 05:37 AM, Samuel Thibault wrote:
>
> So we agree, and so the right solution is to either completely rework
> the interface (ugh), or just add LED routing (which can be very useful,
> actually, I for instance don't care at all about the num lock state, but
> I _do_ care about the lock that lets me shift between different keyboard
> layouts).
>
Adding LED routing and using keyboard levels is so clearly The Right Thing.
We already allow the LEDs to be programmed; we should probably just
have, for each LED, the ability to program it off/on/flashing/connected
to modifier #X.
The current KDSETLED/KDGETLED interface is of course too limited for
this -- we need an interface with at least a byte per LED.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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