public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup in userspace
Date: Wed, 20 Jun 2007 06:20:51 -0500	[thread overview]
Message-ID: <00d301c7b32d$0f5afd30$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070620083354.GA4139@fajrero>

A few useful references

http://linuxconsole.sourceforge.net/input/input.html

Using the Input Subsystem - No matter how many buttons an input device
has or how many kinds of events it can generate, you can now work with
it from user space.

http://www.linuxjournal.com/article/6429

Here is part one of that article series
http://www.linuxjournal.com/article/6396

Here is a useful way to browse around in the input driver source
http://www.gelato.unsw.edu.au/lxr/source/drivers/input/?a=i386

This POC /dev/input/event/* keylogger is interesting
http://archives.neohapsis.com/archives/sf/linux/2005-q3/0065.html

This is an interesting simple example driver code for input driver
http://kernel.org/pub/linux/kernel/people/landley/kdocs/Documentation/input/input-programming.txt

This is old but useful due to its description of the bigger picture
of keyboard scancodes and related stuff
http://www.linuxjournal.com/article/1080

As for console output, just as with the Input Driver redesign, it is
changing quicky and they are trying to clean up the architecture.
I suppose the first thing would be to see how the console is
changing and where it's heading architecture wise. I have a lot
of interest in this for other projects and will be doing some
investigation.

One thing I have in mind is implementing what will basically be the
equivalent of a VT100 terminal using a small microcontroller, where
input is an attached keyboard and output is speech. Since there
already is serial console, a means to implement a terminal with
keyboard input and speech output would be quite useful. Rather
than connecting a machine to serial port for console, you'd plug
in a dongle which would have both a keyboard port and an
output port for speech, or possibly even speech hardware in the
actual dongle. I'll share some more info on this idea a bit later.

  -- Doug



  parent reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Spivey
 ` Luke Yelavich
   ` Samuel Thibault
     ` Luke Yelavich
       ` Samuel Thibault
 ` Doug Sutherland [this message]
   ` Samuel Thibault
     ` Doug Sutherland
       ` Samuel Thibault
         ` Christopher Moore
           ` Samuel Thibault
           ` Albert E. Sten-Clanton
             ` Doug Sutherland
               ` W. Nick Dotson
               ` Albert E. Sten-Clanton
             ` Deborah Norling

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='00d301c7b32d$0f5afd30$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).