From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
David Herrmann <dh.herrmann@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@linux.intel.com>
Subject: VT Improvements
Date: Mon, 23 Dec 2013 17:02:15 +0400 [thread overview]
Message-ID: <52B83457.8080907@gmail.com> (raw)
Greetings!
I would like to know about the VT plans. Historically, keymap
implementations are similar in the kernel and kbd project. I rewrote
it in kbd. So, it can handle keycodes bigger than 255. In a kernel
everything remained as before. I want to fix this part in a kernel. As
pluses will be:
* opportunity to define keycode > 255.
* opportunity to reduce this table a kernel in most cases.
I would like to ask your opinion about my plans because I heard about
the thought of moving this functionality to user space.
Whether it is worth starting so large-scale changes?
--
Rgrds, legion
next reply other threads:[~2013-12-23 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 13:02 Alexey Gladkov [this message]
2013-12-23 19:15 ` VT Improvements H. Peter Anvin
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=52B83457.8080907@gmail.com \
--to=gladkov.alexey@gmail.com \
--cc=alan@linux.intel.com \
--cc=dh.herrmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.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.