[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090116193603.GA5401@const.famille.thibault.fr>
Date: Fri, 16 Jan 2009 20:36:03 +0100
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Pavel Machek <pavel@...e.cz>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, dmitry.torokhov@...il.com,
linux-input@...r.kernel.org
Subject: Re: Re (hello?): [PATCH] Let keyboard notifiers modify key codes
Pavel Machek, le Thu 15 Jan 2009 08:40:44 +0100, a écrit :
> On Fri 2009-01-09 22:43:57, Samuel Thibault wrote:
> > Alan Cox, le Fri 09 Jan 2009 21:35:55 +0000, a écrit :
> > > Samuel Thibault <samuel.thibault@...-lyon.org> wrote:
> > > > Came somebody have a look at this? The need is real, the only question
> > > > that comes to my mind is whether notifiers are allowed to modify the
> > > > param they are given. Since they are not marked const, I'd guess it'd
> > > > be ok?
> > >
> > > The notifier code doesn't care.
> >
> > I know, but I'm asking about current practice.
> >
> > > > Make kbd_keycode() read param.value after calling the keyboard notification
> > > > chain, to let the callee change the translation on the fly. This for instance
> > > > permits to remap the physical positions of the keys independently of the
> > > > configured keymap, for e.g. single-handed people.
> > >
> > > Surely that is just a new keymap ?
> >
> > No. That would mean a lot of keymapSSS. Doing it the keymap way
> > would require to have us, us-revert-left, us-revert-right, en-uk,
> > uk-revert-left, uk-revert-right, etc. I really don't like that approach,
> > thus the "independently of the configured keymap".
>
> ...and that is ok if you autogenerate those keymaps, right?
> Pavel
I have already answered that, see
http://marc.info/?l=linux-kernel&m=123153985127010&w=2
Samuel
--
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