From: Jon Smirl <jonsmirl@gmail.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: vojtech@suse.cz, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: keymaps, event interface and multiple keyboards
Date: Sun, 22 May 2005 10:43:50 -0400 [thread overview]
Message-ID: <9e47339105052207431634c341@mail.gmail.com> (raw)
I'm working on keyboard support for Xgl (the OpenGL based accelerated
Xserver). X implements it's own keymaps but since this is all new code
I can look at using the kernel ones. I haven't been a fan of having
two separate systems. Since I have little experience with keyboard
support I could use some help in getting the code right.
One goal of XGL is to allow multiuser. It does this by using
independent framebuffers and the event interface for keyboard/mouse.
This all works but it ignores the VT system.
Now I'm starting to look at the kernel keymap support. Kernel keymaps
are tied to the VT system. There is only one VT system and it is not
multiuser. So how do I get support for multiple users (maybe with
different keyboards) using kernel keymap? Should keymap support be
broken out of the VT code and moved to input?
--
Jon Smirl
jonsmirl@gmail.com
reply other threads:[~2005-05-22 14:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9e47339105052207431634c341@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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