[BRLTTY] brltty new user

kendell clark coffeekingms at gmail.com
Sat Jul 2 22:38:12 EDT 2016


hi
The odroid is an ARM based computer wich can run android or any other
linux distro that supports the ARM architecture. What he means by
staging is the kernel modules that are considered unstable for whatever
reason. It usually only contains brand new kernel modules while they're
being developed and they're moved out into the main kernel. But speakup
has never made it out. I don't know why, but I've heard that it's
because of the way it access older serial based synthesizers,
communicating raw commands instead of using the /dev/ttyusb0 and
/dev/ttys0 and other serial devices.
Thanks
Kendell Clark


Dave Mielke wrote:
> [quoted lines by Storm Dragon on 2016/07/02 at 21:48 -0400]
>
>> The device is something like /dev/svca. I haven't done anything with it 
>> myself, but maybe it could be useful.
> It's /dev/vcsa. Brltty does use it. It doesn't stream new characters written 
> to the screen. It allows the current screen content to be read.
>
>> Speakup is a great screen reader. I personally love it and would happily be 
>> using it now, except the Odroid kernel doesn't include staging, so no speakup 
>> for me. 
> What's the Odroid kernel? Is Odroid a Linux distribution that, for whatever 
> reason, you prefer to use?
>
> What do you mean by "staging"?
>
>> I have to find an alternative. I have been using full graphical for a while 
>> now. 
> What do you use in graphical mode? Orca? If so, I guess you're already using 
> brltty, as well, for that.
>
>> A lot of people think the screen reader doesn't belong in the kernel. 
> I guess what you're really saying is that you like Odroid (whatever it is), but 
> they (the Odroid people) believe that the screen reader doesn't belong in the 
> kernel, thus they don't think they should be including Speakup.
>
>> Personally I could care less if it is in the kernel or user space, just so 
>> long as it works. I don't care about the politics, just the functionality lol, 
> Yes, I understand. From their perspective, though, it's probably very hard to 
> maintain something on an on-going basis that's in the kernel.
>
> Of course, that's something the Speakup people should be doing. Have they 
> stopped doing it?
>
>> As for getting it working with pulse, I can't take credit for that. Chrys 
>> figured that out. You just have to drop in 2 files and it will start playing 
>> nicely together. I have attached them here. The client.conf goes in the pulse 
>> config for root: Place the default.pa in your ~/.config/pulse directory 
>> Finally restart pulseaudio or reboot your computer and it should work. 
> Only default.pa was attached. Please also send the other one (client.conf?). I 
> can include them with brltty's distribution. I can also include a nice set of 
> instructions if you won't mind writing up a nice how-to.
>
>> Speech with espeak is a bit too quiet even on loudest setting, but other than 
>> that, it is very responsive and quite nice to use.
> I think I know what might fix that. Are you building brltty from source so that 
> we can give it a try?
>



More information about the BRLTTY mailing list