From: Nicolas Pitre <nico@cam.org>
To: Lee Maschmeyer <Lee_Maschmeyer@wayne.edu>
Cc: blinux-list@redhat.com
Subject: Re: Diagnosing ABT320 Braille Terminal
Date: Fri, 9 May 2003 12:36:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0305091213590.11745-100000@xanadu.home> (raw)
In-Reply-To: <20030509152433.GB1336@wayne.edu>
On Fri, 9 May 2003, Lee Maschmeyer wrote:
> IMHO, one thing that adversely affects the Alva is that the left and
> right keys are not typematic. I doubt this matters on an 80-character
> display, but on a 40 it's a pain and I bet it's worse on a 20. Thanks to
> Nicolas I found the place in the source where I could change it, but it
> still seems an unfortunate default.
And I explained why...
> However, the Linux Alva driver seems more sluggish than (my memory of)
> the DOS program, so I don't think it's the serial port settings since
> DOS presumably uses the same ones.
On DOS the default mode of operation is through the parallel port which is a
much faster link. Even BRLTTY is much snappier with a parallel port
connection. But unfortunately the parallel port protocol information isn't
available and only an old binary-only library exists which just can't be
linked with BRLTTY using recent versions of gcc.
But to reduce the sluggishness a lot you can change the default serial
baudrate from 9600 to, say, 38400. On BRLTTY's side you need to edit
Drivers/Alva/brlconf.h accordingly and recompile. On the Alva side you need
to change the baudrate using the built-in menus accessible by pressing
PROG+HOME+CURSOR simultaneously.
Nicolas
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
John J. Boyer
` Travis Roth
` Lee Maschmeyer
` John J. Boyer
` Nicolas Pitre
` Lee Maschmeyer
` John J. Boyer
` Nicolas Pitre [this message]
` John J. Boyer
` Nicolas Pitre
` to John J. Boyer <director@chpi.org> Nicolas Pitre
` Diagnosing ABT320 Braille Terminal Tom Masterson
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=Pine.LNX.4.44.0305091213590.11745-100000@xanadu.home \
--to=nico@cam.org \
--cc=Lee_Maschmeyer@wayne.edu \
--cc=blinux-list@redhat.com \
/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).