From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: development questions
Date: Sat, 26 Jan 2002 21:23:10 -0500 [thread overview]
Message-ID: <005b01c1a6d9$92c9d760$0100a8c0@tward> (raw)
In-Reply-To: <001701c1a6d2$26881500$6801030a@greatmachine>
There is a Double Talk LT driver already.
----- Original Message -----
From: Chris Peterson <capeterson@visi.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, January 26, 2002 8:30 PM
Subject: Re: development questions
>
> ----- Original Message -----
> From: "Kirk Reiser" <kirk@braille.uwo.ca>
> To: <speakup@braille.uwo.ca>
> Sent: Saturday, January 26, 2002 5:38 PM
> Subject: Re: development questions
>
>
> > Well, the best way to start is to install speakup into a kernel and
> > start using it. You can find out about the keymap by reading the
>
> I'm waiting for my doubletalk pc to come so I can do that. Btw, is there
> any plan to write a driver for the doubletalk lt?
>
> > keymap tutorial in /usr/src/linux/Documentation/speakup. Basically
>
> >The following is from that tutorial:
> >keycode 72 = 0x0d0a
> > altgr keycode 72 = 0x0d20
> >#keycode 72 = KP_8
> > alt keycode 72 = Ascii_8
> >
> >Notice that the only thing which has changed on the first line is the
> >function called when the key is struck. It is a hexadecimal number
> >identifying the function called in a look up table. It is not a
> >symbolic representation yet because that means we need to change the
> >loadkeys program to understand our symbolic names. We will do this in
> >the future but for now it is more expedient to just use the table
> >indices. You will find a table at the bottom of this document
> >listing the review functions and their corresponding hex lookups.
>
>
> Okay, so where is that lookup table stored? I can read the one at the
botom
> of the tutorial, but I want to know where this is actually stored so I can
> understand how to add my own functions to it. Perhaps I didn't phrase my
> initial question well or I had to many questions in one message.
>
> Thanks,
> Chris
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Peterson
` Kirk Reiser
` Chris Peterson
` rmann
` Thomas Ward [this message]
` Chris Peterson
` Kirk Reiser
` Chris Peterson
` Angelo Sonnesso
` Geoff Shang
` Gregory Nowak
` Geoff Shang
` Buddy Brannan
` Thomas Ward
` Kirk Wood
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='005b01c1a6d9$92c9d760$0100a8c0@tward' \
--to=tward@bright.net \
--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).