Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755811AbZKSNhl (ORCPT ); Thu, 19 Nov 2009 08:37:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753798AbZKSNhh (ORCPT ); Thu, 19 Nov 2009 08:37:37 -0500 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:18398 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755340AbZKSNhd (ORCPT ); Thu, 19 Nov 2009 08:37:33 -0500 X-IronPort-AV: E=Sophos;i="4.44,771,1249250400"; d="scan'208";a="37045527" Date: Thu, 19 Nov 2009 14:37:37 +0100 From: Samuel Thibault To: Alexey Dobriyan , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, hpa@zytor.com, alan@lxorguk.ukuu.org.uk, mgarski@post.pl Subject: Re: [PATCH] kbd: (#7063) make CapsLock work as expected even for non-ASCII Message-ID: <20091119133737.GE31025@const.bordeaux.inria.fr> Mail-Followup-To: Samuel Thibault , Alexey Dobriyan , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, hpa@zytor.com, alan@lxorguk.ukuu.org.uk, mgarski@post.pl References: <20091116190739.GJ4764@const.famille.thibault.fr> <20091116195313.GB4462@x200> <20091116222738.GQ4764@const.famille.thibault.fr> <20091116225429.GB4764@const.famille.thibault.fr> <20091116230523.GC24961@x200> <20091116231520.GD4764@const.famille.thibault.fr> <20091117115503.GB1657@x200> <20091117132358.GJ12736@const.bordeaux.inria.fr> <20091119131854.GA1628@x200.localdomain> <20091119132828.GA31025@const.bordeaux.inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091119132828.GA31025@const.bordeaux.inria.fr> User-Agent: Mutt/1.5.12-2006-07-14 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1411 Lines: 34 Just to make sure you really understand. Samuel Thibault, le Thu 19 Nov 2009 14:28:28 +0100, a ?crit : > Now, as I said, kbd's issue is that it doesn't have any way to express > that a unicode keysym should get capslock behavior, due to kernel > interface limitation. And that's precisely why I just showed how such limitation could be lifted: > > > More precisely, in the kbd source code, in the add_capslock function, in > > > the unicode case, instead of ignoring the '+', add 0xD800 to the unicode > > > value if it is below 0x0800. > > > > You suggest to change kernel and keymap and kbd and introduce 0xD800 hack. > > This is not going to fly. > > Sure, that's precisely what I said here: > > > > But again, that's a very limited fix and just fixing the LED interface > > > would allow to just use modifiers and permit much more powerful keymaps. 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). Samuel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/