more fixes for my modded speakup

[David]

Multi line reads like say screen now release the lock between lines
so the voice thread can get in earlier.
smarter highlight tracking scores colors to determine what should be read.
a bunch more work so synths can write usb devices etc.
This is a work in progress.
moved bleep into the main with a timer so the catch-up thread only
handles the synth. then for soft synth, we won't even create it.
The buffer.c code now allows gets of strings which auto-lock
until the next status check so we will be able to write blocks
of data to a system device driver.
Soon I can use my dec talk on a netbook with a usb to serial converter!
Hopefully I didn't break anything. I only have a dectalk for testing.

[Zachary Kline]

Hey,

The news about the DecTalk with serial converter is awesome, as the recent weirdness with Espeakup/Alsa attest. DO you have any idea when this might be merged back into the mainline? I haven’t done any kernel compilation in a long time, le alone patching like this.

Thanks,
Zack.

Post by David
Multi line reads like say screen now release the lock between lines
so the voice thread can get in earlier.
smarter highlight tracking scores colors to determine what should be read.
a bunch more work so synths can write usb devices etc.
This is a work in progress.
moved bleep into the main with a timer so the catch-up thread only
handles the synth. then for soft synth, we won't even create it.
The buffer.c code now allows gets of strings which auto-lock
until the next status check so we will be able to write blocks
of data to a system device driver.
Soon I can use my dec talk on a netbook with a usb to serial converter!
Hopefully I didn't break anything. I only have a dectalk for testing.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Chris Brannon]

Post by David
moved bleep into the main with a timer so the catch-up thread only
handles the synth. then for soft synth, we won't even create it.

Is it safe? If I remember right, I was the one who moved bleep into
its own thread, and I did it because of a kernel change that started
causing lockups. My memory is really fuzzy, and I can't spot anything
in list archives. But maybe it was that kd_mksound was sleeping with a
spinlock held?

-- Chris