From: Pavel Machek <pavel@suse.cz>
To: Sébastien HINDERER <jrf3@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Keyboard simulation
Date: Thu, 1 Mar 2001 12:41:59 +0000 [thread overview]
Message-ID: <20010301124158.E34@(none)> (raw)
In-Reply-To: <3a9cc5953b575371@citronier.wanadoo.fr>
In-Reply-To: <3a9cc5953b575371@citronier.wanadoo.fr>; from jrf3@wanadoo.fr on Wed, Feb 28, 2001 at 10:38:03AM -0000
Hi!
> I'm writting a driver so that my soft braille display can work with the
> BRLTTY daemon.
> My braille computer contains a braille display, and a braille keyboard
> which I can use to enter characters that are transmitted to the computer.
> When my driver gets "normla" chars, he writes them to /dev/console. So for
> applications, it looks as if they came from the normal keyboard.
> Now, I'd like to be able to change the current virtual console and to view
> previously displayed screens (equivalent to shift+page up) just by pressing
> keys on the braille keyboard.
> So my question is: What should my driver do when it detects that the
> "change tty" key or the "scroll key" was pressed on the braille keyboard?
> Should the driver change the current tty itself (scroll the screen), or is
> it possible to call the kernel exactly like the normal keyboard driver
> would do (transmit keycodes), saying "alt + function key was pressed", or
> "shift + page up/down was pressed".
Transmit keycodes is AFAIK not implemented in official drivers.
Take a look at vojtech's new input suite.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2001-03-02 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 10:38 Sébastien HINDERER
2001-03-01 12:41 ` Pavel Machek [this message]
2001-03-02 23:14 ` Guest section DW
2001-03-04 11:40 ` Pavel Machek
2001-03-04 12:57 ` Guest section DW
2001-03-07 9:38 James Simmons
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='20010301124158.E34@(none)' \
--to=pavel@suse.cz \
--cc=jrf3@wanadoo.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®