public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Zachary Kline" <klinez@onid.orst.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup and hald conflict in Slackware 12.2
Date: Mon, 15 Dec 2008 23:16:22 -0800	[thread overview]
Message-ID: <7ABE31F924E74FEA8FF5C5A82111FBB9@ZKMOBILE> (raw)
In-Reply-To: <20081216064224.GB30529@localhost.localdomain>


----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, December 15, 2008 10:42 PM
Subject: Re: speakup and hald conflict in Slackware 12.2


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, Dec 15, 2008 at 07:36:54PM -0800, Zachary Kline wrote:
>> I, too, am
>> using a Dectalk USB in serial mode, with VirtualBox, for what that's
>> worth.
>
> Well, I've got gnome, and hal too, running under debian testing in
> virtualbox, and am not seeing sluggish response, when using the bns as
> the synth. So, I'd say that whether running under virtualbox, or on
> actual iron probably doesn't make a difference here, since using the
> bns on a real box is fine here, in both cases (except for vbox's
> serial port issues), as I've said before.
>
> BTW, speaking of virtualbox, how are you managing to use the dectalk,
> given vbox's serial port issues?
>
> http://vbox.innotek.de/ticket/812
>
Hi Greg,
    I'm using Virtualbox 2.0.6 under a Windows XP host.  I haven't noticed 
any serial port issues, certainly not as described in the above ticket. 
(Perhaps it has something to do with the fact that by default the Dectalk 
USB in serial mode seems to use Xon/Xoff handshaking?)
    I use a USB-to-serial converter on both my desktop and laptop with the 
Dectalk this way.  VirtualBox doesn't react oddly at all, and the unit just 
works.  I must confess, though, that the intricacies of serial 
communications are for the most part beyond me.  I'm just glad to be able to 
say that it works for me, though I don't know why.
Hope this helps, somehow.
Best,
Zack.


  reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Adam Myrow
 ` Igor Gueths
   ` Gregory Nowak
 ` Michael Whapples
   ` Adam Myrow
   ` Adam Myrow
     ` Gregory Nowak
     ` Zachary Kline
       ` Gregory Nowak
         ` Zachary Kline [this message]
           ` Garrett Klein
             ` Gregory Nowak
               ` Alex Snow
                 ` Zachary Kline
         ` Alex Snow
           ` Zachary Kline
             ` Alex Snow

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=7ABE31F924E74FEA8FF5C5A82111FBB9@ZKMOBILE \
    --to=klinez@onid.orst.edu \
    --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).