From: Derek Fawcus <dfawcus@cisco.com>
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: Mon, 12 Jan 2009 22:36:21 +0000 [thread overview]
Message-ID: <20090112223621.GA21489@cisco.com> (raw)
In-Reply-To: <20090109222341.GI5073@const.famille.thibault.fr>
On Fri, Jan 09, 2009 at 11:23:41PM +0100, Samuel Thibault wrote:
> Alan Cox, le Fri 09 Jan 2009 22:01:44 +0000, a écrit :
> > > > Surely that is just a new keymap ?
> > >
> > > No. That would mean a lot of keymapSSS. Doing it the keymap way
> >
> > Why - its an algorithmic question about how to edit them - remember you
> > can edit keymaps in programs at runtime and live.
>
> Right. I'm still afraid by that: we'd need to know how to remap the
> various keycodes (amiga, atari, i386, mc, sun).
Err - just use EVIOCSKEYCODE to swap the keycodes around, this works
in terms of the evdev keycodes. I use it in a small program to swap
around a bunch of keys.
A bit more of a challange would be listening to evdev, and when
detecting the 'swap' keycode, doing the reload with the actual swaps.
I'm not sure w/o reading the code if the kernel will allow this to be
shared between the tty and evdev on the same vt, but then one could
run a controller program talking through a pty and direct to the keyboard.
DF
next prev parent reply other threads:[~2009-01-12 22:54 UTC|newest]
Thread overview: 12+ 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:35 ` Alan Cox
2009-01-09 21:43 ` Samuel Thibault
2009-01-09 22:01 ` Alan Cox
2009-01-09 22:23 ` Samuel Thibault
2009-01-12 22:36 ` Derek Fawcus [this message]
2009-01-12 22:51 ` Samuel Thibault
2009-01-13 1:06 ` Derek Fawcus
2009-01-13 1:45 ` Samuel Thibault
2009-01-15 7:40 ` Pavel Machek
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=20090112223621.GA21489@cisco.com \
--to=dfawcus@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox