From: Marcel Holtmann <marcel@holtmann.org>
To: Mario Lang <mlang@delysid.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: User-space Keyboard input?
Date: Fri, 23 Jul 2004 12:54:12 +0200 [thread overview]
Message-ID: <1090580051.4791.24.camel@pegasus> (raw)
In-Reply-To: <87y8lb80yj.fsf@lexx.delysid.org>
Hi Mario,
> I'm working on BRLTTY[1], a user-space daemon which handles braille displays
> on UNIX platforms. One of our display drivers recently gained the ability
> to receive (set 2) scancodes from a keyboard connected directly to the display.
> This is a very cool feature, since the display in question has
> a bluetooth interface, making it effectively into a complete wireless
> terminal (input and output through the same connection).
tell me more about this Bluetooth device.
> However, this creates some problems. First of all, we now have to deal
> with keyboard layouts. Additionally, since we currently insert via
> TIOCSTI I think this might get problematic as soon as one switches
> to an X Windows console and modifiers come into play.
>
> Does anyone know (and can point me into the right direction) if
> Linux has some mechanism to allow for user-space keyboard data to
> be processed by the kernel as if it were received from the system
> keyboard? I.e., keyboard layout would be handled by the same
> mapping which is configured for the system.
Take a look at the user level driver support (uinput).
Regards
Marcel
next prev parent reply other threads:[~2004-07-23 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 10:36 User-space Keyboard input? Mario Lang
2004-07-23 10:54 ` Marcel Holtmann [this message]
[not found] ` <87bri6n7nz.fsf@lexx.delysid.org>
2004-07-23 14:52 ` Marcel Holtmann
2004-07-24 1:02 ` Samuel Thibault
2004-07-24 6:09 ` Mario Lang
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=1090580051.4791.24.camel@pegasus \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlang@delysid.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