From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail.surferie.net ([63.175.116.33])
	by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian))
	id 198PYm-00013Q-00
	for <speakup@braille.uwo.ca>; Wed, 23 Apr 2003 15:05:36 -0400
Received: from beavis.surferie.net [205.162.139.114] by mail.surferie.net with
 ESMTP
  (SMTPD32-6.06) id A30139F017C; Wed, 23 Apr 2003 15:01:21 -0400
Message-Id: <5.2.0.9.0.20030423150005.00c41eb0@mail.surferie.net>
X-Sender: jacobs@mail.surferie.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 23 Apr 2003 15:04:40 -0400
To: speakup@braille.uwo.ca
From: Jacob Schmude <jacobs@surferie.net>
Subject: Re: trippletalk status?
In-Reply-To: <x7vfx5l9gp.fsf@speech.braille.uwo.ca>
References: <5.2.0.9.0.20030423044544.00c201d8@mail.surferie.net>
 <5.2.0.9.0.20030423044544.00c201d8@mail.surferie.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; x-avg-checked=avg-ok-558C3908;
 boundary="=======62E91E16======="
Sender: speakup-admin@braille.uwo.ca
Errors-To: speakup-admin@braille.uwo.ca
X-BeenThere: speakup@braille.uwo.ca
X-Mailman-Version: 2.0.11
Precedence: bulk
Reply-To: speakup@braille.uwo.ca
List-Help: <mailto:speakup-request@braille.uwo.ca?subject=help>
List-Post: <mailto:speakup@braille.uwo.ca>
List-Subscribe: <http://speech.braille.uwo.ca/mailman/listinfo/speakup>,
	<mailto:speakup-request@braille.uwo.ca?subject=subscribe>
List-Id: Speakup is a screen review system for Linux. <speakup.braille.uwo.ca>
List-Unsubscribe: <http://speech.braille.uwo.ca/mailman/listinfo/speakup>,
	<mailto:speakup-request@braille.uwo.ca?subject=unsubscribe>
List-Archive: <http://speech.braille.uwo.ca/pipermail/speakup/>

--=======62E91E16=======
Content-Type: text/plain; x-avg-checked=avg-ok-558C3908; charset=us-ascii;
 format=flowed
Content-Transfer-Encoding: 8bit

Hi
Great to hear it's being worked on! Unfortunately I don't have a PCI one to 
send (I'm not gonna buy one if I can't use it) but it's great to know that 
there is progress. Could you explain a bit what you meant by the "chipset 
code?" Do you mean the actual chips in the PCs, or the kernel drivers? I've 
got a VIA kt400-based board but it works with the UHCI driver and EHCI for 
USB 2.0. Would this be compatible whenever the driver is released?

At 07:49 4/23/2003 -0400, you wrote:

>We have a Trippletalk usb synth.  We also have a usb driver partially
>written for it.  One of the problems has been that the usb code for
>the Intel family of chips is fairly stable while the code for the Via
>chip set is not.

--=======62E91E16=======--