[BRLTTY] BRLTTY and Raspberry PI
kperry at blinksoft.com
kperry at blinksoft.com
Sun May 1 20:46:44 EDT 2022
Excellent thanks. Now to go play and see if I can get my build to work.
-----Original Message-----
From: BRLTTY <brltty-bounces at brltty.app> On Behalf Of Dave Mielke
Sent: Sunday, May 1, 2022 8:27 PM
To: Informal discussion between users and developers of BRLTTY.
<brltty at brltty.app>
Subject: Re: [BRLTTY] BRLTTY and Raspberry PI
[quoted lines by kperry at blinksoft.com on 2022/05/01 at 19:07 -0400]
>Options? I have not given it any options.
And maybe you don't need to. I just mentioned that the run-brltty script
takes the same options as brltty in order to describe it.
>So I am not sure what I should give it for a Orbit reader 20 (Not plus).
Or an Orbit Reader 40.
Brltty has (hopefully) sensible defaults. One of those defaults is to
autodetect the braille device that you're using.
>Can you send me what the lines should look like for those two?
If you want to be explicit: The Orbit Readers use the Baum driver, so that'd
be -bbm. If it's connected via USB then that'd be -dusb: (yes, the trailing
colon is required). As I've already mentioned, though, you shouldn't need
to.
A couple of options you may want to know about are the ones used for
logging. There's -L (uppercase) to specify the log file, and there's -l
(lowercase) to specify what to log. You may wish to use these to look for
problems. If you'd like more than the usual logs then you can use, for
example, -ldebug.
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: Dave at Mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke
Phone: +1 613 726 0014 | Canada K2A 1H7 |
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY at brltty.app For general
information, go to: http://brltty.app/mailman/listinfo/brltty
More information about the BRLTTY
mailing list