From: Okash Khawaja <okash.khawaja@gmail.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Cc: Gregory Nowak <greg@gregn.net>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: supporting more than ttyS*
Date: Wed, 7 Jun 2017 14:40:12 +0100 [thread overview]
Message-ID: <20170607134012.GA2444@sanghar> (raw)
In-Reply-To: <45AB8D04-640E-418B-B002-4B232F118A4D@gmail.com>
On Mon, Jun 05, 2017 at 06:11:13AM +0100, Okash Khawaja wrote:
>
>
> > On 4 Jun 2017, at 23:47, Gregory Nowak <greg@gregn.net> wrote:
> >
> >> On Sun, Jun 04, 2017 at 10:37:17AM +0200, Samuel Thibault wrote:
> >> Tom Fowle, on sam. 03 juin 2017 23:22:41 -0700, wrote:
> >>> Since many parallel ports are not bidirectional, it might be hard or
> >>> impossible to support indexing on a parallel port.
> >>
> >> Yes.
> >
> > That did occur to me as well. The blazer manual doesn't mention
> > anywhere that a ieee1284 cable is required. I have in fact used it
> > under a windows screen reader using a standard non-bidirectional cable
> > without issues. If a synthesizer supports indexing, would speakup
> > enable it when using a serial port, and disable it when using a
> > parallel port,
> Yes, that should be possible. Haven't looked at code but can't see why we can't disable it on parallel port.
>
> On a general note, I don't know much about parallel port programming yet, so there still might be issues unaddressed in the first pass. Of course we can come back to them in subsequent patches.
Indexing on /dev/lp* can be disabled by returning 0 from
synth_supports_indexing function in synth.c, whenever the device is lp*.
However, there are other places where input is also used. Ideally we
would disable all such functionality for lp*. Some synths also toggle
serial control lines which I am not sure will be possible or supported
by default in lp. Will have to look into this.
So I suggest, for the first pass we limit lp support to bns, acntsa,
dummy and txprt. Then we expand it to other synths based on their
functionality, e.g. on ltlk we disable indexing and interrogating to
print ROM version.
Let me know if that's okay.
Thanks,
Okash
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
Okash Khawaja
` Samuel Thibault
` Gregory Nowak
` Samuel Thibault
` Gregory Nowak
` Samuel Thibault
` Okash Khawaja
` Samuel Thibault
` Okash Khawaja
` Tom Fowle
` Samuel Thibault
` Gregory Nowak
` Okash Khawaja
` Okash Khawaja [this message]
` Samuel Thibault
` Tom Fowle
` Samuel Thibault
` Gregory Nowak
` Chris Brannon
` Gregory Nowak
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=20170607134012.GA2444@sanghar \
--to=okash.khawaja@gmail.com \
--cc=greg@gregn.net \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).