From: Pavel Machek <pavel@suse.cz>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dmitry.torokhov@gmail.com, linux-input@vg
Subject: Re: Re (hello?): [PATCH] Let keyboard notifiers modify key codes
Date: Thu, 15 Jan 2009 08:40:44 +0100 [thread overview]
Message-ID: <20090115074044.GA1599@ucw.cz> (raw)
In-Reply-To: <20090109214357.GH5073@const.famille.thibault.fr>
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@ens-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
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@suse.cz>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: Re: Re (hello?): [PATCH] Let keyboard notifiers modify key codes
Date: Thu, 15 Jan 2009 08:40:44 +0100 [thread overview]
Message-ID: <20090115074044.GA1599@ucw.cz> (raw)
In-Reply-To: <20090109214357.GH5073@const.famille.thibault.fr>
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@ens-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
--
(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:[~2009-01-16 19:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 0:58 [PATCH] Let keyboard notifiers modify key codes Samuel Thibault
2009-01-09 21:23 ` Re (hello?): " Samuel Thibault
2009-01-09 21:23 ` Samuel Thibault
2009-01-09 21:35 ` Alan Cox
2009-01-09 21:43 ` Samuel Thibault
2009-01-09 21:43 ` Samuel Thibault
2009-01-09 22:01 ` Alan Cox
2009-01-09 22:23 ` Samuel Thibault
2009-01-09 22:23 ` Samuel Thibault
2009-01-12 22:36 ` Derek Fawcus
2009-01-12 22:36 ` Derek Fawcus
2009-01-12 22:51 ` Samuel Thibault
2009-01-12 22:51 ` Samuel Thibault
2009-01-13 1:06 ` Derek Fawcus
2009-01-13 1:06 ` Derek Fawcus
2009-01-13 1:45 ` Samuel Thibault
2009-01-13 1:45 ` Samuel Thibault
2009-01-15 7:40 ` Pavel Machek [this message]
2009-01-15 7:40 ` Pavel Machek
2009-01-16 19:36 ` Samuel Thibault
2009-01-16 19:36 ` Samuel Thibault
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=20090115074044.GA1599@ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vg \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.