-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Oct 14 2004 at 10:12:53PM -0400, Dave Mielke wrote: > I don't think so. This highlights what I believe to be a current problem with > how the two applications have been integrated. Speakup, as I understand it, > always tries to start. If you don't specify a device or synthesizer type then > it autoprobes. This means that Speakup will autoprobe your BrailleLite. This > may cause problems to both Speakup and the BrailleLite. I don't think there's > currently a way to tell Speakup to simply not start at all. You can use a kernel parameter of speakup_synth=none to prevent speakup from probing, but whatever you do you're not going to get meaningful braille output from speakup. If you're using a current version of speakup you can then do "echo synthname >/proc/speakup/synth_name" to start speakup. - -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan Thomas Stivers e-mail: stivers_t@xxxxxxxxxxxxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBbzXZ5JK61UXLur0RAr/PAJ4u3YvkH8w6FqAVz87BVbvOXC2jUACfRCua bJUCDaaUfZl2FClfb16lXrw= =C7wO -----END PGP SIGNATURE----- _______________________________________________ Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list