public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: USB synthesizers
Date: Mon, 22 Feb 2010 10:25:08 -0600	[thread overview]
Message-ID: <20100222162508.GA28605@linux1> (raw)
In-Reply-To: <alpine.DEB.2.00.1002111645340.3165@hawk.zacknet>

Hi Zack,

On Thu, Feb 11, 2010 at 04:52:12PM -0800, Zachary Kline wrote:
> Since the topic of serial ports has come up, I thought I might inquire 
> about the possibility of interfacing directly with those USB hardware 
> synthesizers that do exist.  I'm thinking especially of the Dectalk USB, 
> which I happen to own.
> I don't know much about USB protocols, but I'd guess the one it uses isn't 
> just an encapsulation of the one used over the serial port?  I just think 
> that if we could either reverse-engineer or better yet pursuade the 
> manufacturers to give us the specs for those protocols, we'd dodge the 
> serial port problem entirely.
> I'm probably raising the same question that bugs free software people 
> everywhere, but I thought it should be asked.

Actually this is being worked on.  I have sent email to the
manufacturer (Access Solutions) last week about getting the specs.  I'll
let you know what happens there.

I own a triple talk USB myself, so I am looking at writing the driver for it
to start with, then probably the dectalk USB.

I'll probably start with kernel level device drivers that create
a device in /devso they can be accessed from user space then figure out
how to integrate them into speakup.

Thanks,

William


  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` William Hubbs [this message]
   ` William Hubbs
     ` acollins
       ` Gregory Nowak
         ` Trevor Astrope
           ` Kirk Reiser
             ` Tyler Littlefield

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=20100222162508.GA28605@linux1 \
    --to=w.d.hubbs@gmail.com \
    --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).